The unwrapping of the onion has started by getting diagrams out of ArgoUML.
We may be left with core parts of ArgoUML that for some reason need to listen for GEF events but we can always wrap those with our own events as we do for the model subsystems. For now though, for me, this is looking too far ahead. Bob On 20 April 2011 12:46, Thomas Neustupny <[email protected]> wrote: > Hi Bob! > >> If we can isolate GEF in ArgoUML then it will gives us more choices in >> future to fix it or move away from it to an alternative. > > My naive view on this topic: GEF should be used in the diagram code only, so > by a new implementation of the diagram subsystem and diagrams itself, this > could be taken into consideration (isolating usage of GEF). > > Ah, maybe listening to GEF events is spread all over the codebase (outside > diagram code), right? > > Anything else in our codebase which depends on GEF? Persistence (PGML)? Known > modules? We could at least analyse the GEF dependencies and think about the > solutions that later could be implemented. > > Thomas > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2721763 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. > To be allowed to post to the list contact the mailing list moderator, email: > [[email protected]] > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2721766 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
