Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)
Rik Hoekstra writes: This raises the question how dependent the splitter on the paticularities of the document source - I do not really see how different splitters could be useful for one single document. This is perhaps less obvious than it appears, as you may want to use different splitters for documents in different languages. Taken as a whole I would say choosing a splitter would be a decision that had to be taken at indexing time anyway. But perhaps it's just my imagination that is Of couse, the search must follow the same splitting rules than the indexing did. Changing the rules (the splitter or its configuration) after indexing will make the index inconsistent. I agree; in fact I think we're saying the same. What is more interesting, is how (less than when) you decide to use which splitter. With heterogeneous documents I'd think it would be difficult to decide automagically... Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)
Chris McDonough wrote: It just occurred to me that depending on the splitter to do positions makes it impossible to alter the splitter without reindexing the whole text index... but I think this is a reasonable tradeoff. Other opinions welcome. This raises the question how dependent the splitter on the paticularities of the document source - I do not really see how different splitters could be useful for one single document. This is perhaps less obvious than it appears, as you may want to use different splitters for documents in different languages. Taken as a whole I would say choosing a splitter would be a decision that had to be taken at indexing time anyway. But perhaps it's just my imagination that is lacking. There is a much greater dependence on the lexicon here. And indeed several different lexicons could be applied to a set of documents depending of what is wanted. my 2 cents Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: PossitionIndex (was: Re: [Zope-dev] ZCatalog phrase indexingrevisited)
Once you're satisfied with the implementation, would you be willing submit the module to the collector? Do you think you (or someone else for that matter) could have a look at [1] the method that returns the position in the document - positionInDoc() - to how that could be made to run much faster? Maybe it is how it used... It is too slow to be very useful when indexing large amounts of data. Anyway, I suck at making Python fast (or using it the right way, which ever I've fallen pray for this time ;-), and any hints would be greatly appretiated. I've been indexing and searching a lot this weekend, and bar that problem with the indexing-speed it seems ok and I have no issues submitting it to the Collector. Doing something similar (in fact what I needed was citations of word usage) I took a two step approach, with the idea that most of the actual returning of results would have to be done on a much smaller subset of documents than if you'd have to index all documents with word indexes and positions. I use a normal textindex for querying. Then if a document is returned by the query I start processing the documents. This requires parsing the query in a slightly different way (throw out the NOTs). The two step approach has the advantage that you can postpone processing actual documents until you return the results for the specific documents. Using your positionInDoc will require a _lot_ of processing (why does it use string.split btw and not Splitter?; why split on and not on string.whitespace?). I have used string.find for finding word positions, which is probably faster than looping a list of words. BTW, I'd rather use Splitter, but word positions appeared not to be reliable (bug, or something I didn't understand; anyhow, string.find works for me and is fast) def splitit(txt, word): postions = [] start = 0 while 1: res = string.find(txt, word, start) if res is -1: break else: start = res+1 postions.append(res) return postions sidenotePerhaps using re would perhaps also be an option, but allowing regular expressions will complicate searching a lot, so I use globbing lexicon for expanding and then do the matching on the expanded items (if necessary - not if using [wordpart]*)/sidenote Advantages of using this approach: - it's faster. - it splits up the query processing part in different subparts which also contributes to speeding things up. - it's also more flexible, as you can divide searching and parsing over different webrequests, and even make them dependend on the number of results. For example: why return text fragments from all documents if your users will not be able to see all the results anyway. Or why return all fragments containing word combinations from one single document while returning a few occurrences from different documents is more useful for your users. Note that this will mainly affect returning text fragments, which may or may not be useful. There's also a couple of disadvantages (as I see them , but there may be more): - it only works with exact word positions and not numbers in a text. The within two words approach may be remedied by using string.split on substrings however if really needed. Depending on you purposes an even rougher approach is by taking some default length for words (this is a bit faster). These are not very elegant solutions, though. - because of an approach that is not so coupled with (Z)Catalog, integration strategies are less obvious (at least for me) - the positionIndex might be used for further processing as is, in my approach this is less obvious. another 2 cents Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Deleting objects by the users
one small correction: the line: dtml-call expr="manage_delObjects(getId())" should read: dtml-call expr="manage_delObjects([getId(),])" as the manage_delObjects takes a list as argument hth Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] case insensitive sorts
Andy McKay wrote: Minor nit and patch: I've found that really for me what users want to see is a case insensitive sort of objects, not the current python case sensitive sort. So that the order of objects from dtml-in and tree is a, A, b, B as apposed to A, B, a, b. Anyway Ive patched dtml-in and dtml-tree to do this sort on a ignore_case tag. Is this useful to anyone else? And Ive thought of patching my Zope so this is the default behaviour what does anyone else think. The next thing to patch is ZCatalog... The way I approached this was to have a ZPatterns attribute provider, or a method, that provides a modified version of the value I want to sort on. For example, I have a load of documents and folders with titles like Big Folder brown document "Berries for Cooking" list I wanted to present these sorted by non-case-sensitive first letter or number. So, I made a method "title_for_sorting" that stripped off any punctuation at the start, and returned the first 20 characters in all lower case. In this case, as it was a ZPatterns application, the method was presented as an attribute of the object using some skin-script. I used this attribute as a field-index in my SiteIndex ZCatalog. The reason I mention this is that sometimes case-insensitivity is not enough for sensible sorting. In this case, I had to strip out punctuation too. Hm, reading this... just a loose comment. In light of the awkward search interface of ZCatalogs, would it be a good idea to make a search interface for ZCatalog ZPatterns based? This would add the possibility to make it configurable wrt case sensitivity, and to do nice things with ANDing and ORing different kinds of indexes. The only thing I can't judge whether it would be possible to make this generic enough. for-what-it's-worth Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] How do I create folders/methods etc. within the code?
Some additions: 2. To create folders, mthods etc in the code. I have found some functions manage_addDTMLMethod, manage_addFolder, but how do I use them? well look at their signature in the code eg: self.manage_addFolder(id='Testing') The Zope Help system that comes with your Zope installation gives a contextual help with exactly these methods. Another friend is the Zope Quick Reference (http://zdp.zope.org/projects/zqr). 3. I need to make a site that allows users to register ( i.e. to generate user folder with some standard documents in them). Anyone have hints regarding this? (or in fact a whole application I can use?) Look at GenericUserFolder or LoginManager. As an addition: look at the PTK: it does many of these things for you already and at least it may be a source of information (http://www.zope.org/Products/PTK). The only issue is that it's, um, quite dynamic at the moment if you want to develop code with the PTK as a base. Some might say a moving target. But if you look for inspiration it will be fine on all accounts. hth Rik- ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] ZPatterns: Non-ZODB storage and Racks
[rh]I've been following this thread. This may be a bit of a newbie question, but it's been bugging me for a while. I see how I can store propertysheets in Racks using ZClasses and Skinscripts, but the propertysheet term suggests that there should always be an object that the properties are attached to. Is that an actual ZODB object or is it the Specialist object that can 'create' virtual objects on the fly? It's determined by the radio button setting on the Storage tab. If you neglected to set it to "loaded by accessing attribute " and fill in the blank, then your objects have been stored in the ZODB, as well as in the RDBMS. Roche wrote: Thanks. I set "loaded by accessing attribute" to the attribute "id". Storing items in the RDBMS works fine. But when I try to retrieve them with getPersistentItemIDs() nothing is returned? I have a skinsript method getCustomer: WITH getCustomerSQL(CUSTOMER_ID=self.id) COMPUTE id=CUSTOMER_ID, name=NAME and getCustomerSQL is a SQL method. [rh] If I read this right, this suggests that an object stored in a SQL database and 'masquerades' as a Zope object? Or does an object always have to exist in the ZODB (with it's own id that corresponds to the id in the RDB or knows how to retrieve it). In other words, does the ZPatterns framework need an 'anchor' in the ZODB to connect it's properties to, or can you create pure virtual objects, that retrieve all of their properties from a specialist, including the ID. If the last is the case, could someone give an example how to implement it. A very simple one would suffice I suppose (hope). I hope I expressed my question clearly, 'cos this is difficult matter? tia Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] ZPatterns: Non-ZODB storage and Racks
snip great explanation Thanks, Phillip, that was enlightening Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Re: New Name for Python Methods
Thus the poll did not ask the right question. To be honest, I was surprised that Python Method was still in the poll list. A new poll is not a good alternative, though. Any plans about what to do - take the second best. Re-polling. Apparently it was a bad day for elections in the US in general ;-) (sorry, couldn't resist) Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] mailing list 'noise'
I dont see this as a problem: You only create a new list when the traffic for that proposal gets too great for zope-dev. Threading is good enough before that point. Yes, but zope-dev has a relatively high traffic load... Why should you have to put up with all that 'noise' if you're only interested in posts for your comparatively small discussion? I read the 2-10 articles that I'm probably interested in, and miss the 95% which is almost always noise. The question is why you'd want to receive all this if you don't have to (as remarked above). ...because it is usually a mistake to categorize any discussion as small, to exclude it from the mainstream zope-dev. I started this thread with a request that developers use zope-dev in the way requested by the Fishbowl Process document - but (I assume) it has also been valuable to people thinking about a next-generation wiki. That would not have happened if discussion was partitioned into Wikis (Todays wikis - not VaporWikiNG) unless some WikiNgWiki person was (by coincidence) keeping up with the FishbowlWiki. Are you really advocating that? No, did I sound like I did? as long as you can follow it. But for prolonged and diverging discussions? Not quite IMO/Experience. Can you explain why? Because discussion change topics. Because most people only answer parts of the post. Because you throw away parts of the posts (I know you shouldn't but the mail client is not under your control). Because you loose overview and you can't step back and take a look at the whole thread.. Because no one ever summarizes the discussions. They could, but they won't. I have done these kind of summaries for several intricate Zope related discussions and when you start summarizing it gets very clear that for a larger discussion only parts of the issues involved ever get discussed. Or, to summarize my point, maillist discussion are hardly ever consolidated. It's like having a meeting without an agenda or a chairman who gets the thing going. In the case of a meething once in a while a good chairman/moderator takes back the discussion, summarizes and puts up the open points for further discussion. If you ever experience a meeting that needed someone to guide it, but didn't have one, then you probably know what I mean. Or for discussions that you fall into in the middle? Agreed - Todays Wikis are better than todays email list archives. Ha! ;-) And what if you want to follow discussions at different places, with different tools and you depend on a POP Server or differential access (POP/IMAP/Web) to a mailserver? Its true that the web model is increasingly becoming a lowest common denominator. Are your suggesting that a majority of Zope developers actually need that? Um, I couldn't tell with any certainty. In light of the adoption of Wikis, I suppose so yes. People seem to have been unsattisfied by the maillist and or other discussion tools. It's also remarkable that DC did not adopt Squishdot as a discussion forum, yes. And apart from this, a WikiNG would benefit a much larger community, of which I _am_ sure that it needs it. (Agreed, a VaporWikiNG that does both would be nice) Agreed that for now there are no tools that do such thing. That is also why it's worthwile to get WikiNG out of the vapor notwithstanding the myriad of discussion tools that have been around for many years already. As I understood it, the discussion is less about tools and more about modes of discussion. But we couldnt be having this discussion (in any mode) without tools. did I say that? *My* email and news tools support the mode of discussion that we are advocating *better* than *Todays* Wikis I think everyone agees about that, but at least some of the participants in this discussion also agree that most of the existing discussion tools for any mode of discussion are frustrating and insufficient at times. Moreover, apparently not everyone favours the same mode of discussion and this alone would be more than enough justification for a product that would cater different modes of discussion _at_the_same_time_. Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] mailing list 'noise'
Karl Anderson wrote: Ken Manheimer [EMAIL PROTECTED] writes: I dont see this as a problem: You only create a new list when the traffic for that proposal gets too great for zope-dev. Threading is good enough before that point. Yes, but zope-dev has a relatively high traffic load... Why should you have to put up with all that 'noise' if you're only interested in posts for your comparatively small discussion? Yeah - maillists flow by, and not everyone can follow all the traffic all the time!! The cool thing about "content-based" mailling lists, where people can subscribe to notifications about changes in subthreads, is that you just subscribe to the part of the discussion that has your interests!! I haven't understood this gripe ever since I started reading mail with Gnus. Before anyone groans, I'm not sure that Gnus is ready for general use by anyone who doesn't want to learn elisp - but surely there's anther reader with these features? most have features a bit/lot/sufficiently like this. They (apparently) do not work for everyone. Moreover,not everyone works the same way. The point that I'm trying to make is that a mailing list has all the strucure needed to keep abreast of an important thread. I don't think it's perfect when you can't afford to miss a single important article, but it works great for general lists. as long as you can follow it. But for prolonged and diverging discussions? Not quite IMO/Experience. Or for discussions that you fall into in the middle? And what if you want to follow discussions at different places, with different tools and you depend on a POP Server or differential access (POP/IMAP/Web) to a mailserver? I read the 2-10 articles that I'm probably interested in, and miss the 95% which is almost always noise. The question is why you'd want to receive all this if you don't have to (as remarked above). As I understood it, the discussion is less about tools and more about modes of discussion. Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] I feel your Wiki Pain ;-)
Do you feel that weblogs are bad models for debates? I think they're pretty good least-common-denominators. I would probably prefer the kind of annotation-based thing i described in my last message (and began to sketch in the WikiNG proposal) for collaborative generation of documents, but i can see the place for weblogs, just as i can see a place for network chats. With adequate integration of email (for notification and response), i see them as better than just email... I like the email list proposal of Martijn Faassen earlier on this list. I added some comments to the Wiki discussion page, where someone proposed using XML for Wikis: I agree with Peter that the proposal is practically shouting XML all over the place. In a Zopish way this would mean dividing up a Wiki page in different objects (say Topics or Paragraphs or whatever). So a Wiki page would become an XML document, consisting of Wiki node documents. The advantage is that this would allow for a presentation in the form of - one or several continuous pages as in the OFWikis (OF=Old Fashioned as opposed to NG). - a presentation with 'folded' nodes (like in a folding editor) - a threaded discussion a la S[qu|w]ishdot or the Discussable thingy - an XML document (for who would want it) The editing could be in the form of Martijn Faassens XML Widgets editor: put a node point in front of a 'discussable' node, promote that one to the top when the 'node point' is clicked on and allow for editing. An example below, in which the o stands for an editable (=clickable) node point (for wiki reasons I have not put blank lines between them. pre o this is the first editable node (user::time) this is a comment to it (user::time) and another comment to that (user::time) this another one (user::time) more comments o this the second one this one is not editable o this one is (user::time) a commennt to the last node /pre alternate view (in threaded discussion mode - probably know to all): (- is foldable; + is expandable) pre -This is the first editable node + this is a comment to it - this another one - and another one to that - this the second one this one is not editable +this one is /pre another 2 cents Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] ODBC Error
There _was_ a patch available (can't find it now, search the maillist archives) Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] is INSTANCE_HOME broken on Win32?
Any ideas? the python way of getting the right path separators is to use os.path.join(item1, item2, ...) Works even for macs ;-) Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Render DTML without having it in a Zope object
I have some HTML/DTML saved in the database and I want to now display it. What database - something different then data.fs probably? But before I display, I need to render the DTML that is contained in the text. Can anyone lead my in the right direction; maybe by telling me which file handles the rendering and I can read some source code. But of course, it would be cool, if I could get a more explained response. BTW, I can call the method to render the text from Python or DTML. I really don't care. You'd have to feed it to zopehome/lib/python/DocumentTemplate/DT_HTML.py and use the String method, probably. It is not completely clear to me what you try to do. Is it indirect dtml calling - this could be difficult (your best bet would be to use an external method methinks). If not, why can't you include it like any normal DTML Method? HTH (if only slightly) Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Call for a creation_datetime property!
"Jay, Dylan" wrote: It is really a painful thing to do without. I realize I can add this capability to factories of my own objects but I don't want to have to create my own versions of dtml-document and everything else just to ensure that a creation date is kept. I've tried using transaction logs but this is very dodgy for the following reasons. 1) An object can be created by many different methods. Its guess work working out which created the object. 2) The odb can be packed and then you've just lost your creation date. Can anyone give a good reason not to include this property as a standard for all ZODB objects? A me too here Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Zope as CGI with IIS Windows 2000 Server
URGENT! Need assistance with Zope as a PCGI with IIS 5 on Windows 2000 server. After configuring Zope for use as a PCGI, and configuring IIS to use the pcgi-wrapper.exe, etc... The test link:http://localhost/Scripts/Zope.pcgi ...is returning the following message within the "Temporarily Unavailable" error response page: !-- Error parsing pcgi info file pcgi-wrapper-version 2.0a4 -- I have tested the file using parseinfo and get no response. what do you mean by no response? Is it not returning anything or just no errors? A theory, at this point has been that there is a conflict/incompatibility with Zope as a PCGI with IIS 5.0 on Windows 2000. This seems to be a pcgi (Zope) error though. Only used it on NT4 and IIS4 but from the above a basic incompatibility seems unlikely (to me). Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Zope Content Management System
Hi there, I am working on a project and have been looking at the Zope Content Management System as part of the solution. However, I have a couple of questions. From what I have seen so far, the page generation is all done through the Zope Management Interface, and the content of the page is done through a textarea requiring the user to have knowledge of the zope system(DTML) and HTML. With type type of solution I am looking for however, I need page content to be generated be users that have little or no knowledge of HTML. What I am wondering is if it is possible to integrate the Zope content management system with Cold Fusion as I can allow users with no knowledge of HTML to use an interface designed with Cold Fusion to create page content. I do not wish to build a content management system from scratch with Cold Fusion. Any suggestions and/or comments would be very helpful. Um, intergration with Cold Fusion would be strange I think. WHat your question is, probably, is whether you can you wysiwyg HTML editors with Zope. Some minor inconveniences aside that mostly have to do with file extensions, the answer is yes. As Zope speaks ftp and WebDAV and a host of other protocols, you can easily prepare Zope content with tools like HomeSite and Dreamweaver (and many other tools). Just try it out on a Zope installation hth Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] why is manage_addZSQLMethod unavailable ?
Why does this work
dtml-call "_['testadd'].manage_addDTMLMethod('MethodId', 'Method
Title','method text')"
While this does not:
dtml-call "_['testadd'].manage_addZSQLMethod('ZSQLID', 'ZSQL Title',
'DB','','select * from data')"
Error Type: AttributeError
Error Value: manage_addZSQLMethod
I studies the Znolk product and found that it uses _setObject directly
instead of
manage_addZSQLMethod .
In general there is an inconsistency in adding objects: sometimes you can
use the manage_addYourProduct interface, and sometimes only going through
the addProduct invocation (don't have the whole thing handy here) will do
the trick. This can get very confusing. Wouldn't know if that's the matter
here, though. I think this should be standardized in the interfaces.
but it IMHO the visibility of manage_addDTMLMethod and manage_addZSQLMethod
_should_ be the same ?
I agree
___
Zope-Dev maillist - [EMAIL PROTECTED]
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 )
Re: [Zope-dev] Recursively adding ZClasses (continued)
snip Thanks for replying Kevin, but it won't work ;-( I tried it ALL, and it _will_not_work_. The nested ZClasses will apparently solve it (I used it elsewhere), but it will get you into trouble in other situations - if you want to add an instance of the nested zclass to an existing instance of that same nested zclass. I had to change my product before because of that. I'm using nested ZClasses in KM|Net News. Take a look at the AddArticle method. In KMNN, these ZClasses are set up as nested ZClasses, so that may change things somewhat. However, it may still work. Rather than doing manage_addProduct[], you *might* be able to just directly call ZClass_add(_.None, _), because it could be in your acquisition path at the top of the product. In KMNN, that's all I had to do, but in that case the ZClass_add method was located within the ZClass that was to contain it. That sounded kind of rambling, so I hope it makes sense... No matter if you use ZClass_add directly or in dtml-with. No matter if you close the first dtml-with and open another. No matter if you redirect to get out of namespace problems (that will _really_ give strange errors). Believe me, it was a _very_ frustrating experience (and I really wanted to refrain from ranting -just couldn't help myself) thanks again for replying Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Calling DTML methods from Python
Andrew Wilcox wrote: OK, I'll set up a DTML Quick Reference on the ZDP site right now! It's link is http://zdp.zope.org/portals/beginners/DQR We should be able to get this in place. Contributions sought! Do you want me to include my text? Where would it go? Yes. Hm, this is already rather specific. I'll paste it into a section (Topic) called Calling DTML. We may need to revise the topics afterwards, but that doesn't really matter now. Note that you can make your own topics (at least I think you can). Last night I couldn't finish it, but I thought the idea would be there as is. I'll try and work on it a bit today. thanks Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Cataloging LocalFS content
I think, cataloging "LocalFS" content would be nice. I have the following problems with it: 1. "LocalFS" defines various meta types: "Local File System", "Local Directory" and "Local File". Only "Local File System" is a "true" meta type which should appear in the available objects list of ObjectManager's. However, I may well be useful, to select the others, too, in for "find" and cataloging. This could be done, but my concern is that when changes are made to the file system this will cause the catalog to be out of synch until you re-index. How does this work with Zope objects? If you move or delete a Zope object that is cataloged does it automatically update the catalog? Only if it is 'Catalog Aware', otherwise you'll have to update it manually. In the case of LocalFS this will always be the only way. Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
Re: [Zope-dev] Calling DTML methods from Python
Is it just me or is there a lot of confusion between the terms namespace, self, client, and the REQUEST object (which, unlike it's name implies, seems to contain a lot more than stuff relating to the HTTP request, like the RESPONSE object, for example ;-) Perhaps this could be shaken down and then, a first for the Zope community I believe ;-), _documented_ somewhere!!! OK, I'll set up a DTML Quick Reference on the ZDP site right now! It's link is http://zdp.zope.org/portals/beginners/DQR We should be able to get this in place. Contributions sought! Rik ___ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
