October 1999 - Zope-Dev

RE: [Zope-dev] inconsistency in tag argument syntax
by Jay, Dylan 07 Oct '99

07 Oct '99

> -----Original Message----- > From: Martijn Pieters [mailto:mj@antraciet.nl] > Sent: Thursday, October 07, 1999 18:30 > To: Jay, Dylan; 'zope(a)zope.org' > Cc: 'zope-dev(a)zope.org' > Subject: Re: [Zope-dev] inconsistency in tag argument syntax > > > At 09:32 07/10/99 , Jay, Dylan wrote: > >After playing around with making a tag an inconsistency in > the tag syntax > >became apparent to me. Sometimes "asd" is treated as an > expression and > >sometimes as a string. e.g. > ><dtml-let blah="aObject.method()"> is an expression however > ><dtml-mime name="aObject.method()"> makes the name argument > a string with > >'aObject.method()' > >This is confusing and inconsistent. Also treating any > argument always as a > >string means that the value of the argument can never be dynamically > >specified i.e. there is no way I could name a mime block > dynamically e.g. > >from a form. The same applies for instance to the 'sort' argument in > ><dtml-in>. This is very limiting. > > > >The problem is however that I can't see a backwards > compatible way of fixing > >this problem. Alternatives are > >a) You could introduce a evaluate expression syntax like > there is in sh > >script. i.e. name="`myMethod()`". This however makes things > more confusing > >and unreadable. > >b) Another possibility is to make all "non-expression" > arguments become > >expression arguments. This would break existing code and > mean all string > >constants look like name="'A name'" which is also not > intuitive and messy. > >This could be made cleaner by allowing syntax such as name='A name'. > >c) Or ignore the problem. > > > >I prefer option b). > >What do other people think? > > Hmm.. > > This is not as inconsistent and illogical as you think. Your > DTML page is > compiled into a hierarchy of objects, speeding up rendering > of the page > when called. Most attributes are static, which helps. Only > those attributes > that need to be dynamic, are really so, just to help this > along. Attributes > that allow expressions are an exception, not a rule. First let me clarify. By incosistent I meant from a user perspective. To have one named argument be treated completely differently from another depending on context is very confusing for the user. I think that logical consistancy and readability of a language are very important. It seems these were very important in the design of python however I don't think those principles have translated as nicely to DTML. DTML's goal should be to easy for everyone. Basically syntax "exceptions" are not a way to make an easy to use language. Anyone who has learnt english as a second language will tell you how hard it is because english has so many "exceptions". As for speed, this is irrelevent. A static value can be recorded as such regardless if a variable can be used instead. A simple check to determine if it is static or not is not a big performance hit.

1 0

RE: [Zope-dev] Clarification: Bug patches and Product update
by Anthony Pfrunder 07 Oct '99

07 Oct '99

On Thu, 7 Oct 1999, Rik Hoekstra wrote: > Yep, I followed all your instructions but got nothing but tracebacks (not > sure if they were exactly the same as Martijn's). If it works for you > obviously we do something different :-\ Bummer, I must have some patches still lying around somewhere. I'll see if I can find them. > That would be great - but doesn't the the ZEI example depend on a IE only > HTMLText (or something alike) tag? Yes, but the javascript I'm using for VZ provides a cross-browser javascript DOM model which works on both NS and IE. This DOM includes all the "useful" enhancements from IE 5.0. You can find it at: http://www.dansteinman.com/dynduo The code is GPL but the tutorial is NOT. You will need to make modifications to your javascript code (ie its not a drop-in replacement). The purpose of VZ IS to make it a drop-in replacement ;) Cheers, Anthony Pfrunder

1 0

NotMail on Win32 Zope
by Josh Zeidner 07 Oct '99

07 Oct '99

Has anyone successfully installed NotMail on Win32 zope-install? thanks to all the zope people! --josh z ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

1 0

File Logging
by Jason Spisak 07 Oct '99

07 Oct '99

I tried the stupid file logger and the output in that file doesn't seem to match the output in my terminal. In my terminal I get a lot of "Z2 CONFICT ERROR" with competeing writes. Is there a way to keep this from happening. Also I get "uncaptured python exception (Broken Pipe) and (Bad file descriptor) a lot. Is there anything I can do to fix this kind of thing or keep it from happening. Or is it not hurting anything? -- Jason Spisak webmaster(a)hiretechs.com

1 0

Re: [Zope-dev] inconsistency in tag argument syntax
by Martijn Pieters 07 Oct '99

07 Oct '99

At 09:32 07/10/99 , Jay, Dylan wrote: >After playing around with making a tag an inconsistency in the tag syntax >became apparent to me. Sometimes "asd" is treated as an expression and >sometimes as a string. e.g. ><dtml-let blah="aObject.method()"> is an expression however ><dtml-mime name="aObject.method()"> makes the name argument a string with >'aObject.method()' >This is confusing and inconsistent. Also treating any argument always as a >string means that the value of the argument can never be dynamically >specified i.e. there is no way I could name a mime block dynamically e.g. >from a form. The same applies for instance to the 'sort' argument in ><dtml-in>. This is very limiting. > >The problem is however that I can't see a backwards compatible way of fixing >this problem. Alternatives are >a) You could introduce a evaluate expression syntax like there is in sh >script. i.e. name="`myMethod()`". This however makes things more confusing >and unreadable. >b) Another possibility is to make all "non-expression" arguments become >expression arguments. This would break existing code and mean all string >constants look like name="'A name'" which is also not intuitive and messy. >This could be made cleaner by allowing syntax such as name='A name'. >c) Or ignore the problem. > >I prefer option b). >What do other people think? Hmm.. This is not as inconsistent and illogical as you think. Your DTML page is compiled into a hierarchy of objects, speeding up rendering of the page when called. Most attributes are static, which helps. Only those attributes that need to be dynamic, are really so, just to help this along. Attributes that allow expressions are an exception, not a rule. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------

1 0

inconsistency in tag argument syntax
by Jay, Dylan 07 Oct '99

07 Oct '99

After playing around with making a tag an inconsistency in the tag syntax became apparent to me. Sometimes "asd" is treated as an expression and sometimes as a string. e.g. <dtml-let blah="aObject.method()"> is an expression however <dtml-mime name="aObject.method()"> makes the name argument a string with 'aObject.method()' This is confusing and inconsistent. Also treating any argument always as a string means that the value of the argument can never be dynamically specified i.e. there is no way I could name a mime block dynamically e.g. from a form. The same applies for instance to the 'sort' argument in <dtml-in>. This is very limiting. The problem is however that I can't see a backwards compatible way of fixing this problem. Alternatives are a) You could introduce a evaluate expression syntax like there is in sh script. i.e. name="`myMethod()`". This however makes things more confusing and unreadable. b) Another possibility is to make all "non-expression" arguments become expression arguments. This would break existing code and mean all string constants look like name="'A name'" which is also not intuitive and messy. This could be made cleaner by allowing syntax such as name='A name'. c) Or ignore the problem. I prefer option b). What do other people think?

1 0

Bug patches and Product update
by Anthony Pfrunder 07 Oct '99

07 Oct '99

Hi, I have released a new version of the VisualZope Product (was VisualStudio but a certain company in Redmond has a product with the same name...). VZ now runs on top of and REQUIRES the following products: * XMLWidgets * Python Methods (with patch) * XMLDocument This is a development release and is not complete - please use the old version to build your widgets (the DTD has not changed) unless you are borrowing / looking at the code. Python Methods requires a simple patch to work. For some reason methods located within a ZClass crash upon creating a function with a self parameter. To fix this, goto the innermost line ref'd in the traceback and delete the "...and len(cofunc...)..." bit. Restart Zope. XMLDocument has lots of bugs in it (sorry Amos ;) most of which are fixed in the subclasses within VZ. One which I haven't patched yet is insertBefore(newchild, oldchild). For some reason if you pass it getFirstChild it will dup this node and then insert your newchild. There is lots of interesting code showing how to call child ZClass methods and Product supermethods, how to implement Product/Zclass conditional callbacks and how to use the ZDOM to the max. Useful stuff includes subclassing from other products at product level and walking up the aquisition tree to generate custom Add Object palettes. Nasty things are done to the aq_* metaattributes and some things will make you scream - so be warned! Please install it as per the instructions located @ http://www.zope.org/Members/NoneToBe/VisualStudio/new_html Cheers, Anthony Pfrunder

4 7

RE: [Zope] change to MimeWriter to add "MIME-Version: 1.0"
by Jay, Dylan 07 Oct '99

07 Oct '99

> -----Original Message----- > From: Pate, Clarence T [mailto:Clarence.Pate@bridge.bellsouth.com] > Sent: Thursday, October 07, 1999 04:45 > To: jason(a)mtear.com; michel(a)digicool.com; zope(a)zope.org > Subject: RE: [Zope] change to MimeWriter to add "MIME-Version: 1.0" > I'm also making changes to MimeTools. I've split the mime tag into two tags, mime and boundary. This allows for the conditional inclusion of sub parts. I am currently trying to allow variablized parameters to the tags (and not having much luck!). I want to be able to say <dtml-boundary name="upload_file.filename()"> Anyone have any ideas? > =-> > =->Note that Mimewriter is a standard python module, not a > part of Zope. > =->You should submit your patch to the apropriate module > author or to the > =->http://www.python.org/python-bugs section of the python site. > =-> > =->Thanks for the patch! > =-> > =->-Michel > =-> > > Michael, > > I sent a message to Guido, and he suggested something that > was much better (I > really should not have bothered him with this minor problem.) > All that was > necessary is to change "MimeTools.py". Basically, I added a > parameter to the > mime tag, . Since I am not a python > programmer, > somebody should verify that this does what I think it does!?! > I have included the subset of MimeTools.py that I changed. > > > > name='mime' > blockContinuations=('boundary',) > encode=None > """I added version=None. I guess this is like a global variable. > I am not sure if this is necessary""" > version=None > > def __init__(self, blocks): > self.sections = [] > > for tname, args, section in blocks: > """I added the parameter version""" > args = parse_params(args, type=None, disposition=None, > encode=None, name=None, version=None) > > has_key=args.has_key > > if has_key('type'): > type = args['type'] > else: > type = 'application/octet-stream' > > if has_key('disposition'): > disposition = args['disposition'] > else: > disposition = '' > > if has_key('encode'): > encode = args['encode'] > else: > encode = 'base64' > > if has_key('name'): > name = args['name'] > else: > name = '' > """I added this. I believe it checks for any value, if no > value set to ''""" > if has_key('version'): > version = args['version'] > else: > version = '' > > if encode not in \ > ('base64', 'quoted-printable', 'uuencode', 'x-uuencode', > 'uue', 'x-uue', '7bit'): > raise MIMEError, ( > 'An unsupported encoding was specified in tag') > > self.sections.append((type, disposition, encode, > name, version, section.blocks)) > > > def render(self, md): > contents=[] > mw = MimeWriter(StringIO()) > > """I added this. If version exists, add the header to 'outer'. > This only provides for version 1.0, maybe this should be a > variable that is actually passed if there are new future > version numbers. """ > for x in self.sections: > t, d, e, n, v, b = x > if v: > outer = mw.addheader("MIME-Version", "1.0", prefix=1) > outer = mw.startmultipartbody('mixed') > > Thanks for the help! > > Clarence T. Pate > > >

1 0

Re: [Zope-dev] What happened to the WinNT Service Product?
by Josh Zeidner 06 Oct '99

06 Oct '99

I think you might have misunderstood ( but maybe not ) : There was once a product that duplicated the functionality of the NT service Manager Applet for the Web. This was very useful for me. I did not mean running Zope as an NT service. thanks anyway. -jmz >At 12:12 PM 10/5/99 EDT, Josh Zeidner wrote: > > > > What happened to the product that allowed you to control WinNT services > >from Zope? > > > > ...what a loss :) > >You can do this with Zope out of the box! Just run the windows installer. > >If you want more control examine ZServer/ZService.py > >-Amos > > > >_______________________________________________ >Zope-Dev maillist - Zope-Dev(a)zope.org >http://www.zope.org/mailman/listinfo/zope-dev > >(Related lists - please, no cross posts or HTML encoding! > >To receive general Zope announcements, see: >http://www.zope.org/mailman/listinfo/zope-announce > >For non-developer, user-level issues, >zope(a)zope.org, http://www.zope.org/mailman/listinfo/zope ) ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

2 1

RE: [Zope-dev] Truncating a Corrupted Data.fs
by Michel Pelletier 06 Oct '99

06 Oct '99

> -----Original Message----- > From: Jason Spisak [mailto:webmaster@hiretechs.com] > Sent: Wednesday, October 06, 1999 12:16 PM > To: zope-dev(a)zope.org > Subject: [Zope-dev] Truncating a Corrupted Data.fs > > > Does anyone know the best way to truncat a corrupted Data.fs > file at the > corrupted record? Use 'split'. Try, 'man split'. -Michel > > All my best, > > -- > Jason Spisak > webmaster(a)hiretechs.com > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://www.zope.org/mailman/listinfo/zope-dev > > (Related lists - please, no cross posts or HTML encoding! > > To receive general Zope announcements, see: > http://www.zope.org/mailman/listinfo/zope-announce > > For non-developer, user-level issues, > zope(a)zope.org, http://www.zope.org/mailman/listinfo/zope ) >

1 0