Hi,

Here are a few of my understandings, please correct me if I am wrong.

1. WPFDiagram is similar to JDiagram in the functionality it offers.

2. JDiagram is written in Java and WPFDiagram against the .Net Framework 3.5

3. JDiagram can function in a browser in the form of an applet, and WPFDiagram should be able to do that in the form of XBAP (XAML Browser App)

4. If I host WPFDiagram as an XBAP, the user who sees this diagram will need the entire .Net Runtime for 3.5 installed on his machine.

Have you even explored the option of Silverlight 2.0 because that also comes with a stripped down version of the .Net Runtime and provides quite a powerful Graphics environment.
I realize it is not even Beta yet, but maybe you are confining the WPFApp to the features that would also be available in Silverlight 2.0 (when it releases), and you would have a SilverlightDiagram also with very smooth transition from WPFDiagram. A person with a MAC will be able to view the diagram.

Thanks,
Praveen

With Silverlight 2.0 in Beta 2, do you have an more information on your direction for a silverlight control? Will is be a part of the WPFDiagram product or will it be a separate product. Any release dates available?

We are currently looking for a silverlight solution. We would want to generate the diagram on the client using data sent from the server, but the user would not "draw" a diagram.

We would use a entity/relationship diagram. Where two entities might have multiple relationships, so multiple edges between nodes would be a requirement. We would also need the ability to respond to clicks on an entity to redraw the diagram with new data from the server on the clicked entity.

Thanks

Hi

WpfDiagram 2.0 was released last week (congrats!)
however I don't see any obvious support for Silverlight in the downloaded zip file.

Trying to add an assembly reference to it in a Silverlight project doesn't work.

I started down the path of trying to rebuild WpfDiagram sources as a Silverlight class library but there are a number of BCL dependencies missing from Silverlight, e.g. System.ICloneable, System.Collections.CollectionBase etc.

is there an ETA for a Silverlight-compatible release?

thanks

yes I would like to try the Silverlight edition.

if you will later have DiagramNodeAdapter support working sometime after, I can work on porting other parts of our WPF app code, currently I depend heavily on databound custom WPF controls to display for each node

thanks!

We plan to release a Silverlight version with a very basic set of features in the next month or so. Next, we'll implement a Silverlight front-end for our Netdiagram ASP.NET control, which is what I'd recommend for using in web apps. This should be available in 2-3 months. The Silverlight control will be also available with our WPF product.

A new build of diagramlite.dll is available here:
https://mindfusion.eu/_beta/diaglite.zip

- now the main namespace is called MindFusion.Diagramming.Silverlight;
- the Bezier links style has been implemented
- the graph layout classes has been ported
- now the control is built against the official Silverlight 2 version

Stoyan

Hi,

We expect all features of the core component to be available after a two or three releases. We do not plan to implement SVG/Visio/PDF import and export components specifically for the Silverlight version, but instead rely on the ones coming with our ASP.NET package, where the Silverlight component will be available as a front-end.

As for limitations, Silverlight does not provide a low-level access to the WPF rendering system, but expects the component’s UI to be implemented by composing other UIElements. The standard item types in the full WPF version are more lightweight, being Visual objects that override the Render method. In the Silverlight version item types are a composition of UIElements such as Grids, TextBlocks and Paths, and are more resource-intensive. As a result the Silverlight version will probably work a bit slower when displaying a lot of items.

Stoyan

We'll release a beta version with installer, help file and samples next week. For the time being, you could report bugs here.