Publish code used by websequencediagrams

To make it easier to compile a set of diagram in a folder without collecting them in a document or html page, allow the generate graphic to include a textual title at the top of the sequence diagram.

Currently it takes too much time to create sequence diagrams of large application due to dependency on internet. It would be better to create desktop application that will be clone of this applicaton

The Sequence Diagrams are great and I agree, I find myself using them most often - mostly for conveying initial design architecture and for documentation purposes. But I also use the Class Diagram very often for documenting code.

This is not standard and takes space

In order to have something like in the diagramm

1 Authentication request
2 Authentication response

Scalable Vector Graphics for higher quality output. SVG is a quite simple but powerful XML-based format that may even be easier to generate than PNGs.

Sometimes I need to highlight a particular transition, and colors might help.

A command line version allows use of any editor. The errors shown should be a form that Visual Studio and other dev tools will recognise when executing the build diagram.

In VOIP sequence diagrams after the call has been set up there will be bidrectional flow of audio/video packets between at least 2 of the objects in the diagram, this is often shown with a double line with RTP written in between the two lines and a big arrow at each end

As you know, the sequence diagram may contain different participants which come to life at different times. But in this tool, all the participants are shown as if they all came to life together. This leads to confusion.
Could you make a provision for a participant to come to life later in a sequence diagram when it is initialised.

IT would be nice to have some similar way of adding text and generating a diagram for actors and use cases.

It requires fewer steps than copying and pasting all the time

Allow for specification of open or closed arrows to distinguish synchronous and asynchronous requests and responses.

Loop spans across all the participants, which is not required all the time. So looping across limited participants is required

If object is activated when it is already active, draw nested activation bars, where the latest is a bit shifted from the previous. This can be turned on in Rose.

There is absolutely no reason to share your code. Let those lazy developers think of their own great app, instead of thieving yours. They just want to copy it and steel this great idea. Keep your guards up there!

there is support for alt/else, opt and loop. Could you also add for 'par', 'region', 'neg', 'ref' and 'sd'.

For very long diagrams the lines look bad.