> I can't reply to all the points but as far as I can see most of the points > seem to be addressed by our desire to move to the eclipse framework.
I had the same thought as I read through this thread. > Work has already started in argoeclipse but so far this is mainly I > think building a presentation layer on top of ArgoUML. Maybe we should > start to discuss other aspects of RCP such as undo and discuss when > core ArgoUML should start using that directly. So far this work has mainly involved fitting the current UI into Eclipse. Recent work has involved integrating ArgoUML with some of the views provided with the Eclipse platform, and allowing certain aspects of ArgoUML to be extended via Eclipse's extension-point mechanism. The Eclipse undo framework is part of the org.eclipse.core.commands plug-in, which in turn depends on org.eclipse.equinox.common - ArgoUML could build its undo/redo support around Eclipse's framework by using these two plug-ins/jars. A more detailed discussion on this should probably occur on its own thread. Brian On Mon, Aug 25, 2008 at 8:42 PM, Bob Tarling <[EMAIL PROTECTED]> wrote: > There is a great deal said in this thread, I really think you do > better with more threads of discussion and less scope in each. I can't > reply to all the points but as far as I can see most of the points > seem to be addressed by our desire to move to the eclipse framework. > > Work has already started in argoeclipse but so far this is mainly I > think building a presentation layer on top of ArgoUML. Maybe we should > start to discuss other aspects of RCP such as undo and discuss when > core ArgoUML should start using that directly. > > The alternative is that the argoeclipse becomes the new ArgoUML with > functionality gradually migrating across into that project and hence > into the eclipse framework. > > The problem I have is when or whether to stop with core ArgoUML to > learn the RCP framework and then begin helping where I can in > argoeclipse. Now is certainly not the time though, once we have the > next release out the door I can review that. > > In the meantime core ArgoUML is definitely improving in features and > in structure. > > We are a small team and none of us are sponsored to work on this > project. It must fit around our personal lives and working lives. For > me personally and maybe others here that does make keeping to a > roadmap difficult as I must often prioritise things above my work > here. > > Regards > > Bob. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
