Re: [EBOB-DISCUSS] UI for "Inspect": please respond

[Liam M. <lm...@wp...>]

Comments embedded.

Gary Pollice wrote:

>[gfp] I'm curious.
>  
>
The properties view uses a table tree viewer, but instead of allowing a 
complete heirarchy, they allow just one level- any property can have a 
"category", but you can't have nested categories. So we'd have to have a 
popup for inspecting an object within the object. (We couldn't have 
replace the contents of the properties view because that would break 
with the properties view being selection based.) Also, anyone can turn 
these categories on or off so we can't expect them to be there; the 
category would have to end up being something like the name of the 
variable, and everything else would be on the same level. It also 
doesn't support images whatsoever, so I couldn't use the same images 
that Eclipse uses in the rest of the UI. It's all less than ideal.

>[gfp] I bet with a little creativity you can come up with a 16x16 image that
>would work. You can also just use what many tools put in for public (+),
>private (-), and protected (#) properties and add something for final.
>
Are you saying we could do it in ASCII? Or come up with our own smaller 
image? I actually misspoke about the image size- I just checked, and the 
TableTreeViewer is cutting off the images to a size of 10x10 pixels, 
which I don't understand at all. The icons which are the size we would 
want are 16x16. I think that being consistent with the JDT would be 
great, seeing as how they give us a whole bunch of images to use off the 
bat. I'd also want to follow 
http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#IconSpecsOvr_VDG.

>This way, we can expand objects that are within other objects in a UI that's
>fairly consistent with Eclipse, as opposed to a pop-up "Inspect" 
>dialog which would open yet another "Inspect" dialog.
>[gfp] There's precedent for using inspect dialogs since they are very much a
>part of debugging.
>  
>
A pop-up dialog while debugging in Eclipse? Where is that?

>[gfp] It's probably fine. Now, putting on my Mr. Draco hat ... are these the
>important things that will keep you from having a working project? What's
>the first deliverable? Get that and then incrementally add. I'm really
>concerned that you're suffering from feature creep. Not that this isn't a
>good thing to do in the sense of a research project, but you do need to
>realize that there's a deadline that will be quickly coming up.
>
Actually I'm way ahead of schedule, and I'm bored. The deadline for this 
iteration is in 1 week, I could do this in two days (seeing as how I can 
reuse most of the code), and it's really all that's assigned to me this 
iteration. If we had to release it today, I'd release the existing 
tabletreeviewer from last iteration.

Liam