Bob and I discussed about this and we think that some issues are blocker in sequence2 before a release, but we can do that work into the argouml trunk.
Switching from one to other in the sequence diagram create actions will be simple, so if the work is not stable enough just before the release we can easily switch to the old implementation for the release. So if everybody agrees, I'll start the merging. On 11/28/07, Bob Tarling <[EMAIL PROTECTED]> wrote: > Hi all > > I'd previously suggested the replacement sequence diagrams are not > merged until we have a migration provided from the old diagrams to > new. > > I've rethought that. > > I see no reason why we couldn't merge the sequence diagrams now and > have the old and new diagrams side by side for some time. > > The new diagrams are defined in their own separate package and so the > two diagrams can live side by side in the same project. > > All we need to do is have the new sequence diagram button create the > new style and have no way to create the old style sequence diagrams. > > We still need to convert old style diagrams at some stage so that they > gain the benefits of the new ones and we don't have extra code to > maintain. But I don't think that need should cause any delay in > allowing the user to create new style sequence diagrams. > > The only difference I'm thinking when we bring across is to have this > new diagram as a separate subsystem under src and repackage as > org.argouml.sequencediagram > > Any thoughts? > > Bob. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Christian López Espínola
