[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-dev] More Renames for Common navigator in HEAD
|
Will be glad to do so. But thought it good to discuss them prior to
opening bugs that the group might think frivolous. I'm working on using
the Navigator for usecases outside of WTP. It would be great to
eventually see it up in the ide someday but for now I'm happy to use it
with WTP.
I'll supply some patches where I can.
BTW, when is the next milestone planned for release? If such a thing can
be planned ;-)
-Mark
David M Williams wrote:
Thanks for the comments Mark.
Many would agree with you, some of these issues have been discussed,
and I just happen to know
that component lead has promised to cleanup that particular 'logger'
problem :)
I suggest, however, when you notice issues like this you open a
feature/bug request which
details both
1) the problem/issues involved, and
2) the importance/motivation for fixing (for example, if inhibitor for
use of R1, or, hard to
load minimum from CVS, etc.)
If you'd like to call to the attention of the WTP Architecture Group,
please use [arch] in the
beginning of the bug summary, so we'll find it with some of our
standard queries.
Oh ... and, BTW, feel free to open feature requests for a component
with a patch that "cleans
up" any issues you can ... if its something that's large and touches a
lot of files, like the
logger issue, first please state your willingness to help (in the
feature request), and ask the
component lead (in the feature request), when would be the best time
to "synch up" to provide
the most useful patch.
Thanks again
*Mark Diggory <mdiggory@xxxxxxxxx>*
Sent by: wtp-dev-bounces@xxxxxxxxxxx
04/10/2005 12:41 PM
Please respond to
mdiggory and "General discussion of project-wide or architectural issues."
To
"General discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
cc
Subject
Re: [wtp-dev] More Renames for Common navigator in HEAD
Is the common navigator planned to always have the dependency on JEM and
JDT? Or are there efforts to factor this out into the JST? I notice
there are a number of dependencies that are a little weak. Such as
dependency on a "Logger" class in JEM. Logging could go directly to the
Eclipse logger, dependencies like this cause large libraries (JDT) to
have to be present just to use Common Navigator. Seems as though the
CommonNavigator and the WorkbenchNavigator extension should really be
weaned of such dependencies. I'd recommend that the two be refactored to
function on just the Eclipse Platform runtime and not the full Eclipse
SDK.
-Mark Diggory
Chuck Bridgham wrote:
>
> The following classes have moved to internal.provisional
>
> org.eclipse.wst.common.navigator.views ->
> org.eclipse.wst.common.navigator.internal.provisional.views
> AdaptabilityUtility.java
> CommonActivitiesUtilities.java
> CommonNavigator.java
> CommonNavigatorManager.java
> CommonSorter.java
> CommonViewer.java
> ICommonActionProvider.java
> ICommonDropActionDelegate.java
> ICommonLabelProvider.java
> ICommonMenuConstants.java
> ICommonOpenListener.java
> ILinkHelper.java
> INavigatorContentExtension.java
> INavigatorContentProvider.java
> INavigatorExtensionFilter.java
> NavigatorActionService.java
> NavigatorContentService.java
> NavigatorContentServiceContentProvider.java
> NavigatorContentServiceLabelProvider.java
> Priority.java
>
> Thanks - Chuck
>
> Rational J2EE Tooling Team Lead
> IBM Software Lab - Research Triangle Park, NC
> Email: cbridgha@xxxxxxxxxx
> Phone: 919-254-1848 (T/L: 444)
>
>------------------------------------------------------------------------
>
>_______________________________________________
>wtp-dev mailing list
>wtp-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
