Usually, when you develop an application, you deal with the database schema and the source code. With Oberon the database schema is replaced with the application schema or in other words with the collection of administrative objects that represent the object classes, the object link-types, the lifecycles, the menus, commands, forms, views and so on. The schema is defined by using the Context Design tool (or directly with OOQL commands) and it is stored in the database. While the source code (web-pages or java classes) may be versioned and shared with a Subversion repository, the schema can be shared only if exported and imported (or compared) in the others Oberon DB instances.
The new release 1.6 allows to collaborate for the application schema creation and to share the administrative objetct definitions directly with the SVN repository, avoining the repeated and annoying export/import operations. You can simply check differences by connecting to the SVN repository and by updating your application schema or by commiting the modifications.
This accelerate the development of open source projects when the developers are distributed in different locations.
|
Copyright © 2000 - 2008 Mantis Group