From DevRiot for .Net and Java
The test trees support dynamic handling of a most of Java collection classes.
The snippet editor will help feed the Java engine (or the C/C++ engine) the missing bits of information. It is context sensitive and allows the user plenty of flexibility: define arrays, nest generic types (when in Java perspective)
DevRiot for Eclipse will have the following contribution to the Java perspective:
Currently if the eclipse view is resized, the rest of the widgets in it do not resize accordingly.
In order to integrate DevRiot seamlessly with Eclipse, decorations and other Eclipse patterns will be used to provide a more visual experience to the user. In this case note the decorator signaling the value "1" as a valid new test id.
The popup menus are wired. We will add keyboard shortcuts to avoid the long commute in the pop-up menu
The Eclipse glue code is mostly well behaved. It is attached to the Java and PDE perspectives. Will use some of the Eclipse facilities this time to reduce the size of DevRiot even more. Smaller and using NIO means more phones and devices from we could run
The test trees are implemented using TreeViewers and JFace in general. This should yield a more pleasant user experience.
Something missing from the previous java version was an auto-completion feature that reduced even further the time and test development costs. Here it is, providing on zoomed in interface implementors:
The behaviour and looks of DevRiot's views are more in tune with Eclipse's.
The behaviour and looks of DevRiot's views are more in tune with Eclipse's (II)
Collection handling and validation just became part of Riot's logic:
The plug-in architecture has been greatly simplified. A lot of useless code has been removed so Criot (Riot for C/C++) can fit in seamlessly.