Does creating REAL over-the-web Python code become realistic with Zope 2.4?
Hi! When I read about the reload functionality of Zope 2.4, an old vision came back to my mind: If we can reload Python code at runtime, and we can also edit, generate and store files (containing code) via the web (as LocalFS or extFile prove), then it should be perfectly possible to have something like ZClasses (it terms of the over-the-web front-end) that spits out and dynamically loads REAL Python classes instead of the rather experimental simulation of classes we get with ZClasses, right? I'll skip the part about why we should not be able to manipulate Zope code over the web, which can be discussed separately ... What do you think about this idea? If it finds some friends, I'll set up a formal proposal for something like "ZClass-like features to build REAL Zope Python classes over the web". Joachim
Coincidently, I was just trying to edit a file on the filesystem with an FTP client going thru Zope/FTP and a LocalFS. It didn't work. The LocalFS instance didn't look like a directory to FTP so FTP could neither read nor write to the directory. Does that throw a monkey wrench into your idea? -- Loren
-----Original Message----- From: zope-dev-admin@zope.org [mailto:zope-dev-admin@zope.org]On Behalf Of Joachim Werner Sent: Thursday, May 31, 2001 15:54 To: zope-dev@zope.org Subject: [Zope-dev] Does creating REAL over-the-web Python code become realistic with Zope 2.4?
Hi!
When I read about the reload functionality of Zope 2.4, an old vision came back to my mind:
If we can reload Python code at runtime, and we can also edit, generate and store files (containing code) via the web (as LocalFS or extFile prove), then it should be perfectly possible to have something like ZClasses (it terms of the over-the-web front-end) that spits out and dynamically loads REAL Python classes instead of the rather experimental simulation of classes we get with ZClasses, right?
I'll skip the part about why we should not be able to manipulate Zope code over the web, which can be discussed separately ...
What do you think about this idea? If it finds some friends, I'll set up a formal proposal for something like "ZClass-like features to build REAL Zope Python classes over the web".
Joachim
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
On Thu, May 31, 2001 at 04:11:56PM -0700, Loren Stafford wrote:
Coincidently, I was just trying to edit a file on the filesystem with an FTP client going thru Zope/FTP and a LocalFS. It didn't work. The LocalFS instance didn't look like a directory to FTP so FTP could neither read nor write to the directory.
Does that throw a monkey wrench into your idea?
ahhh, but ftp access appears on the LocalFS to-do list... -- charlie blanchard http://baldguru.com/ LosAngeles area Zope Users Group http://lazug.org
Coincidently, I was just trying to edit a file on the filesystem with an FTP client going thru Zope/FTP and a LocalFS. It didn't work. The LocalFS instance didn't look like a directory to FTP so FTP could neither read nor write to the directory.
Does that throw a monkey wrench into your idea?
No, not really. LocalFS was just an example. The only important thing is that I can edit something, post it over the web (either from a weg form or using FTP, WebDAV etc.) and then store it to the filesystem instead of the ZODB. BTW LocalFS works fine over the web frontend, and FTP over Zope over LocalFS is not really necessary in most cases, as you can go directly to the filesystem with plain FTP anyway. But LocalFS should be fixable to work over FTP, I think. Joachim
If we can reload Python code at runtime, and we can also edit, generate and store files (containing code) via the web (as LocalFS or extFile prove), then it should be perfectly possible to have something like ZClasses (it terms of the over-the-web front-end) that spits out and dynamically loads REAL Python classes instead of the rather experimental simulation of classes we get with ZClasses, right?
Do you mean generating Python code from ZClasses? For example making and editing a Product over the web? Well the one flaw is that you will still need to restart AFAIK to install a brand new product. Cheers. -- Andy McKay.
Do you mean generating Python code from ZClasses? For example making and editing a Product over the web?
Kind of. Probably not full-fledged Products, but ZClass-like Classes that define values for property sheets, include Methods, inherit from certain base classes etc. ... well, maybe I'll end up with a Product ;-) And I would maybe not generate the code "from ZClasses", but write a Python Product that does the generation.
Well the one flaw is that you will still need to restart AFAIK to install a brand new product.
This has to be tested out. At least it should be possible to add classes to an existing Product. So that would do. I'd just need a "dummy" Product where all the new over-the-web classes would go ... Joachim
Hi Joachim, Joachim Werner wrote on Friday, June 01, 2001 12:54 AM:
If we can reload Python code at runtime, and we can also edit, generate and store files (containing code) via the web (as LocalFS or extFile prove), then it should be perfectly possible to have something like ZClasses (it terms of the over-the-web front-end) that spits out and dynamically loads REAL Python classes instead of the rather experimental simulation of classes we get with ZClasses, right?
Your suggestion sounds like something stated in the Zope Directions Document at http://dev.zope.org/Resources/ZopeDirections.html:
The major goal will be to simplify how components (now called products) are built and used. For example, currently some products are built in the filesystem and some are built in the object database. We want to remove this distinction so that all components can be edited via the filesystem and live in the object database.
Joachim Werner wrote on Friday, June 01, 2001 12:54 AM:
What do you think about this idea? If it finds some friends, I'll set up a formal proposal for something like "ZClass-like features to build REAL Zope Python classes over the web".
Well I think many people would be interested to reduce the differences between ZClasses and python products. At least I would be interested. Regards Eric
On Fri, 1 Jun 2001, E. Seifert wrote:
at http://dev.zope.org/Resources/ZopeDirections.html:
The major goal will be to simplify how components (now called products) are built and used. For example, currently some products are built in the filesystem and some are built in the object database. We want to remove this distinction so that all components can be edited via the filesystem and live in the object database.
This does worry me. I think I understand at least one motivation (ZEO), but... Well, as long as it doesn't compromise my ability to write Zope python code using filesystem tools, it should be OK. It just makes me nervous <grin>. --RDM
this distinction so that all components can be edited via the filesystem and live in the object database.
This does worry me. I think I understand at least one motivation (ZEO), but...
Well, as long as it doesn't compromise my ability to write Zope python code using filesystem tools, it should be OK. It just makes me nervous <grin>.
I guess the crucial point is that everything should be editable from BOTH the filesystem (or a mountable Zope storage ;-)) and the web front end. Actually our motivation is a bit different from the one at DC. They mainly see the programmer as the target. For us, it's the power user, who wants to creat new objects, but only within a limited framework. For adding completely new functionality, these people would rely on professional help. But adding a new attribute to an object or changing a form should all be possible over the web. Joachim
participants (6)
-
Andy McKay -
Charlie Blanchard -
E. Seifert -
Joachim Werner -
Loren Stafford -
R. David Murray