Chuck, would the 'common' component
be a good home for this work? I'm not sure its needs a separate CVS home
and bugzilla component.
Its seems analogous to tabbed properties
view, which will be in 'common' component. Similarly with 'snippets view'
(if and when we can
make it completely free of sse dependancies).
I think the definition of 'common' component
is something that's not really web or jst related ... and is pre-req'd
or used by more than one other component ... and could
in theory be part of base eclipse. (I
say 'in theory' just to emphasize that it has no dependancies on other
web or jst components, I don't mean to say it "should" be in
though that's debatable in this case
It seems "common.navigator"
would still be good plugin/package name.
It could still have its own 'feature'
and plugins, and still be in 'common', right? And there need be nothing
"common place" about the plugins in 'common'.
Have you heard my old story about "Common
Lisp" ... in version 1 they found no one got excited about it, because
it was perceived as "common place" so in the second
version they called it "Common
Golden Lisp" ... maybe we should have named that component 'golden'
Chuck Bridgham/Raleigh/IBM@IBMUS Sent by: wtp-dev-admin@xxxxxxxxxxx
11/09/2004 01:02 PM
Please respond to
[wtp-dev] Request for "navigator"
component to be moved to wst
I have another move request after studying the dependencies, and intended
audience of this component.
The "navigator" component offers a pluggable content based view
that is fully customizable - and is not limited to jst components.
This component belongs in wst so components from both subprojects can take
Thanks - Chuck
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Phone: 919-254-1848 (T/L: 444)