More SEQUENCE posts
January 20, 2004
SEQUENCE - Improved Examples and Help
plus, of course, some bug fixes. Embarassing though it is to admit, working through putting together the examples, which are available under the Help menu in SEQUENCE, showed up a few problems that I needed to fix. As well as adding lots more examples, and improving the help I also deprecated the old "LISP style" syntax for describing sequence diagrams. You can still get access to it by passing the --offer_parser_choice option on the command line, but by default you now only get the more Java like syntax.
The source code is in sequence_src.jar and an executable version is available in sequence.jar. To run it just type java -jar sequence.jar. You'll need a 1.4 or better Java version.
Comments
Hi,
I am still using sequence more and more.
I have a suggestion for an improvement (not easy I'm afraid) to support parallel execution.
In brace syntax, the idea is to define:
Obj.Oper (Args) -> Stat {
Obj1.Oper...
&&
Obj2.Oper...
}
Graphically, this would do something like (or anything better):
Obj Obj1 Obj2
| |
| |------------------------------->+-+
| | | | |
| |------------>+-+ | |
| | | | | |
...
| | | | | |
| |<------------+-+ | |
| |<-------------------------------+-+
| |
Regards
Posted by: Pascal MALAISE on February 24, 2004 07:49 AM
Hi Alex. Wonderful tool, I was able to create my first diagram only seconds after downloading Sequence. Support for asynchronous messages/multiple threads, as already requested by others, is the only feature that i sadly miss.
Possible bug: I changed the "vertical gap between method executions" preference, but it didn't seem to affect the display. Same with the "show return types" checkbox: checking/unchecking made no difference.
And a small suggestion: mentioning the default return type "void" seems superfluous. I think the diagrams become clearer when methods without return values simply end in unlabeled dashed arrows towards their caller.
Otherwise: great tool.
Posted by: Martin on March 15, 2004 07:54 PM
Great tool -- just what I need and the text input is so much better than futzing around with drawing. Really great stuff.
a few comments
1. Would like to be able to say not to show a return line on a method by method basis. I guess if I don't give a return, I'd rather there be no line and no "void". If I want void, I'll put in -> void.
2. You are disabling "Save As..." when I save and until the next change -- but I might want to save As... a saved/unchanged sequence.
3. Export makes a PNG, but I only know that because I hex edited the resulting file. A hint in the menu (Export to PNG) or in the save as dialog (with the extension) would be great.
Posted by: Lou Franco on May 4, 2004 06:45 PM
Alex, I will echo the praise of your tool. However, I believe there is a bug in the latest version. It appears to skip the first object in the call sequence. I'm sure this is easy to fix and the older version works great (even thought it doesn't have a good a help system.)
Thought you'd want to know.
Joe :-)
Posted by: Joe Angerer on May 28, 2004 03:11 PM
I'm using sequence v7, and I'm having a nasty bug that I can't seem to resolve. I'm creating several .txt sequence descriptions, and loop through a script to generate the pngs headlessly. What I've discovered is that something usually goes wrong with the headless generation. The only example that seems to generate successfully is the "all" example. The one labelled "Conditions", for example, is generating a 41x31 pixel png when I run headless. Here is the "Conditions" example:
// Method names can be preceeded by a condition in [ and ]. This must
// follow any *. Use *[condition] for repeating the call while a condition
// is true and [condition] for calling the method once if a condition is true.
objectOne.methodOne {
objectTwo.methodTwo(foo, bar) -> value {
objectThree.*[while != null] methodThree(value) -> anotherValue
objectFour . [> 10] methodFour()
}
}
This diagram will generate correctly in the interactive version, but I'm looking to generate headless. Thanks for any suggestions! I haven't sat down and tried to figure out what is being done differently in headless vs. interactive modes.
Posted by: Mark on July 12, 2004 11:59 AM
hi alex! tx a lot. a really fine tool. exactly what i was looking for.
i already made some bugfixes & changes - "Show Return Types" and "Vertical method execution gap" now work and i did a hack to allow "sorting" objects/classes. if you're interrested just let me know.
Posted by: oaky on July 18, 2004 08:26 PM
i want an examples about serries and sequnce
Posted by: salem on May 9, 2005 02:41 AM
Post a comment