[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [wtp-dev] The Big Picture
|
That's good to hear about source editors' dependency on modulecore. Just
for my curiosity, could you elaborate a bit on what you mean by the
dependency becoming optional? Is that an OSGi facility that I am not
familiar with or am I just reading too much into the words and you are
just saying that the dependency will be removed? Sorry for a stupid
question. :)
Thanks for the tip regarding Mylyn Zest. It is definitely worth
investigating. It would be interesting to see how well it can handle
complicated graphs (like our component dependency graph without
transitive edge reduction).
- Konstantin
-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Nitin Dahyabhai
Sent: Friday, September 07, 2007 1:09 PM
To: wtp-dev@xxxxxxxxxxx
Subject: RE: [wtp-dev] The Big Picture
No, the source editors' dependency on modulecore is very small. Any
runtime dependencies on modulecore and facets in 2.0 should become an
optional dependency in 3.0, possibly very soon. There's no reliance on
the related artifacts already.
Also, isn't visualization of a graph such as this is exactly what the
Zest project does? There's a wiki page at
http://wiki.eclipse.org/Mylyn_Zest_Visualization showing a viewer that
lays out a graph based on a content provider, plus rooting around the
sources shows that it should support different connection styles.
There's a proposal (bug 164387) to move it from Mylyn's sandbox into
some part of the GEF project, which would make it even easier for us to
use (assuming it ever leaves the inbox).
---
Nitin Dahyabhai
Structured Source Editing
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
