September 2000 - Zope-Dev

ZPL HowTo?
by Lalo Martins 29 Sep '00

29 Sep '00

We wished to release the new development version of HiperDom under the ZPL, but we figured it wouldn't be that simple, as the license text is all littered with "Digital Creations". Is it just a matter of s/Digital Creations/Hiperlógica/g? Is this even legal? (This message is mostly rethorical, because we already decided to just release it under the MIT-X11 license anyway, but I feel this question should be discussed if people want to release stuff under the ZPL in the future.) []s, |alo +---- -- Hack and Roll ( http://www.hackandroll.org ) News for, uh, whatever it is that we are. http://zope.gf.com.br/lalo mailto:lalo@hackandroll.org pgp key: http://zope.gf.com.br/lalo/pessoal/pgp Brazil of Darkness (RPG) --- http://zope.gf.com.br/BroDar

1 0

Fix for Can't Change Image & File Security Settings in Zope 2.2.x
by Chris Withers 29 Sep '00

29 Sep '00

Hi, You may, like me, have noticed that you can't change security settings on Image and File objects in Zope 2.2.x. This is because the __call__ method of these objects was removed by the appropriate bit of __ac_permissions__ wasn't taken out. The patch in the PS fixes this... cheers, Chris PS: =================================================================== RCS file: /cvs-repository/Zope2/lib/python/OFS/Image.py,v retrieving revision 1.105.2.12 diff -r1.105.2.12 Image.py 169c169 < 'getContentType', '__call__', '')), --- > 'getContentType', '')), 450c450 < 'getContentType', '__call__', '')), --- > 'getContentType', '')),

1 0

Soft links again
by al028823＠alumail.uji.es 29 Sep '00

29 Sep '00

Hi all, First, I'm using Zope 2.2.1 (Debian package). I've been trying to implement zope objects that behave like unix soft links. The message http://lists.zope.org/pipermail/zope-dev/2000-July/005963.html by Shane proposes an implementation based in the __of__ method: class SoftLink (SimpleItem): def __init__(self, path): self.path = path def __of__(self, parent): ob = self.restrictedTraverse(self.path) return getattr(ob, 'aq_base', ob).__of__(parent) but it fails when I try to create an instance: Traceback (innermost last): File /usr/lib/zope/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/lib/zope/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: manage_addImportedSubject) File /usr/lib/zope/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: manage_addImportedSubject) File /var/lib/zope/Products/LLEU/subjects.py, line 1129, in manage_addImportedSubject (Object: Traversable) File /usr/lib/zope/lib/python/OFS/ObjectManager.py, line 250, in _setObject (Object: Traversable) File /usr/lib/zope/lib/python/OFS/ObjectManager.py, line 236, in _getOb (Object: Traversable) AttributeError: A00 A little of debug shows that the object has been added (line 249, see below), the exception raises when it tries to get the object (line 250). The hasattr function (line 234) returns false but the object has been added (it's in the __dict__) attribute and its __off__ method is called when the hasattr function is called. What I'm doing wrong? Thanks, david ObjectManager.py: class ObjectManager( ... def _setOb(self, id, object): setattr(self, id, object) def _delOb(self, id): delattr(self, id) def _getOb(self, id, default=_marker): 234 if not hasattr(aq_base(self), id): if default is _marker: 236 raise AttributeError, id return default return getattr(self, id) def _setObject(self,id,object,roles=None,user=None, set_owner=1): v=self._checkId(id) if v is not None: id=v try: t=object.meta_type except: t=None self._objects=self._objects+({'id':id,'meta_type':t},) # Prepare the _p_jar attribute immediately. _getCopy() may need it. if hasattr(object, '_p_jar'): object._p_jar = self._p_jar 249 self._setOb(id,object) 250 object=self._getOb(id)

4 8

Re: [Zope-dev] XHTML Templates comments from the peanut gallery
by Dieter Maurer 29 Sep '00

29 Sep '00

Chris Withers writes: > > A **page** is the result of applying presentation to data in the > > object system. A page is a particular result of a URL when viewed > > under certain conditions. > > ....I'd like to add to this: > components used to make up 'page's should not be URL-visible. Why should > they be? > (would this raise issues with XML-RPC?) Because, you want to access them for management purposes (e.g. change them). > > Site Designers will create XHTML Template objects that control > > Where can I find out more about XHTML? --> http://www.w3c.org Dieter

2 1

RE: [Zope-dev] I feel your Wiki Pain ;-)
by Toby Dickenson 29 Sep '00

29 Sep '00

> | 1. No threading. On several occasions I have made comments in a Wiki > | that were subsequently ignored - I guess because they got > lost in the > > and from the WikiNG proposal: > > For more elaborate editorial and commentary annotations, i can > see layered documents, using mixin objects that provide a > tailored view on other or contained objects. The mixin would > be a layer by which annotations are associated with text > passages in the rendered subject document, like "the crit > system":http://crit.org does for arbitrary web pages. > > Overall, document authors could use a particular annotation > structure according to their needs. Eg, discussion objects for > points which can be discussed, or brief editorial passages to > give feedback, and author checkmarks for when they've satisfied > or refute the suggestions, etc. > > Annotation is a spiffy kind of threading. I dont actually have anything against Wikis in general; I have used on very successfully for what I would describe as "document refinement", and a better annotation scheme will enhance that use of Wikis. The passage you quoted uses terms like "subject document", and at the moment I dont see that as the best model for a *debate* > | 2. No personal replies. On several occasions I would have liked to > > From WikiNG: > > - Attribution of changes for tracking > > With attribution, you can identify and could respond directly to the > author of a particular passage. It's useful for more, of course. Cool, I missed that one. > | 3. No update notification. The one time I was update to > > | 4. Hard to keep track of many Wikis: Each wiki has its own 'whats > > The ability to subscribe for notification (above) and/or to track what > you personally have seen, and not, is intended for this kind of thing. It would keep me happy if the notification includes a link to the new content (rather than a link to the page that contains new content). Even better, the email notification could *include* the new content. > | 6. Too easy to miss the creation of a Wiki. On several occasions > > My plans for notification subscriptions would be hierarchical, and > enable you to subscribe to events like creations of new wikis > within a > hierarchy - so if you subscribe at the top of the wiki space, > you find > out about any new wikis, while if you subscribe within the developer's > part of the space, you learn about new developers wikis. Etc. (This > was not covered in the WikiNG proposal - i was trying to avoid > including too many details, and failed miserably anyway...-) Im happy. > | 9. I never get the structured text quoting of python source right > | first time. > > The only quoting you need to know is example:: > > The two colons after the word "example" indicate that this > contained > block is all quoted. Ill remember that. Your proposed new attribution scheme would help too. > As i said in my last reply (but after you posted this, so you couldn't > have taken it into account), mailling lists as they stand don't work > for establishing growing structures. But Wikis don't (for me, today) work for loosely structured commentry. Quoting from http://dev.zope.org/Fishbowl/Introduction.html >In some cases a mailing list will be setup for substantive, >large-scale projects. Otherwise existing mailing lists can >be leveraged (for now, use zope-dev for this). Perhaps I should rephrase my objection..... The *real* problem is that this isnt happening - discussion is stored in Wiki pages like http://dev.zope.org/Wikis/DevSite/Proposals/XxxxDiscussion

6 17

Re: [Zope-dev] I feel your Wiki Pain ;-)
by Karl Anderson 29 Sep '00

29 Sep '00

Martijn Faassen <faassen(a)vet.uu.nl> writes: > I think you could integrate both mailinglists and wikis. On the one > hand, often we'd like to preserve a good posting in a mailing list as > a wiki page. So we make a separate wiki(a)zope.org address that's subscribed > to the mailing list, that keeps listening to the list and sees things > like this in postings: > > Wiki:StructuredTextWiki:FooBarPage > > This is a bunch of text that should be added to FooBarPage. > > Wiki:end Check out the MonkeyFist blog at <http://monkeyfist.com/DailyChurn/> - it's generated by scanning their IRC channel. -- Karl Anderson karl(a)digicool.com

1 0

ZCatalog with UTF-8 Chinese
by Sin Hang Kin 29 Sep '00

29 Sep '00

Dear Developer: Trying to short-cut UNTEXTINDEX to handle UTF-8 Chinese, I need some help. After reading some code of query, I think the regular expression operations which in parse, quotes and parse2 were not safe for utf8 string. So, I decide to emulate what they do. However, I do not understand what getlexicon is doing and I would like to learn what q should looks like before it is passed to evaluate. I do not understand that vocabulary seems to store like integer, is getlexicon a step to look up the string to convert them to integer? I am getting lost. Could some experienced developer help me out of these? Rgs, Kent Sin --------------------------------- kentsin.weblogs.com kentsin.imeme.net def query(self, s, default_operator = Or, ws = (string.whitespace,)): """ This is called by TextIndexes. A 'query term' which is a string 's' is passed in, along with an index object. s is parsed, then the wildcards are parsed, then something is parsed again, then the whole thing is 'evaluated' """ # First replace any occurences of " and not " with " andnot " s = ts_regex.gsub('[%s]+and[%s]*not[%s]+' % (ws * 3), ' andnot ', s) # do some parsing q = parse(s) ## here, we give lexicons a chance to transform the query. ## For example, substitute wildcards, or translate words into ## various languages. q = self.getLexicon(self._lexicon).query_hook(q) # do some more parsing q = parse2(q, default_operator) ## evalute the final 'expression' return self.evaluate(q)

2 1

RE: XHTML Templates comments from the peanut gallery
by Jay, Dylan 28 Sep '00

28 Sep '00

> However, the focus of the new Template architecture will be a new > format based on XHTML. This XHTML Template will be focused on > giving Site Designers round trip presentation authoring using the > dominant tools such as Dreamweaver. > > XHTML Templates will be complete, well-formed HTML that look like a > resource will look when the XHTML Template is applied to it. There > will be no "source vs. rendered" issue. > > In this Presentation Architecture, Site Designers can start mocking > up a Zope site by editing real HTML and graphics in Zope from the > very beginning. There will be nothing Zope-ish in what they are > doing. > > As the mockups turn into live content, certain regions of the XHTML > Template will be "connected" to the live content. This is done by > indicating the object data that will be inserted when the XHTML > Template is applied to content. This all seems like a good idea but its hard its not very concrete. I proposed something very similar about a year ago. http://lists.zope.org/pipermail/zope-dev/1999-September/001624.html It was an extension to DTML that enabled the use of documents that were rendered html and dtml source combined. This gives you round trip wysiwyg editing without "doing away" with the whole DTML scripting thing. A designer might make a mockup, the coder would then zopify it by putting in iterations etc in DTML as they normally would. The designer could then view the document in "design-mode" that would render the DTML but keep special tags in place around the rendered content that contained the code. Whent the designer saved back this version there would be a spcial "design-mode" compiler that would work out all the DTML objects etc the relevent bits of content (and code) belonged to. Content relating to any object that the designer doesn't have permission to edit or the content was dynamic like from a database, just gets discarded. This solution seems to achieve most of your aims for XHTML but without some of the weird architecture changes. Dylan Jay Avaya Communication.

1 0

XHTML Templates comments from the peanut gallery
by Spicklemire, Jerry 28 Sep '00

28 Sep '00

> >Chris Withers writes: > > A **page** is the result of applying presentation to data in the > > object system. A page is a particular result of a URL when viewed > > under certain conditions. > > ....I'd like to add to this: > components used to make up 'page's should not be URL-visible. Why should > they be? > (would this raise issues with XML-RPC?) > whereupon Dieter Maurer responded: > Because, you want to access them for management purposes (e.g. > change them). and, conceptually at least, this should facilitate displaying the hypothetical "block" resources as "include virtual" sorts of beasties, on the inside of some next generation hyper-editing environment. Zopefully, Jerry S.

1 0

zope2.2.2 - ZopeTime not available to users defined in acl_users below the root? the root?
by ross 28 Sep '00

28 Sep '00

Here's a problem which bit me today. I'd delegated someone to manage a Yihaw directory. zope 2.2.2 source running on a sun. make a folder at the root (eg /foo) with an acl_user folder there define a new user in the foo acl_user folder (eg foobar) with manager/owner rights add a dtml method to view ZopeTime (eg <dtml-var ZopeTime> ) view it and see the current time. It's owned by a real manager and it works as expected. Now, close your browser down and authenticate as foobar and try to view the page. You'll get: Zope Error Zope has encountered an error while publishing this resource. Error Type: KeyError Error Value: ZopeTime Traceback (innermost last): File /udd/rerla/zope222/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /udd/rerla/zope222/lib/python/ZPublisher/Publish.py, line 187, in publish File /udd/rerla/zope222/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: Traversable) File /udd/rerla/zope222/lib/python/ZPublisher/Publish.py, line 171, in publish File /udd/rerla/zope222/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: test) File /udd/rerla/zope222/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: test) File /udd/rerla/zope222/lib/python/OFS/DTMLMethod.py, line 172, in __call__ (Object: test) File /udd/rerla/zope222/lib/python/DocumentTemplate/DT_String.py, line 528, in __call__ (Object: test) KeyError: (see above) Note, it's not unauthorised - it's just not in the namespace. ZopeAttributionButton is defined in the same Application.py but it works fine. I even tried adding ZopeTime__roles__=None to no avail. What gives???

2 1