Re: [cdt-debug-dev] feature work

[John Cortell <john.cortell@xxxxxxxxxxxxx>]

Mikahil,

Ah; OK. I see now. Hm. I'm not sure the type of information I'm 
looking to expose for register details fits nicely into a key-value 
pair view. I need more of an open-ended canvas. I actually think the 
Properties dialog would be more along the lines of what I was 
thinking. So, even though that might not have been your intended 
suggestion, I'm glad I misunderstood you :-)

John

At 04:17 PM 5/17/2006, Mikhail Khodjaiants wrote:
> John,
>
> I was talking about the Properties view ("Window->Show 
> view->Other->General->Properties"), not the Properties dialog. It's 
> a general view that listens to the current selection in the active 
> view and tries to get the properties provider for the selected object.
> The "value" fields of the view are not exclusively textual. The 
> "Browse" button or a selection list widget also can be used. It may 
> not look very attractive but it's not too bad as a first step.
>
> Mikhail
> ----- Original Message ----- From: "John Cortell" <john.cortell@xxxxxxxxxxxxx>
> To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>; "CDT 
> Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
> Sent: Wednesday, May 17, 2006 5:07 PM
> Subject: Re: [cdt-debug-dev] feature work
>
>
> > Mikhail,
> >
> > Certainly; the new view would get its debug context from the Debug 
> > view. It just wouldn't be tied to the Registers View.
> >
> > Well, I can certainly try to see if I can design the GUI of the 
> > feature to fit in the details pane. I also like the idea of the 
> > properties dialog. It's application modal from what I can tell, but 
> > I don't think that presents a work flow problem.
> >
> > Thanks for the suggestions.
> > John
> >
> >
> > At 03:39 PM 5/17/2006, Mikhail Khodjaiants wrote:
> > > John,
> > >
> > > Yes, it wouldn't look very good if you want to use exactly the 
> > > same widgets and layout. But the info field can be replaced by a 
> > > button, the format field can be removed, etc. So, I don't think it's a problem.
> > > Another approach is to use the properties framework (see 
> > > org.eclipse.ui.view.properties), so instead of adding a new view 
> > > you can use one that is already in place.
> > >
> > > And in your implementation the detail view still should be tied to 
> > > the current debug context to display changes and to clean up the 
> > > view when the session is terminated.
> > >
> > > Anyway, it's just my 2 cents...
> > >
> > > Mikhail
> > > ----- Original Message ----- From: "John Cortell" 
> > > <john.cortell@xxxxxxxxxxxxx>
> > > To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>; "CDT 
> > > Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
> > > Sent: Wednesday, May 17, 2006 3:15 PM
> > > Subject: Re: [cdt-debug-dev] feature work
> > >
> > >
> > > > Mikhail,
> > > >
> > > > Please look at the amount of detail in the screenshot I attached 
> > > > to the bug report. How do you figure I can cram all that UI into 
> > > > the details pane of the registers view?
> > > >
> > > > Also, I never said the new view would be tied to the existing 
> > > > registers view. If anything, I could see right clicking on an 
> > > > item in the registers view and selecting "Set in details view", 
> > > > which would change the context in the new view. But the two views 
> > > > would not actually be tied.
> > > >
> > > > Do you still think it's a bad idea?
> > > >
> > > > John
> > > >
> > > > At 02:04 PM 5/17/2006, Mikhail Khodjaiants wrote:
> > > > > John,
> > > > >
> > > > > Register Details View: 
> > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=137681.
> > > > > As I have already mentioned, I don't think it's a good idea to 
> > > > > add an additional view that depends on the selection in another 
> > > > > view. I think 
> > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=75852 (Support for 
> > > > > custom details view widgets) is much better solution.
> > > > >
> > > > > Mikhail
> > > > > ----- Original Message ----- From: "John Cortell" 
> > > > > <john.cortell@xxxxxxxxxxxxx>
> > > > > To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
> > > > > Sent: Wednesday, May 17, 2006 2:53 PM
> > > > > Subject: [cdt-debug-dev] feature work
> > > > >
> > > > >
> > > > > > We plan to implement the following features in the upcoming 
> > > > > > months. Please feel free to attach any suggestions you have to 
> > > > > > the bugzilla reports.
> > > > > >
> > > > > > Save/Restore Registers: 
> > > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=126657
> > > > > > Save/Load/Fill Memory: 
> > > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=100080
> > > > > > Register Details View: 
> > > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=137681
> > > > > >
> > > > > > John
> > > > > >
> > > > > > _______________________________________________
> > > > > > cdt-debug-dev mailing list
> > > > > > cdt-debug-dev@xxxxxxxxxxx
> > > > > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> > > > >
> > > > > _______________________________________________
> > > > > cdt-debug-dev mailing list
> > > > > cdt-debug-dev@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> > > >
> > > > _______________________________________________
> > > > cdt-debug-dev mailing list
> > > > cdt-debug-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> > >
> > > _______________________________________________
> > > cdt-debug-dev mailing list
> > > cdt-debug-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev