BuildAp 0.3

• Search for parts. Allow free text search for a part in parts library.
• Mapping of outpin and inpin parameters. New mappigs - Object[index]- Object[index], Objects[] to Hashmap, all parameters to Object[], all parameters to Hashmap, Hashmap element to Object.
• Code generation for deployment. After the development of the application for better performance the executable code can be generated with hard coded connectors.
• Make Buildap, Diagram Editor and SVG Editor modules available for Eclipse IDE.
• Unit Tests/Framework optimizations. Buildap framework is a critical part, which needs further optimization. Although before moving into optimization we need to develop complete unit tests to regress the existed functionality.
• Automated Part Tester. When part is developed then a developer may provide correct input/output sequences and then the tester can automatically test the part with the given inputs and outputs. It will try under different sequences to make sure it works independently of input firing order.
• Record/Play/Compare feature. It will record all execution (fired events) and then allow replaying again and comparing with previous executions. Will be useful for regression tests and also for performance tuning.
• Analyzers. Because the model is formalized, different analyzers, valuators and other tools can be used to improve productivity and quality.
• Multiple Views
• New Connectors (streams, distributed connectors)
• Generate project doc in html (similar Together/J) with navigational diagrams 
• SVG features to Nebeans DiagramEditor. Allow opening any SVG image and drawing diagrams using SVG as background. Allow usage of the SVG viewer features like zoom, convert to other formats, thumbnail view etc. When we remove DiagramEditor toolbar it will become a standard SVG viewer.
• Part Editor to draw symbols and add them to the library
• Runtime panels. DiagramEditor based VSCB runtime visualization – simulation, animation, visual tracing, and step mode.

BuildAp 0.2 ( released)

• Library panel and drag & drop from library to GraphEditor .
• Autolayout of diagrams.
• Nebeans VSCB tree views
• Basic Libraries complete and standardization. Parts Classification. We need to provide basic libraries complete enough to develop basic applications.
• Part Generation/Java IDE integration. When block and connectors were drawn, developer may need to develop a Java code to implement the box-and-pin functionality. Then it will generate a Java code skeleton with given pins and within the same IDE will allow to add Java code, will compile and integrate it into the model.
• Runtime Layering. It may need to have many runtime layers of the same diagram.
• XDoclet integration (generate config files)