[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [science-iwg] January - New Eclipse Project Proposal
|
Tracy,
That's a good question. Let's consider that particular example.
The data structures in ICE are about organizing information in logical ways to process user workflows. Many of those structures implement our Component interface, which guarantees that the data can be identified, copied, observed, etc. It isn't entirely different than an EMFObject. The GeometryComponent is such a Component, but it doesn't actually describe its own geometry. The whole set of components make it easy to logically describe data in ways that scientists understand including collections of data, tables, matrices, meshes and so on. Some of them are self contained and some make use of external data structures from EAVP or GlazedLists.
The data structures in EAVP are purely about doing visualizations. So there are a lot of structures for CSG trees, etc. There is nothing like the Component interface.
So, ICE's data structures make use of the EAVP data structures to fill in the gaps. That's where they overlap.
I don't see the Components from ICE moving into EAVP because they use it; there is a one way dependency "down" to EAVP. But, the bundles can exist beside each other (and presently do) so that people could use them without requiring all of ICE. For that matter, keeping a CSG tree in a visualization project isn't ideal: it should be possible to use something like that without getting all the visualization/rendering code.
We moved all of the EAVP data structures out of ICE because we have a lot of requests to use ICE's visualization tools... just without ICE! ;)
I hope that helps. I'm happy to answer more questions and we can schedule a video conference if you want.
Jay
On Jan 29, 2016 8:01 AM, "Tracy Miranda" <
tracy@xxxxxxxxxxxxxxxx> wrote:
Jay,
I'm interested in the overlap between ICE and EAVP - I appreciate things are actively being developed at the moment so it may be more useful to talk about how you envision them down the road.
So understood they are both nothing to do with ndarrays, but for instance, in the example before you talked about a GeometryComponent being in ICE and the associated CSG tree being in EAVP. Would you see GeometryComponent moving into EAVP eventually? Just trying to get more of a feel of the types of things we are talking about.
Tracy
_______________________________________________
science-iwg mailing list
science-iwg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/science-iwg