Page Comparison

• supports dynamically negotiated features
• supports stream compression
• supports TLS
• multiple serialization formats possible (currently there are two: NGP and Java object serialization)
• supports easier setting of timeouts (connection parameter timeout)
• timeout handling is now somewhat more clever
  • the old NET/GMPP protocol also runs into a timeout if it isn't able to send/receive ping/pong in time, so it would close the connection even if still data is sent, this is something the new protocol avoids
• the serialization itself is genereated via an EMF model, using Acceleo, so adding new fields is pretty easy

• because there is no decent chart for displaying timeseries based on SWT, we had to implement one, ourselves
• the chart itself is separated from any openSCADA specifics, so it is usable in a totally different context
• of course there are some abstractions which make integration in any openSCADA context easier
• openSCADA timeseries based on data items or hd items are configured via an EMF model
• the chart can be updated in real time
• supports multiple axis, multiple timeseries

• integration with Draw2D, there is also already a widget in DAKARA to integrate charts in a DAKARA VI-View

• openSCADA has a predefined style for alarms, which is now changable to a different style set, also in a client the style can be changed by the user

• some minor usability tweaks 
  • double click opens connection
  • configuration import dialogs remembers last import file
  • connection tree has some additional nodes where connections are sorted by URI, protocol, ...
• JFreeChart removed, replaced with our own INFINITY implementation implementation
• summary alarm explorer
• connection statistics (status, send/received bytes)

• Added example for the Eclipse Democamp, based on our Arduino sample setup.
• the source code for this demo will be found
  • here: http://git.openscada.org/?p=org.openscada.tauri.git
  • and here: http://git.openscada.org/?p=org.openscada.oxygen.git

Not really satisfied with the existing documentation tools, we build our own DocDocDoc which is of course better than everything else

Some features are:

• automatic extraction of system properties from java code (via JDT)
• automatical gathering of license information
• bundles are documented within, these documentation snippets are then gathered to a large document
• extensible
• only renderer at the moment is HTML, but there will be more

The first (obviously not very complete) version is found here: http://download.openscada.org/documentation/R/1.0.0/html/system/