Re: java mdr ui spec

Tim Boudreau <[email protected]> Thu, 13 Feb 2003 19:59:54 +0100
Newsgroups gmane.comp.java.netbeans.modules.mdr.devel
Organization CollabNet Hosting
Message-ID <[email protected]>
cL wrote:
> hey folks,
> 
> i've updated the spec:
> 
> http://ui.netbeans.org/docs/hi/javamdr/index.html
> 
> it would be nice to link to it from the mdr module web page.
> 
> based on the meeting we had last week here in prague i've made a few 
> minor changes to the spec:
> 
> 1. the split in the explorer is not horizontal
> 2. removed spec for integrating parsing options with 3.x mount f.s. 
> procedure. the spec now focuses purely on projects integration
> 3. added Source Editor section. this is new and only sketched out 
> roughly based on comments in the meeting

You could consider docking the object explorer into the *right*
side of the editor, at least if getScreenSize() returns a reasonable
value for width (okay, with layers that's a little hard).

> Open Issues (from the document)
> 
> Does the tree work everywhere? Should some of the views have a different 
> display model (list, tree table, etc)

I played with this writing the class navigator module.  If you're
only displaying a flat list of something like class members, it
uses horizontal space better to use a list and avoid the

|_
|_
|_

line of the tree.

> What information has been left out of the spec. Specifically, in the 
> Object Explorer, are there details in any of the views that should be 
> added?

Another option for UI, if we wanted to go there, is a Mozilla-style
component that can be popped open on demand, and the rest of the time,
shows a small line and handle that can be clicked.  Sort of like a
JSplitPane you can open with a single click, I don't know what they
call such a component.  You'd know better than I if they're intuitive.

> Is the UI implementable? The split pane spec'd here is a never before 
> seen item for nb.

How so?  Not much reason it couldn't be its own explorer component -
it's mainly how they're positioned together that determines the
perception that it and the traditional explorer are the same component
or different ones, AFAIK.

Cheers,

Tim