Buckminster

Buckminster is a set of frameworks and tools for automating build, assemble & deploy (BA&D) development processes in complex or distributed component-based development. Buckminster allows development organizations to define fine-grained "production lines" for the various stages in software production - unit testing, integration testing, field deployment, staged migration, etc. - and to automate the execution of corresponding processes.

Eclipse PMF

Eclipse PMF focuses in fact on high level presentation modeling concepts on GUI by ignoring the displaying technology artifacts such as appearence, layouts and data binding support. It allows each technology to make its specific connection with this framework. 

The purpose of this framework is to provide the basic functional concepts of user interaction in a PIM level UI modeling language. The language can be extended in two ways:

Eclipse DAWNSci

This project provides features to allow scientific software to be inter-operable. Algorithms exist today which could be shared between existing Eclipse-based applications however in practice they describe data and do plotting using specific APIs which are not inter-operable or interchangeable. This project defines a structure to make this a thing of the past. It defines an inter-operable layer upon which to build RCP applications such that your user interface, data or plotting can be reused by others.

Buckminster Component Assembly

Buckminster is a set of frameworks and tools for automating build, assemble & deploy (BA&D) development processes in complex or distributed component-based development. Buckminster allows development organizations to define fine-grained "production lines" for the various stages in software production - unit testing, integration testing, field deployment, staged migration, etc. - and to automate the execution of corresponding processes.

XWT

XWT is a powerful declarative UI in XML for Eclipse. It is a thin layer of markup language by unifying SWT/JIFace and JFace Databinding in one. It simplifies the UI development in Eclipse and open a door to provide more tools such as:

  • Visual editing using Windows Builder
  • Model Driven UI. Papyrus uses XWT to generate the "Properties View" for UML model editing.

Eclipse Xtext

Eclipse Xtext is a framework for development of programming languages and domain specific languages. It covers all aspects of a complete language infrastructure, from parsers, over linker, compiler or interpreter to fully-blown top-notch Eclipse IDE integration. It comes with good defaults for all these aspects and at the same time every single aspect can be tailored to your needs.

Eclipse QVT Operational

The Eclipse QVT Operational component is an implementation of the Operational Mappings Language defined by Meta Object Facility™ (MOF™) 2.0 Query/View/Transformation™ (QVT™). In long term, it aims to provide a complete implementation of the operational part of the standard.

Operational QVT project provides a powerful Eclipse IDE:

  • feature-rich editor (syntax highlighting, hovers, hyperlinks, code completion, templates, outlines, markers, etc.)
  • debugger (conditional breakpoints, variables view, expressions view, watches)
  • metamodel browser, trace view
  • project builders, launch configurations
  • deployment facilities and Ant support
  • Java API for executing QVT transformations programmatically, support for the standalone execution of transformations
  • support of Java Black-Box units and libraries
  • seamless integration with JDT supporting co-development of QVTo and Java in single workspace

Additional tooling QVTO Code Coverage provides:

  • annotate the Operational QVT Editor to highlight covered and non-covered parts of transformation
  • JUnit launch configuration to integrate with the JUnit test framework

Eclipse Graphiti

The goal of Eclipse Graphiti is to support the fast and easy creation of graphical tools, which can display and edit underlying domain models using a tool-defined graphical notation. Graphiti supports the developer in getting to a first version of an editor with very low effort by:

  • Hiding platform specific technology (e.g. GEF / Draw2D on Eclipse)
  • Providing rich default implementations inside the framework
  • Providing a default look and feel that was designed in close co-operation with usability specialists