Amos Latteier wrote:
Bobo is much more simple and flexible than Zope. The Zope framework provides lot of services, but it also imposes lots of conventions in order to play ball.
It's hard to know how or even if it's possible to marry to "raw power and flexibility" of Bobo to the fuller services of Zope. I'm definitely open to suggestions.
Maybe there could be some way to code in Bobo, but write the UI in Zope... Or maybe we just need to better document the Product API so that writing a real Product doesn't seem so daunting. Maybe we should consider further segmenting the Zope Framework so that you can pick and choose the pieces you want.
For example, we have a "web tool" coded in bobo and it would be great, I think, if we could add a "newsgroup" for the tool embedded inside it, along with the other documentation. The way I imagine this to work is by simply importing a newsgroup python module (confera?), making a newsgroup instance and giving it a name to publish it. Would something like that be possible in principle? Or is it possible right now? Regards, Jan -- =================================================================== Jan Decaluwe === Easics === Design Manager === VHDL-based ASIC design services === Tel: +32-16-395 600 =================================== Fax: +32-16-395 619 Interleuvenlaan 86, B-3001 Leuven, BELGIUM mailto:jand@easics.be http://www.easics.com