Hi Bob, How would this work if you were editing the code in an IDE and re-imported it into your project? Wouldn't that still break references in your model? Wouldn't you expect it to break those references? I guess in that case when you generated the code you would end up with code that wouldn't compile but could be easily fixed. One possible solution to that would be to support simple refactoring, like method renaming and method signature changes, but that would probably take longer to implement.
My thought is that something like this would be small enough in scope that someone could implement it in a weekend and contribute something that makes modeling easier. At a first pass though, it would be useful simply to support green field modeling with this. Mark On Thu, Sep 1, 2011 at 9:31 AM, Bob Tarling <[email protected]> wrote: > On 1 September 2011 17:11, Mark Fortner <[email protected]> wrote: > > Hi Bob, > > My thought is that the "instant reveng" function would basically replace > the > > model for the class that you're currently editing, rather than trying to > > incrementally update individual operations. > > But what about any other model elements that refer to the existing > oprerations? > > If some of those operations you "replace" but are really the same then > you lose those references. > > Bob > > ------------------------------------------------------ > > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2833988 > > 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=2833989 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]]
