July 1999 - Zope - Zope lists

Defining variables
by Alexander Staubo 13 Jul '99

13 Jul '99

Currently we have REQUEST.set(). This is nice, but I think there is a need for a general-purpose variable namespace that isn't related to REQUEST (plus the fact that typing "REQUEST.set(...)" all the time isn't so cool). I have one specific case where it's simply arduous having to mix real REQUEST variables -- meaning those that come in through the query string or form data -- with actual request-related variables. How about adding something like _.set()? -- Alexander Staubo http://www.mop.no/~alex/ "He could open a tin of sardines with his teeth, strike a Swan Vestas on his chin, rope steers, drive a steam locomotive and hum all the works of Gilbert and Sullivan without becoming confused or breaking down in tears." --Robert Rankin, _The Book of Ultimate Truths_

1 0

Re: [Zope] Zope and Frontier Comparison
by Kevin Dangoor 13 Jul '99

13 Jul '99

--- Kam Cheung <zope(a)littlecircle.com> wrote: [lots of good comparison of Frontier and Zope acquisition deleted] > In Frontier, it's another story. When you view a > Frontier object, Frontier > will assume that you will acquire the most immediate > pageHeader, pageFooter > and template. So, in a Fronter object, all I need to > do is put in: > > Bodytext goes here!!! > > I don't need to refer to any pageHeader or > pageFooter in the html object. When I chose to start working with Zope, I also evaluated Frontier. To me, the automatic use of templates seems natural and convenient. It allows the delegation of content creation without the writer having to know *anything* about DTML. If you use Structured Text, they only need to know a little structured text, no HTML. It would not be difficult in Zope2 to create ZClasses that automatically use a default template. Kevin _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

Zope and Frontier Comparison
by Kam Cheung 13 Jul '99

13 Jul '99

> Zope uses acquisition, which is a pretty powerful concept, but not > exactly template oriented (it can use any object, including Document > Templates). Perhaps you can give us an overview of how Frontier does > this? Actually, the way how a Zope object acquires properties (or atrributes) is very similar to Frontier. The part that I feel Frontier is more advanced is, I don't need to put in the  and  in Frontier. It's much easier to illustrate it by an example. Let's say we have a site like this: SITE_ABC template pageHeader pageFooter index_html another_html FOLDER_A template pageHeader pageFooter index_html FOLDER_B index_html (NOTE: the actual object name that you need to use in Frontier maybe different. In Frontier, template, pageHeader and pageFooter are attributes, and you must put a "#" before its name.) In Zope, inside the html objects, I will need to put in:  Bodytext goes here!!!  Also, the pageHeaders and the pageFooters in FOLDER_A and FOLDER_B will be different, since FOLDER_B will acquire SITE_ABC.pageHeader and SITE_ABC.pageFooter, while FOLDER_A has its own pageHeader and pageFooter. However, the object "template" here is useless. You can even say that the html object PLUS the header, footer, and other object that you put into the html object BECOME a template by itself. You can of course, built a index_html object that will read data from object on other part of the site. But it's up to your own to do that, Zope doesn't do this. In Frontier, it's another story. When you view a Frontier object, Frontier will assume that you will acquire the most immediate pageHeader, pageFooter and template. So, in a Fronter object, all I need to do is put in: Bodytext goes here!!! I don't need to refer to any pageHeader or pageFooter in the html object. Instead, I will put all of these into the "template" object. A Frontier template usually compose of: {pageHeader ()} {bodytext} {pageFooter ()} Let's look at it from another perspective. When a user request a html object in Frontier. Frontier walks into the directory tree, grab whatever attributes that you have specified, override any previously declared attributes as it walked towards the html object. When it hits the html object, it will start the rendering. Right up to this point, Zope and Frontier is still very similar. Then the difference start to appear. In Zope, you must put in a reference to the attribute by yourself, since your html object is essentially a template. In Frontier, the Frontier framework will do one more step. It grabs the template object. So, instead of rendering against the html object, it will render against the template object, and use the html object as a "Content Object". You can override the folder's template/pageHeader/pageFooter attributes in the html object if you want, but if you don't Frontier will always force default attributes to your objects. Is it clear? Or, is it still very confusing? I have to admit that I am not a good writer, not to say an English writer. I think Philip Suh can do a lot better than I do. Kam On Cheung

2 1

Confera "talkback" buttons - is this correct?
by cg＠cdegroot.com 13 Jul '99

13 Jul '99

I've done an experiment for talkback buttons on the bottom of pages. Basically, I created a Confera topic, copied all files but index_html to the top level folder, and copied the relevant part of the Confera's topic index_html to a top-level "talkback" DTML document. All I need to do now is create a Confera topic, edit an index_html inside the topic just like it was a normal document, and include a  somewhere at the bottom. Seems to work like a charm... Is this sensible? Any caveats? -- Cees de Groot http://www.cdegroot.com <cg(a)cdegroot.com>

1 0

Question: user homepages
by cg＠cdegroot.com 13 Jul '99

13 Jul '99

Zope security isn't exactly clear to me - could someone help out my working me through this example: I have a Users folder, and inside this folder I want to create users and for every user a folder, with just enough rights to create homepages. Furthermore, say that I have a set of users I trust a bit more that can also create Confera topics on their homepages. BTW: is there a way to log out from the management environment so you can connect as a user with less privileges for testing purposes? TIA, Cees -- Cees de Groot http://www.cdegroot.com <cg(a)cdegroot.com>

1 0

RE: [Zope] safe sql queries
by Alexander Staubo 13 Jul '99

13 Jul '99

This should work (untested):  -- Alexander Staubo http://www.mop.no/~alex/ "He could open a tin of sardines with his teeth, strike a Swan Vestas on his chin, rope steers, drive a steam locomotive and hum all the works of Gilbert and Sullivan without becoming confused or breaking down in tears." --Robert Rankin, _The Book of Ultimate Truths_ >-----Original Message----- >From: zope-admin(a)zope.org [mailto:zope-admin@zope.org]On Behalf Of >Graham Chiu >Sent: 13. juli 1999 22:33 >To: zope(a)zope.org >Subject: [Zope] safe sql queries > > > >I would like to construct a crash proof case insensitive query that >searches on a text field, and has a variable number of parameters. > >This effort works > > >param: keyword:tokens > >select * from main where > > > upper(description) like '%%' > >  >  > and >  > > > >but dies if anyone inputs ' or other such chars as a parameter. > >This doesn't work > >select * from main where > > upper(description) like '%%' > >  >  > and >  > > > >as #sqlvar also puts ' marks around the variable, and there is >no way to >convert it to upper case. > >I've tried preprocessing the parameters to upper case them and >add the % >marks before feeding to the ZSQL query but get error messages like: > >'Strings are not allowed as input to the in tag.' > >Suggestions? > >------- >Regards, Graham Chiu >gchiu<at>compkarori.co.nz > >_______________________________________________ >Zope maillist - Zope(a)zope.org >http://www.zope.org/mailman/listinfo/zope > >(For developer-specific issues, use the companion list, >zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

2 1

safe sql queries
by Graham Chiu 13 Jul '99

13 Jul '99

I would like to construct a crash proof case insensitive query that searches on a text field, and has a variable number of parameters. This effort works param: keyword:tokens select * from main where  upper(description) like '%%'   and   but dies if anyone inputs ' or other such chars as a parameter. This doesn't work select * from main where  upper(description) like '%%'   and   as #sqlvar also puts ' marks around the variable, and there is no way to convert it to upper case. I've tried preprocessing the parameters to upper case them and add the % marks before feeding to the ZSQL query but get error messages like: 'Strings are not allowed as input to the in tag.' Suggestions? ------- Regards, Graham Chiu gchiu<at>compkarori.co.nz

1 0

RE: [Zope] documentation bugs
by bruce＠perens.com 13 Jul '99

13 Jul '99

I'd suggest you use the DocBook SGML DTD. This can translate to TeX and HTML and XML and a million other things. It's accepted by many software book publishers for print production. There are 4 docbook-related packages on my Debian system, I haven't explored them and the SGML packages yet, but I know that a lot of people are writing in it. Now I know there are visual tools to edit SGML but I don't know what they are. Thanks Bruce

2 1

RE: [Zope] documentation bugs
by Pam Crosby 13 Jul '99

13 Jul '99

Thanks for the corrections. They are implemented online. We are trying to work out a procedure to allow volunteers submit patches. Hang in there, be patient with me, I'm still learning the internal workings of DC. -- Pamela Crosby Technical Writer mailto:pam@digicool.com Digital Creations > -----Original Message----- > From: bruce(a)perens.com [mailto:bruce@perens.com] > Sent: Tuesday, July 13, 1999 1:51 PM > To: bruce(a)perens.com; pam(a)digicool.com; zope(a)zope.org > Subject: RE: [Zope] documentation bugs > > > From: Pam Crosby <pam(a)digicool.com> > > Thanks for the note. Could you be more specific as to > where the errors > > are? I would be more than happy to fix this. > > Pam, > > First, you're not going to like this part, but I got two > replies from people > pointing out that FrameMaker isn't accessible to your > volunteer collaborators. > I concur. You might want to explore options that would make > it easier for them, > such as some form of SGML. I haven't used Frame in 5 years > and thus am not > familiar with the file formats it can handle. > > Here's a patch for ZCMG.8.html, but obviously you'd have to > get these changes > into the frame source. I think all of them would come up if > you ran the spell > checker. > > Thanks > > Bruce > > --- ZCMG.8.html Mon Jul 12 19:53:05 1999 > +++ ZCMG.8.html.old Mon Jul 12 19:51:26 1999 > @@ -24,9 +24,9 @@ > /manage > as shorthand for the latter. So follow along as we do the > following with Stan: > > -<A NAME="pgfId-1070999"></A>Design and implement a skeleton > site: In this step, Stan creates the basic elements that the > site will be built on: documents, images, and folders. Since > a skeleton site needs to be seen by others quickly, Stan > gives only enough to show what will be coming. > +<A NAME="pgfId-1070999"></A>Design and implement a skeleton > site: In this step, Stan creates the basic elements that the > site will be builts on: ducuments, images, and folders. > Since a skeleton site needs to be seen by others quickly, > Stan gives only enough to show what will be coming. > > -<A NAME="pgfId-1060792"></A>Set up access rights and create > basic content: In this step, we start a Session. A session > allows Stan to work directly on the site in private. None of > the changes he makes to the site will be seen by the public > until he says so. Now, he can start working on the real > content of the site and assigning security privileges without > worrying about exposing broken and in-progress work. Right > away, Stan organizes some of the basic content that all of > the sites will be able to use. He also gives access to the > PR and Research departments for their respective folders. > +<A NAME="pgfId-1060792"></A>Set up access rights and create > basic content: In this step, we start a Session. A session > allows Stan to work directly on the site in private. None of > the changes he makes to the site will be seen by the public > until he says so. Now, he can start working on the real > conten of the site and assigning security privileges without > worrying about exposing brokent and in-progress work. Right > away, Stan organizes some of the basic content that all of > the sites will be able to use. He also gives access to the > PR anr Research departments for their respective folders. > <A HREF="ZCMG.7.html">Previous Chapter</A> | <A > HREF="ZCMG.9.html">Next Chapter</A> | <A > HREF="ZCMG.html">Up</A> | <A > HREF="ZCMG.8.1.html">Next Section</A> | <A > HREF="ZCMG.html">Contents</A> > > > @@ -38,4 +38,4 @@ > <LI> <A HREF="ZCMG.8.3.html"> What's the Difference > Between DTML Methods and DTML Documents?</A> > </UL> > </BODY> > -</HTML> > +</HTML> > \ No newline at end of file > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope > > (For developer-specific issues, use the companion list, > zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

1 0

RE: [Zope] Zope and Apache vs ZAP? Which server to use?
by Michel Pelletier 13 Jul '99

13 Jul '99

> -----Original Message----- > From: Kam Cheung [mailto:zope@littlecircle.com] > Sent: Tuesday, July 13, 1999 10:52 AM > To: Zope > Subject: Re: [Zope] Zope and Apache vs ZAP? Which server to use? > > > BTW, it takes me a while to get used to how Zope handles > templates. It's > quite different than Frontier. The way how Frontier handles inherited > templates, pageheader, and pagefooter is definitely more > advanced than how > Zope does it (as far as I know, if I am wrong, someone please > correct me and > I am more than happy to know how to do it). > Zope uses acquisition, which is a pretty powerful concept, but not exactly template oriented (it can use any object, including Document Templates). Perhaps you can give us an overview of how Frontier does this? -Michel > > Kam On Cheung > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope > > (For developer-specific issues, use the companion list, > zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

1 0