Re: [platform-debug-dev] BreakpointGroups branch

[Jared Burns <jaredburns@xxxxxxx>]

I've moved the breakpoint group code over to HEAD. It's all still very
much work-in-progress (lots of vacation time recently ;) ), but I'm not
aware of any problems that will prevent people from working while
running the new code.

- Jared

On Thu, 2004-09-02 at 11:09, Darin Wright wrote:
> > 
> > I've created a branch named BreakpointGroups for the debug core and
> > debug ui plugins. Interested parties (I'm looking at you, committers :))
> > are encouraged to give this (very much unfinished) code a spin and
> > provide feedback.
> > 
> 
> We (Kevin & Darin W) took it for a test drive. Overall, we like the 
> presentation/feature. Here are some suggestions that we feel would make 
> groups easier to use.
> 
> Creating Initial Groups
> -----------------------
> Creating groups is cumbersome when you want to group everything by file, 
> project, or type. For example, to group all breakpoints by file I have to:
> * select a breakpoint
> * choose "Select by File"
> * choose "Add Group"
> * give the group a name
> * repeat for each file
> 
> Provding a "Group All By >" cascade menu with the options "File, Project, 
> Type" could automatically create groups and (re)group all breakpoints. The 
> groups would be given appropriate names automatically. This action would 
> work on all breakpoints and re-group all breakpoints (destructive).
> 
> Similarly, a "Group By >" cascade menu with the options "File, Project, 
> Type" could automatically create groups and (re)group *selected* 
> breakpoints. This should re-use any existing groups (i.e. if there is 
> already a group for File A, it should be re-used).
> 
> We could also group the "Select" actions in a submenu like "Select By >" 
> "File, Project, Type".
> 
>  
> Default Group
> -------------
> The ability to set a group as the default group for new breakpoints is 
> nice. To emphasize this, the default group could be bolded in the 
> breakpoints view (or something to make it stand out). As well there could 
> be a toggle action "Default Group" (context menu with check mark) to set 
> another group as default, or turn off the current default group.
> 
> Add To Group
> ------------
> It would be nice to have a drop-down box on the "add" dialog to choose 
> from existing groups (rather than having to type it in).
> When a breakpoint is added to a group, and that group is collapsed, we 
> should expand/select the breakpoint, otherwise the user does not see it 
> (i.e. feedback). Perhaps we should select any breakpoint that is 
> created/added to the breakpoint list.
> 
> Group Actions
> -------------
> The "Disolve Group" action could be named "Ungroup" (simpler?).
> The "delete/remove" action in the toolbar could work on selected groups - 
> i.e. delete the group and all breakpoints in them. However, this action 
> should prompt before proceeding, as it affects more than one breakpoint.
> 
> Moving between groups
> ---------------------
> Of course, drag & drop would be nice.
> 
> Bugs(?)
> -------
> * Select all doesn't work anymore.
> * When I remove all breakpoints from a group, and it was the default, it 
> still exists, which is unexpected (i.e. a newly create breakpoint is 
> placed into the group that I could not see).
> * When "skip all" is pressed, breakpoints within groups are rendered with 
> black check marks instead of grey
> 
> 
> Darin & Kevin.
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-debug-dev