This sounds useful by maybe from some popup dialog rather than the source tab.
This is most useful for adding new operations and maybe the dialog should be restricted for that usage. If you also used this to edit the properties of an existing class (which is what the source tab would show you) then it is difficult for a multi-line editor to determine what operations were renamed, added or deleted during that edit. Editing one operation at a time makes it clear that the operation is the same operation with the same uuid even though it may have had its name changed or parameters added or removed. I was hoping we could improve on-diagram of editing of methods (or anything in a compartment box) by the following method which would be similar to navigating through and editing filenames in a directory using windows explorer. To select an operation click on it and it becomes highlighted as current. Pressing F2 on an operation puts it into edit mode - enter accepts change (esc cancels) Using the up/down keys when not in edit mode should possible the selected operation (and maybe even move to the next compartment when applicable). Further to this I thought pressing enter on an operation when not in edit mode will create a new operation under the selected one and place you in edit mode on that. This means having typed in a new operation pressing enter twice allows you to type in the next new operation and rapidly enter one after the other. Bob On 1 September 2011 15:46, Mark Fortner <[email protected]> wrote: > I was working on a model yesterday, and specifying method parameters for the > umpteenth time, and it occurred to me that there must be an easier way of > doing this. I create a class, click on the class to create the operation, > enter the operation, look at the operation's properties, click on each > parameter in turn, click on the Documentation tab and enter a description of > the parameter. > I started thinking, what if you could simply open the the Source tab, and > enter the text of the class directly. When you were done, you click the > reveng button and ArgoUML would reverse engineer the class for you. Of > course you could do this in your favorite IDE and bring it into ArgoUML, but > then you'd be going back and forth between your IDE and ArgoUML, and it > would be nicer if you could do it without leaving ArgoUML. > The source tab wouldn't really need to support much in the way of editing, > except perhaps importing classes that your refer to. The only other > fly-in-the-ointment is that reveng doesn't seem to support inner classes, > annotations, and generics. I'm not sure about varargs support, but I guess > if it doesn't support most of the Java 5 language constructs then it > probably doesn't support varargs. But assuming that these issues can be > dealt with, it would make it a lot easier and faster to create class > diagrams (and class diagrams seem to be what most UML users spend their time > creating). > Any thoughts? > Mark ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2833975 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]]
