Hello Mark and Bob and all...
This is a very interesting discussion on the distinction between Notation
and Code Generation/Reverse Engineering.
>From my experimenting with 0.32.1, it seems that the code generation for
Java does not include documentation of parameters to operations in the
source tab or in the generated source so this is one of the first things
that should be added to achieve this. For SQL and C++ it is not included
either but for PHP4, PHP5, and CSharp it is included.
I also can't get updating from edits in the diagrams to work for the Java
Notation. It works for the UML Notation.
If we implement the on-diagram editing that Bob is advocating, that would
mean to improve the Notation to work better with java, allowing also
documentation of attributes, operations and parameters. The question is how
and if documentation shall appear on the diagram. I assume some hovering/F2
solution will be necessary not to fill the diagram.
Implementing the possibility to edit and then reverse engineer directly from
the source tab is also an interesting option with some challenges that has
been identified.
The biggest challenge is probably to get the two approaches to use the same
implementation so that we don't have to implement this parsing twice for
every language. I am not sure how far the work with Notation by Michiel has
come in this area.
/Linus
Den torsdagen den 1:e september 2011 skrev Mark Fortner:
> 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]<javascript:_e({}, 'cvml', '[email protected]');>
> > wrote:
>
>> On 1 September 2011 17:11, Mark Fortner
>> <[email protected]<javascript:_e({}, 'cvml', '[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] <javascript:_e({}, 'cvml',
>> '[email protected]');>].
>> To be allowed to post to the list contact the mailing list moderator,
>> email: [[email protected] <javascript:_e({}, 'cvml', '[email protected]');>
>> ]
>>
>
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2834502
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]]
