[Zope-dev] ZPatterns bug: no help subdirectory in PlugIns

2000-10-19 Thread Steve Alexander

PlugIns-0-4-3b1 (part of the latest ZPatterns release).

__init__.py fails because at line 8 context.registerHelp() fails, as
there is no "help" subdirectory in the PlugIns product folder.

I guess this is an empty directory that got missed off when the whole
thing was tarred up.

A simple fix is "mkdir help" from the PlugIns directory.

--
Steve Alexander
Software Enigneer
Cat-Box limited
http://www.cat-box.net

___
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] Reversing symlink namespaces ???

2000-10-19 Thread Shane Hathaway

Phil Harris wrote:
 
 Shane/All,
 
 Anybody using the symlink product?
 
 It seems to me it uses namespaces in the wrong order.  Imagine the hierarchy
 below:
 
 Root
 Folder1
 doc1
 Folder2
 symlink1
 
 Now let's assume that Folder1 has a property 'copyright', and also that
 Folder2 has a property of the same name.
 
 At the moment the 'copyright' from Folder1 is used in preference to the
 'copyright' from Folder2 when viewing the symlink.  Does this seem right?
 
 Anybody got any views, suggestions etc.

This occurs because currently, symlink allows the object to retain its
acquisition context for security.  If you change the line below...

v = ob.__of__(parent)

to this...

v = getattr(ob, 'aq_base', ob).__of__(parent)

...then you'll get the effect you're looking for, but if you allow
others to add or modify symlinks, you just might have a security
problem.

Shane

___
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 )




[Zope-dev] WriteLocking Project Initialized

2000-10-19 Thread Jeffrey P Shell

http://dev.zope.org/Wikis/DevSite/Projects/WriteLocking/FrontPage

WriteLocking became a full fledged Fishbowl Project this week, and I've been
spending the past couple of days getting the initial Artifacts and structure
of the Project site together.  The current structure should stand through
elaboration.  There is no planned schedule yet as the Risks themselves are
still being scoped out and the UseCases haven't even been started on yet,
but it is currently planned to get the proposed functionality into Zope 2.3.

The main pages of interest right now are:

VisionStatement (what the project is about, from the original proposal)
 http://dev.zope.org/Wikis/DevSite/Projects/WriteLocking/VisionStatement

RecentChanges
 http://dev.zope.org/Wikis/DevSite/Projects/WriteLocking/RecentChanges

CurrentStatus (I really will work on keeping this up to date)
 http://dev.zope.org/Wikis/DevSite/Projects/WriteLocking/CurrentStatus

There are other pages outlining

 o RiskFactors (this is the one most actively being worked on right now),
 o TargetClients (LOCKing WebDAV clients we're planning to test against),
 o ProjectGlossary (Terms and definitions)

And the general ProjectDiscussion page at
 http://dev.zope.org/Wikis/DevSite/Projects/WriteLocking/ProjectDiscussion

I ask that if you make comments on the proposal to either do them on the
ProjectDiscussion page or on the [EMAIL PROTECTED] list.  Please read the
Scope section of the VisionStatement first, which outlines both what the
intended goals Are and Are Not.

Remember that the project is still in the early stages of Elaboration, and
some of the artifacts are incomplete.  In light of this election season, I
pledge to you I will try my hardest to go to work 50+ miles south of
Washington and fight to keep the information flowing through the Wiki
updated and available to ALL Zope people, everywhere.  No fuzzy math in
these parts!


___
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 )




[Zope-dev] Lists of Objects

2000-10-19 Thread Jack Fitzgerald



Hello,
I am currently keeping a list of objects 
sorted in a particular object. I am wondering if 
anyone has an opinion about whether I should keep 
just the 'id' in this list or if it is ok
to actually keep a reference to the object in the 
list. When I use the list at a later point in time
I will need to access several attributes of the 
object. If I keep the 'id' I would have to find the object 
for each entry in the list. Thanks in advance for 
any opinions.

-Jack Fitzgerald


Re: [Zope-dev] Lists of Objects

2000-10-19 Thread Ender


please don't post html to this zope mailing lists, many people aren't
using html email readers


 Jack Fitzgerald wrote:
 
 Hello,
  I am currently keeping a list of objects sorted in a particular
 object. I am wondering if
 anyone has an opinion about whether I should keep just the 'id' in
 this list or if it is ok
 to actually keep a reference to the object in the list. When I use the
 list at a later point in time
 I will need to access several attributes of the object. If I keep the
 'id' I would have to find the object
 for each entry in the list. Thanks in advance for any opinions.
 
 -Jack Fitzgerald

depending on your application you could just do it the way zcatalog does
it and store the url and resolve the url to an object when you want to
access attributes.

kapil

___
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 )