Hi All, Here are few technical decisions I made so far: http://svn.zope.org/bluebream/trunk/docs/source/notes.txt?view=markup Looking for your feedback and comments. - BlueBream is a "web framework". - BlueBream can be called as Bream or BB for short. - The only public API exposed by "bluebream - the package" is an entry point:: "paste.paster_create_template": ["bluebream = bluebream.template:BlueBream"] The implementation of "bluebream" template is defined in "bluebream.template.BlueBream". The template implementation location could be changed if required later. This leaves us an option to change "bluebream" as a namespace package if required. - All the framework code will be using "zope" or "zope.app" namespace packages. Although "bream" could be considerd as a namespace package in future. - "bluebream" the project consists - documentation - compatibility test suite - project template May be documentation and compatibility test suite could be separated out to separate locations/packages later. - BlueBream 1.0 should provide an upgradation path from Zope 3.4 ZTK - Any "shell command" which developer need to repeat later should not be automated by the project template. - Running ``bootstrap.py`` and ``buildout`` inside project should not be added to project template creation for the previous reason. A suporting reason why it should not be added is to make adding sources to version controlling system should not be difficult. Regards, Baiju M
On Sun, Jan 10, 2010 at 6:38 AM, Baiju M <mbaiju@zeomega.com> wrote:
Hi All, Here are few technical decisions I made so far: http://svn.zope.org/bluebream/trunk/docs/source/notes.txt?view=markup
I have changed few wordings and committed, please look at updated one. I still need to improve my English :) Regards, Baiju M
Am Sonntag 10 Januar 2010 02:08:32 schrieb Baiju M:
Hi All, Here are few technical decisions I made so far: http://svn.zope.org/bluebream/trunk/docs/source/notes.txt?view=markup
Looking for your feedback and comments.
- BlueBream is a "web framework".
- BlueBream can be called as Bream or BB for short.
- The only public API exposed by "bluebream - the package" is an entry point::
"paste.paster_create_template": ["bluebream = bluebream.template:BlueBream"]
The implementation of "bluebream" template is defined in "bluebream.template.BlueBream". The template implementation location could be changed if required later. This leaves us an option to change "bluebream" as a namespace package if required.
- All the framework code will be using "zope" or "zope.app" namespace packages. Although "bream" could be considerd as a namespace package in future.
- "bluebream" the project consists
- documentation
- compatibility test suite
- project template
May be documentation and compatibility test suite could be separated out to separate locations/packages later.
- BlueBream 1.0 should provide an upgradation path from Zope 3.4 ZTK
- Any "shell command" which developer need to repeat later should not be automated by the project template.
- Running ``bootstrap.py`` and ``buildout`` inside project should not be added to project template creation for the previous reason. A suporting reason why it should not be added is to make adding sources to version controlling system should not be difficult.
+1 to everything. I personally like the roadmap and the way to go, especially the upgrade path from Zope 3.4. Best Regards, Hermann -- hermann@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7
participants (2)
-
Baiju M -
Hermann Himmelbauer