Some ideas about the future of Zope products...
Hello, Being new to zope, I hope this is relevant. I just putted together an article about the way I see future Zope products. It is available at : http://123piano.com/en/webdesign/zope-products/default.htm A little extract : "What seems to be a pain when creating a product is the fact that you need to provide your own User Interface. Why do I need to create a specific UI to let the user update the title of my product? And if I want to have my user edit the title trough ftp? Webdav? Do I have to take care of this as well? We should easily agree that UI is not a part of the product, but a part of Zope." If you have any comments to share, let's discuss ! I hope this idea has not been dicussed 100 times before. Philippe Jadin www.123piano.com
Philippe Jadin wrote:
"What seems to be a pain when creating a product is the fact that you need to provide your own User Interface. Why do I need to create a specific UI to let the user update the title of my product? And if I want to have my user edit the title trough ftp? Webdav? Do I have to take care of this as well? We should easily agree that UI is not a part of the product, but a part of Zope."
I only read the extract, but... I disagree. If you are delivering content via Zope then you sort of have a point. Isn't that what the CMF is supposed to do? When writing an application, I 'want' to build my own UI. It should definitely not be part of the core to a point where I have to use it. -- Tim Cook, President - FreePM,Inc. http://www.FreePM.com Office: (901) 884-4126 ONLINE DEMO: http://www.freepm.org:8080/FreePM
I only read the extract, but... I disagree. If you are delivering content via Zope then you sort of have a point. Isn't that what the CMF is supposed to do? When writing an application, I 'want' to build my own UI. It should definitely not be part of the core to a point where I have to use it.
I agree that there are some occasions when you need your own UI, but for the most common *backend* tasks, a standard UI is sufficient. Moreover, I introduce in the article the concept of skins : you define your own gui, and you apply it to the definition file of your product. This would give sharable UI among all your products (even the standard zope products of course). This would be a lot more flexible. And having a standard UI to start quick product prototyping would certainly not hurt. Sorry if the extract choosen was not totally self-speaking. Philippe
On 27 Mar 2001 10:08:37 +0200, Philippe Jadin wrote:
I only read the extract, but... I disagree. If you are delivering content via Zope then you sort of have a point. Isn't that what the CMF is supposed to do? When writing an application, I 'want' to build my own UI. It should definitely not be part of the core to a point where I have to use it.
I agree that there are some occasions when you need your own UI, but for the most common *backend* tasks, a standard UI is sufficient. Moreover, I introduce in the article the concept of skins : you define your own gui, and you apply it to the definition file of your product. This would give sharable UI among all your products (even the standard zope products of course). This would be a lot more flexible. And having a standard UI to start quick product prototyping would certainly not hurt.
Sorry if the extract choosen was not totally self-speaking.
CMF already has skins that do that. :^)=
Hi Phillippe, thats what I sayd 1000 times ;) Zope needs an application abstration layer. Unfortunately we are far away from it :( Regards Tino Philippe Jadin wrote:
Hello,
Being new to zope, I hope this is relevant. I just putted together an article about the way I see future Zope products.
It is available at :
http://123piano.com/en/webdesign/zope-products/default.htm
A little extract :
"What seems to be a pain when creating a product is the fact that you need to provide your own User Interface. Why do I need to create a specific UI to let the user update the title of my product? And if I want to have my user edit the title trough ftp? Webdav? Do I have to take care of this as well? We should easily agree that UI is not a part of the product, but a part of Zope."
If you have any comments to share, let's discuss ! I hope this idea has not been dicussed 100 times before.
Philippe Jadin www.123piano.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (4)
-
Bill Anderson -
Philippe Jadin -
Tim Cook -
Tino Wildenhain