Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343217 - [modeling] usage tracking for GEF diagram editing and navigation
Summary: [modeling] usage tracking for GEF diagram editing and navigation
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 0.9   Edit
Assignee: Miles Parker CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks: 351894
  Show dependency tree
 
Reported: 2011-04-18 19:28 EDT by Benjamin Muskalla CLA
Modified: 2012-03-13 09:11 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Muskalla CLA 2011-04-18 19:28:03 EDT
We need track user interactions with GEF based diagrams to handle the corresponding interaction events.
Comment 1 Miles Parker CLA 2011-07-11 20:56:32 EDT
This one is a bit confusing to me. Benny, as GEF is really an API level tool, there isn't a model component per se. So while we could track user interactions, we wouldn't have a model or any kind of artifact that we would associate directly with those that would give us a mapping back to the document. I mean, I suppose if someone had an editor part and we had a way to detect that that editor part had a GEF component then we might be able to discover the root edit part, but all of that is relying on a lot of runtime discovery, e.g. walking through the component hierarchy of any editor / view that is open. But I think I might be missing the point of this task..
Comment 2 Benjamin Muskalla CLA 2011-07-12 06:32:17 EDT
I wonder if this should happen automatically. I'd rather think there will be some special API in GEF that allows GEF-based editors to be "Mylyn supported". Not sure yet - let's discuss this in our next call.
Comment 3 Miles Parker CLA 2011-07-12 13:39:39 EDT
(In reply to comment #2)
> I wonder if this should happen automatically. I'd rather think there will be
> some special API in GEF that allows GEF-based editors to be "Mylyn supported".
> Not sure yet - let's discuss this in our next call.

Yes, I was really walking through the complexities as a justification for not doing it. I think the API approach makes the most sense by far. We might be able to provide a relativly simple extension point or something that allows people to say, "here's my GEF model, here's how to associate it with a resource, and here is my root part that implements a mapping between the edit part and it's unique persisted path." Something like that. Don't know if this is too generic / ambitious for now, but it might be worth thinking about a graphical editor specific abstraction layer for these kinds of mappings. An important question to ask always is "will anyone actually implement it"? But if it were simple and we had some working implementations..
Comment 4 Miles Parker CLA 2011-07-21 18:00:23 EDT
This is basically complete except for packaging and of course submission. Turned out to be not difficult and pretty general solution. Hopefully it won't even require GMF.
Comment 5 Miles Parker CLA 2011-07-21 18:44:33 EDT
Marking as resolved..