- Simple Application.
- I want to start this project by supporting just a very simple application. Just 1 Zclass. I want to define the Zclass and its fields, and some properties on those fields, and have a number of applications automatically pop up. I want a table of these ZClasses, click on one to edit/view the details of that object. I want the table views and the instance views to be driven by the properties of the ZClass? fields. The properties are the read/right permissions, the execute method permissions, and the create and delete object permissions. I would also like a search form with a ZCatalog?, to be automatically created.
- ER Model Application
- The next stage would be to build a more complex application that looks like a relational database, Entity Relationship Model. We would create multiple classes, and indicate the links between them. Instances of each class would be in the same folder. All folders would be at the same level in the tree. It should be possible to specify the linkages between tables, and have the create/edit and delete forms work just right.
- More Complex Application Object Model
- In phase 3, we would support more complex Object models. There would be parent child nodes, and lists. Instances of a particular class could be in different folders.
- More Complex Object Model
- In this version, I want to build a tree of classes, much like a smalltalk hierarchy. Actually there would be two parallel trees, one for the instance methods, and one for the class methods, and class variables.
- Distributed Zclasses
- I like the idea of a federation of servers, where information about the person is shared among the servers, with the users permission, but each server has additional information. I like the idea of versions of ZClass? products, sucked up by the servers that depend on that product. I think a much more dynamic distributed system is needed, and that it can easily be built on top of Zope 2.
Changes required to Zope 2.
- Simple Application.
- Well the simple application would have the permissions determined by the class objects, not by the folder in the tree where the application resides. Create, Edit, View, execute permissions would be looked up in the Zclass. It would return the role required to execute. A little different than having the permissions be on the Zope tree.
- More Complex Object Model
- This would not work with the current product model.