1 / 21

Blaise NG

Blaise NG. First glimpse. Key issues in current system. Language enhancements Layout Unicode. Consequences. New parser and IDE New meta files New runtime system (DEP). Research. Platforms IDE / Parser. Development platform. The platform that the Blaise developers use Choice .NET.

lawrence-ferguson
Download Presentation

Blaise NG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Blaise NG First glimpse

  2. Key issues in current system • Language enhancements • Layout • Unicode

  3. Consequences • New parser and IDE • New meta files • New runtime system (DEP)

  4. Research • Platforms • IDE / Parser

  5. Development platform • The platform that the Blaise developers use • Choice • .NET

  6. Design platform • The operating system where the Blaise development system will run upon • Choice • Windows, using .NET framework 3.5

  7. Runtime platform • The operating system where Blaise instruments run upon • Choices • Windows, with .NET 3.5 • Browsers, with Silverlight 2.0

  8. IDE/Parser • Microsoft Visual Studio Extensibility (VSX) • Actipro Components • DSL tools • Gold Parser • ANTLR

  9. Phase 1 • Scope • Datamodels • New control centre • New source files • New parser • New meta files • Layout • Compatibility

  10. Phase 1: Datamodels • Focus on datamodels • No Manipula/Maniplus • No CATI • No additional tools (Bascula, Delta)

  11. Phase 1: New Control Centre • Using Actipro components • Flexible • Reinventing the wheel  • Integration with new parser • Source Code Editor • Graphical Datamodel Designer

  12. Phase 1: New source files • New format (.blax) • SQLite database • Can contain main source file as well as include files • Can contain additional information

  13. Phase 1: New parser • Using ANTLR • Define grammar of the Blaise language • Not very easy • Some small changes to the language (no layout statements anymore)

  14. Phase 1: New meta files • New format (.bmix) • SQLite database • Extensible

  15. Phase 1: Layout • WYSIWYG approach • Powerpoint interface

  16. Compatibility • Language • Existing 4.x datamodels can be used • Behaviour • Behaviour is the same as in 4.8 • Data • Data is interchangeable with 4.8 • Idea: • Reuse of the Blaise 4.8 API Service

  17. Architecture

  18. Demo

  19. Phase 1: ToDo • Stabilize current product • Import tool • Template designers • Documentation • Installation • Test with real datamodels • Incorporate user feedback

  20. Phase 2 and beyond • Rewrite Rules Engine • Data storage • Language enhancements • Localization • Manipula • Event language • Multimode support / Case Management • Debugger • Paradata

  21. Milestones • End of this year: CTP (result of Phase 1) • Next IBUC: First production version

More Related