Quote:Is there an advantage to one option or the other (building the diagram on the server and streaming to the browser vs building it in the browser using javascript)? Performance implications?
I suppose building it on the client will be much less taxing to your server. You can embed in the page only the data you need (e.g. as a string array, XML or JSON) and then parse it on the client and create the corresponding diagram elements. Otherwise on each GET request the server would have to load a bunch of Java Graphics and Swing classes instantiated with a Diagram that would not be used.
Quote:API limitations?
You'd have to do a lot of calls to the ScriptHelper class if you build the diagram from JavaScript, and it might still not cover all APIs (we are adding them on demand). You could instead create your own applet that wraps a DiagramView and implement service calls, data parsing, etc in Java.
Quote:We'd also like it to be visible in all browsers and mobile devices. Does JDiagrams make this possible?
You cannot use Java applets on smartphones AFAIK. For them you could export the diagram as a bitmap image on the server and build a corresponding HTML image map (using the HtmlBuilder class) whose AREAs will let you detect clicks on the nodes.
If you are not tied to Java on the server side, check our ASP.NET MVC / HTML5 Canvas based control -
http://mindfusion.eu/Forum/YaBB.pl?board=mvcdg_disc;action=display;num=130210032...The HTML5 canvas element should work at least on iOS and Android.
I hope that helps,
Stoyan