hi again, --On Mittwoch, 25. April 2001 11:04 -0500 David Kovach <davidkovach@hotmail.com> wrote:
That is a good solution with the hidden frame - again, I think the Zope management tool is useful and it works and I know alot of the same functionality could be duplicated in a different (or similar to the edit tool you provide your users) gui implementation - what would be great is integration within HTML/XML editors.
Arent there movements going on here with GoLive and Dreamweaver?
You can use any tool that supports DAV or FTP.
On the other ASP note - what ASP concepts do you think would be the top 5 that would need to be depicted under the Zope Way?
Dont think in terms of programming solutions. Think in terms of concepts!
I think:
1. Form submission and Form Response via ASP
Form submission is never work for the server. Rather it is done by the client.
2. Dynamic content (like time and date - something simple) placed in a page
Try to get away from "pages". Divide your problem into content and application. Content is somewhat semi-static, the rest schould be analyzed into related problems and put into classes.
3. SQL connection object and subsequent SQL call
This is only a building block.
4. Page Redirection and passing of form field or hidden data (state)
There are numerous session products that store data into sql-bases, cookies and such.
5. Reading in attributes from an offline configuration page (asp page) to set the values of an online page - like bgcolor,etc.
There are properties. But keep in mind these things are much better done using CSS. You can generate CSS on the fly or store it into objects or include one object into another.
Probably many of these are done a different way altogether and some of which arent the preferred way to do things with ZOPE (like even using a SQL db). But, idea is to look at ASP concepts - describe em in Zope terms. and show how they can be accomplished more effectively and efficiently with ZOPE.
As I sayd already :-) Forget anything you learned from ASP :)
Sincerely,
David Kovach dave@kovach.com SAP
From: rlanham@speakeasy.net To: "dave@kovach.com" <dave@kovach.com> Subject: RE: [Zope] asp request and response objects Date: Wed, 25 Apr 2001 06:34 -0700
I would be willing to do so - to really point out to other developers (ASP etc.) Why Zope rocks and __blank__ doesnt! We could fairly deep into it - not just high level reasons why its better... Just a thought.
At work I am primarily an ASP developer (though I am turning these squares on to Zope and Squishdot). When I spend a sat or sun working on my zope home-hobby-site, I often struggle with what should be mundane.
I am always wishing for an ASP:Python|DTML Rosetta stone. You do this like that in ASP, this is how you get that done in Python|DTML. I could contribute to such an effort, but I am more in need of it.
The thing I find the clunkiest (though it works flawlessly and makes good intuitive sense) is the management interface. Would be better as a rich gui. This work is going on isnt it already?
The thing that bothers me about the Zope mgmt UI is that the manange_Edit page refreshes so you lose your place every time you submit changes. I built an edit page for my users that lets them make changes in a top frame and show the page they are working on in a bottom frame and submit through a hidden frame with a javascript function. Works great--even with huge amounts of text. Just walks a form, writes it to a hidden frame, and submits. Then refresh bottom frame only.
Wouldn't it be easyer to use the target-attribute of the form-tag to accomplish this? Using a JavaScript here seems a bit over enginered ;)
Regards Tino