| Plans on Graphiti future? [message #732774] |
Tue, 04 October 2011 11:24  |
Eclipse User |
|
|
|
I've been coding quite a bit lately modifying Graphiti sources, changing some ot its architecture, and I'm wondering where I should be aiming... My changes are motivated partly by my own needs, but also by the desire to make Graphiti more cleanly extensible (in particular, I intend that alternative diagram+model storage scenarios - eg, diagram and model in separated resources, or model-only persistence- can be supported out of the box, or with clean classes extensions), and I'm pleased with my (partial) results, but the truth is that my changes imply some relevant API changes: for example, I've removed the DiagramEditorInput class and introduced a DiagramProvider instead; the EditorInternal is now abstract, the DiagramEditor and the DiagramBehaviour are intended to be extensible, etc.
So, I'm reaching a point in which I must make my mind, whether I resign to maintain my own "private fork" of Graphiti, or what. I really like Graphiti, I think it has a lot of potential; of course, I'd like to contribute to Graphiti, but I know very little about the Graphiti development team processes and plans (I'm not even sure if this is the right place to ask). In particular, I wonder if such architecural changes (which require careful consideration and that will break some things, at least for users that have introduced dependence on internal code) are potentially welcomed or rather out of the question.
Is there some development roadmap or discussions in this regard? Graphiti is approaching a version 1.0.0, and (though I'm not sure how relevant that numbering is), I think it's the appropiate time to discuss this. I suspect that there are quite a few users that are touching internal Graphiti code for its own needs (current Graphiti docs seem to admit that the api is half-baked, in that there are many internal classes/methods that should be not modified or even called from the outside, but at the same time it's often necesary to do that in order to adapt Graphiti to user's needs). This is not a nice state of affairs, will make things more painful to change-polish later. Any comments?
|
|
|
|
|
| Re: Plans on Graphiti future? [message #734866 is a reply to message #734357] |
Mon, 10 October 2011 04:20  |
| Eclipse User |
|
|
|
Great to hear you're interested! Interest and willingness to learn are
surely a great foundation...
Regarding your question: thhe dependency to core.resources was only in the
repositoyr for a short while, as we tried to get our build with the new EMF
2.8 to work; it's gone again by now and Graphiti 0.9.0 works again against
Indigo.
Michael
|
|
|
Powered by
FUDForum. Page generated in 0.34592 seconds
Home
I'm certainly interested in contributing to Graphiti. Perhaps currently I don't know enough about the whole framework and the underlying platforms (I'm very novice at EMF -and Git- and I have a rather cursory knowledge of GEF - and I'm not very strong at the whole Eclipse stack), but I'm always glad to learn. I will soon post some thoughts and doubts about what I've been coding and musing on (related to the DiagramEditor, mainly).