4 ms·
Author here. This is completely correct. But my main motivation for creating this was getting something working in a easy and portable fashion. Basically I wan
by josteink 12y ago
Author here. This is completely correct. But my main motivation for creating this was getting something working in a easy and portable fashion.
Basically I wanted to have something I could share with my colleagues and which could be accepted as "documentation" if checked into source-control. For that using a dialect of diagram-generators which nobody else can get working isn't going to cut it. Those solutions are hardly "out of the box"-friendly, and even less so portable.
This package relies 100% on websequencediagrams.com, and for that it is restricted by whatever the website supports.
But because of that it's also 100% portable and should work out of the box on any machine, without any other prerequisites. And I think that is quite nice.
I just thought it was useful and wanted to share. If my needs are aligned differently than yours I'm not going to take offence :)
- ChristianBundy 12y agoTotally useful – I'd love to be able to use this offline, but I understand that that would probably be a much larger task. Thanks for building this and sharing!
- ChristianBundy 12y agoTotally useful – I'd love to be able to use this offline, but I understand that that would probably be a much larger task. Thanks for building this and sharing!
- ibrahima 12y ago> I just thought it was useful and wanted to share. If my needs are aligned differently than yours I'm not going to take offence :) I think there's a tendency here to nitpick everything that's submitted. Personally I'm just glad that you had an itch, scratched it, and then shared it with others. This looks like something I could use right now actually! And from this discussion I learned about PlantUML too. So seriously, thanks a lot and don't pay too much attention to the critics.
- nodivbyzero 12y agoWell done. Do you accept feature requests?
- josteink 12y agoThis isn't a full time project for me, but just something to scratch an itch: writing out big UML processes in a HTML textarea isn't my idea of an ideal editing process. It's hard to promise anything up front, but if you register an issue on the github issue-tracker I can at least consider it. I may like the idea and take on the challenge or I may decide that for me it doesn't seem worth it. But I do also accept pull requests :)