• Layered Graph Layout - Added support for orthogonal edge routing, with integrated bus spacing, which allows for the generation of very nice looking orthogonal graph drawings. Added support for node alignment options, which help you specify the relative alignment of nodes inside the layer. Added support for different node ranking policies. Added support of in and out plug spacing, which work very well with bus spacing and further increases the drawing readability.
  
  
• Dock Layout - Added support for different filling and fitting modes.
  
  
• Orthogonal Graph Layout - Added support for plug spacing.
  
  

• Improved browser compatibility.
  
  
• Extended client side JavaScript class interfaces.
  
  
• The Nevron Instant Callback technology was added as an alternative to the MS AJAX Callback, which greatly improves the performance of the web controls.
  
  
• Configurable event queuing at client side makes mixing of mouse move, mouse click events and auto refresh possible and native to the web site visitors.
  
  
• Improved behavior of the web controls on communication breakdown; a wait message is displayed and the server is queried periodically for availability; when the connection with the server is reestablished, the web controls continue normal operation.
  
  

• Food shapes
  
  Included are 22 shapes related to food.
  
  
• Weather shapes
  
  Included are 26 shapes related to weather.
  
  

• New Layouts
  
  Graph Layouts
  Layered graph layout - hierarchically arranges graphs.
  Barycenter graph layout - implements the barycenter layout method.
  Spring layout - classical layout, which simulates spring and electrical forces. Different coefficients (spring stiffness, length, electrical charge) will be specifiable on a per object basis.
  Symmetrical layout - implementation of the Fruchertman and Reingold force model. Tries to achieve a symmetrical drawing in which the edges are equal in length.
  Custom force directed layout - lets you define your own set of forces, or use the currently provided forces.
  
  Common for all force directed layouts are the following constrain forces:
  
  Magnetic field force - impose an orientation of the edges. Magnetic fields can be combined. Supported are parallel, Polar and Concentric magnetic fields. Edge magnetization (bidirectional or unidirectional) can be specified on a per edge basis. Bounce back force - tries to additionally push overlapping vertices apart.
  
  Tree Layouts
  Layered tree layout - layouts the tree in layers. Tries to improve the breadth tree size.
  Compact tree layout - layouts the tree by improving both the breadth and depth tree sizes. Does not obey to layering in order to achieve compact tree drawing.
  Tip-over tree layout - layouts the parent children horizontally or vertically. The parent children arrangement is specified on a per parent basis.
  Radial tree layout - layouts the tree layers in concentric circles.
  
  
  

• Pages
  
  The diagram component will support pages. Each page will support different logical and display units, layers etc. The page will be controlled by a formula sheet.
  
  
• Formula Shapes
  
  Nevron diagram will support formula shapes. More details on this feature will be published additionally.
  
  

• Simple Network shapes
  
  Tailored to meet the requirements of the developers, which want to display large network diagrams, which need a low level of detail for the individual network particles.
  
  
• Electrical Symbols shapes
  
  Added were many electical symols shapes, which will facilitate the display of simple and complex electrical schemes.
  
  
• Floor Plan shapes
  
  These shapes target the users, which need to display floor plans. The floor plan shapes are defined in their actual size.
  
  
• Country Flags shapes
  
  General purspose shapes, which represent country flags.
  
  

	[RectangleF in XML]
	<Bounds>
	<Location>
		<X>0</X> 
		<Y>0</Y> 
	</Location>
	<Size>
		<Width>220</Width> 
		<Height>220</Height> 
	</Size>
		<X>0</X> 
		<Y>0</Y> 
		<Width>220</Width> 
		<Height>220</Height> 
	</Bounds>
	[NRectangleF in XML]
	<Bounds X="0" Y="0" Width="220" Height="220"/>
	

• Implemented was support for WebForm views. In the context of WebForms the interactive viewing of DOM documents is achieved with WebForm views, which support many image output formats as well as HTML image maps and postback events
  
  
• Implemented were shape factories, which can help you easily create any predefined shape. Added were more than 180 predefined shapes. All of them are nicely grouped in thematic shape factories
  
  
• Added was support for stylesheets, which greatly minimize the effort needed to apply consistent styling to your diagrams
  
  
• Implemented were many graph and tree related algorithms (graph and tree traversal, spanning trees, checks for cyclic, connected graph etc.)
  
  
• Added was support for circular arc primitives
  
  

• You can now instantly convert any 2D shape to 1D shape and vice versa. Plugs are automatically created/destroyed
  
  
• Elements now store most of their properties in property bags, which minimizes the memory footprint of the diagram
  
  
• The shape labels, ports and control point collections are now optional. You can create and destroy them as you see fit. In this way the diagram can further be lightened
  
  
• Improved was the way in which elliptical arcs are defined and edited
  
  
• Graph management was decoupled from shapes. You can now specify on a per shape basis whether you want a shape to be treated as a logical graph part
  
  
• Groups are now much easily created - just add the shapes in their shapes collection
  
  
• Composite shapes are now much easily created - just add the primitives in their primitives collection
  
  
• The composition and decomposition now preserves the local style formatting
  
  
• Added was support for primitive shapes. These are shapes, which aggregate a single primitive model and whose behavior is influenced by the primitive they aggregate - for example rectangle shape, ellipse shape, polygon shape etc.
  
  
• Added was support for form preservation of 1D primitive shapes, when you modify their start and end points
  
  
• Added was support for 22 different modes in which aggregate models can scale models they aggregate (for example the way in which shapes are resized in groups). The most commonly used are CartesianScaleAndReposition, RepositionOnly and AffineScale
  
  
• Added was support for element abilities and protection
  
  
• Added were several new batches. Most of the operations, which views and commands perform with document content go through batches
  
  

• You can now globally specify what types of trackers must be created for the selected shapes (for example disable the creation of pin point trackers)
  
  
• You can specify whether reflexive and partially disconnected connectors should be created
  
  

• Optimized was the initialization performance of documents
  
  
• Optimized was the update performance of documents
  
  
• Optimized was the rendering speed (especially of stroke elements with image filter shadows)
  
  
• Optimized was the hit test speed
  
  
• Optimized was the masters image generation
  
  

• Fully Extensible - you can subclass any DOM object and override its behavior
  
  
• Interface Based Framework - DOM object features are neatly grouped in interfaces. The framework is in this way decoupled to a large extend from the actual object types in works with
  
  
• Hierarchical Scene Management - DOM objects reside in hierarchical scenes
  
  
• Stencils - DOM objects can display reusable content from stencils. Currently provided are arrowheads and point stencils, which can host any model. Stencils are specially optimized to display predefined content
  
  
• Documents - documents are assembled from stencils, layers and models and can be displayed by multiple views. Currently there are drawing and library documents. Drawing documents support custom drawing scale configuration
  
  
• Measurement Units - currently supported are three measurement unit systems: GDI+, Metric and English, with complete set of the respective measurement units. You can also plug your own measurement unit systems (for example extend the component to support Japanese measurement units)
  
  
• Layers - documents content is neatly organized in layers
  
  
• Styles - the visual appearance of all DOM objects is controlled via inheritable styles
  
  
• Permissions - any action, which modifies DOM objects, must have the right permissions to do so. Permissions are also inheritable
  
  
• Models - models are the primary diagram building blocks. Models can be freely transformed
  
  
• Primitive Models - implemented is a complete set of graphics primitives (strokes, closed figures and texts)
  
  
• Aggregate Models - aggregate models are assembled from other primitive and/or aggregate models
  
  
• Shapes - shapes are aggregate models, which represent logical abstractions. Shapes can be involved in complex relationships. Shapes can have multiple ports, plugs and labels. Since any model can represent the geometry of a shape, shapes can even be nested
  
  
• Graph Management - the DOM provides the necessary means to help you easily manage directed and undirected graphs. In this way the DOM is a powerful tool for graph drawing of any type
  
  
• Groups - models can be grouped and manipulated as if they were a single model
  
  
• Routing - models, which represent routes can avoid other models, which represent obstacles. Supported are Poly and HV routing
  
  
• Persistency - documents can be saved in XML, binary and SOAP format
  
  
• Printing - documents can be printed on single or multiple pages. Implemented is built in support for print preview
  
  
• Image Export - an entire document or only portions of it can be exported to image of any type (JPG, PNG, BMP etc.). For documents defined in absolute measurement units (e.g. inches, millimeters etc.) you can also specify the target device resolution (helps you generate ready to print images)
  
  
• History - the entire DOM API is protected by history. Any property or method, which modifies the DOM objects state records history. The history can contain an unlimited number of actions. History actions can be grouped in transactions. Transactions can be committed or rolled back. Also nested transactions are supported. The history is implemented as a service so you can easily override it, suspend or lock it
  
  
• Entities - implemented is a large amount of entities, which facilitate batch operations on logically connected sets of nodes. Currently implemented are entities for basic layouts, transformation, translation, replication, format and ZOrder operations
  
  
• Event Handling - all events are fired from an event sink service, which provides you with the ability to consistently intercept all types of events regardless of the diagram you work with. Interactivity events (mouse, keyboard and drag drop events) support event bubbling