Re: [Zope-dev] Collector Status Meanings

2004-07-30 Thread Marc Lindahl
I would put my $0.02 for a 'tested' state, entered from Resolved.  So 
from resolved you could 'resubmit' back to pending or accepted, or go 
to tested.  This because it does happen, that someone *thinks* they 
have fixed something, but didn't test it thoroughly (there are usually 
way to many combinations for one person to do so), and it wasn't really 
fixed.

On Friday, July 30, 2004, at 10:01  AM, Chris Withers wrote:
Hi All,
Apologies for the cross-posting, but I think this is relevent to all 
these lists.

I've summarised the meaning of the various collector states here:
http://dev.zope.org/CVS/CollectorStatuses
Please let me know if you disagre with any of that, although I'm 
pretty sure they're right and will argue with anyone who thinks 
otherwise ;-)

The only real change is that Deferred now means we asked the user for 
more information and we'll reject the issue unless they give it to us 
within a month

I went through all the issues which WERE deferred and dealt with 
them.
I'm trying to avoid having states where issues end up that aren't 
definitive and so get forgotten about.

The wontfix stuff now has a definitve meaning, but it may still be 
good to go through them all once a year or so to check that none of 
them have been solved in other ways. I found quite a few of the 
deferred ones that really should have been wontfix had been 
addressed and could now be marked as resolved :-)

cheers,
Chris
--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Streaming large files

2004-07-09 Thread Marc Lindahl
On Thursday, July 8, 2004, at 01:07  PM, Thilo Staebler wrote:
hi!
I have to stream large mpeg-files over http with range support. this 
works quite nice until the client seeks in the (media)player and the 
files aren't to large, because zope caches the whole file...
...so each seek means streaming the whole file from the requested 
position till end *g*
- my RESPONSE object doesn't even know, that the player has seeked 
e.g. back to the beginning...
is there a way to bypass the zope caching? and how do I know if the 
player has disconnected, so I can stop streaming?
you mean cacheing in memory?  Anything based on File does not do that.


thanks in advance
thilo
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Image.tag() no longer publishable?

2004-03-04 Thread Marc Lindahl
If you're using Plone, it monkeypatches Image.tag().  Caused me to add 
an Image.pil_tag() monkeypatch to my monkeypatch ImageTag_CorePatch :)

On Thursday, March 4, 2004, at 04:38  PM, Paul Winkler wrote:

I used to be able to browse to an image's tag method
and see its output in my browser.  This worked in zope 2.6.1
and apparently stopped working in 2.6.2.  Anybody know why?
I don't see ANY changes to Image.py between 2.6.1 and 2.6.2.
In 2.6.2, 2.6.4, and 2.7.0 I get the missing docstring error:

The object at http://localhost:8080/foo.jpg/tag
has an empty or missing docstring. Objects must have a docstring
to be published.
Well, that's a bald-faced lie... Image.tag has a nice long docstring!
What the heck? Is this maybe a side-effect of a security fix
somewhere else?
It's very inconvenient, I used this technique to embed zope images
in JSP's and all those pages are now broken.
Any clue would be appreciated.
--

Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's SUBORDINATE FROM IDAHO!
(random hero from isometric.spaceninja.com)
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Image.tag() no longer publishable?

2004-03-04 Thread Marc Lindahl
I changed ImageTag_CorePatch to also do the border=0 default patch.

On Thursday, March 4, 2004, at 08:26  PM, Andy McKay wrote:

Marc Lindahl wrote:
If you're using Plone, it monkeypatches Image.tag().  Caused me to 
add an Image.pil_tag() monkeypatch to my monkeypatch 
ImageTag_CorePatch :)
Oh I wish we could get that into Zope so it actually puts out an image 
tag *by default* without a border. Sigh.
--
  Andy McKay
  ClearWind Consulting
  http://www.clearwind.ca

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Image.tag() no longer publishable?

2004-03-04 Thread Marc Lindahl
On Thursday, March 4, 2004, at 10:14  PM, Paul Winkler wrote:

From OFS.Image.tag in zope 2.7.0:
if not 'border' in [ x.lower() for x in  args.keys()]:
result = '%s border=0' % result
... that's been in there for about 3 years!
If you want to force no border attribute, you can pass it
a false value.

That's similar to mine:

if not 'border' in map(string.lower, args.keys()):
result = '%s border=0' % result
...but yeah, CSS is better



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Serving big files thru zope?

2004-03-02 Thread Marc Lindahl
On Monday, March 1, 2004, at 02:43  PM, Dieter Maurer wrote:
In order to reduce memory consumption and decouple Zope from
ZServer (and the response delivery), a large file
is spooled via a temporary.
This means, that the file content is read from ZODB, stored
in a temporary file and then delivered from this temporary file.
At least, when your client has a high bandwidth to your server,
this serving through a temporary file is a waste.
I found that putting my /var partition (the default place for zope's 
temp files) on a very fast SCSI disk with plenty of space (GB's) 
improved the situation tremendously

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Zope 2.7 b3 problem with reindexing catalog

2003-11-23 Thread Marc Lindahl
Probably you're trying to index non-CMF non-plone objects - you can get 
a similar error with plain CMF if you have non-CMF objects that you try 
to index.  I think what you have to do is clear the catalog and then 
use the 'find objects' page to reindex, only select the object types 
which are plone/CMF.

On Thursday, November 20, 2003, at 12:28  AM, robert wrote:

I did some more investigation:
The problem does occur when a CMF portal_catalog is  reindexed.
It does not happen with plain catalog
Robert
Am Mittwoch, 19. November 2003 17:40 schrieb Andreas Jung:
I can not reproduce this. Can you give us detailed description how to
reproduce it
or track it down on your own?
-aj

--On Mittwoch, 19. November 2003 17:15 Uhr +0100 robert 
[EMAIL PROTECTED]

wrote:
If I try to reindex a (plone) portal_catalog I get the following 
error

Traceback (innermost last):

* Module ZPublisher.Publish, line 100, in publish
* Module ZPublisher.mapply, line 88, in mapply
* Module ZPublisher.Publish, line 40, in call_object
* Module Products.ZCatalog.ZCatalog, line 474, in 
manage_reindexIndex
* Module Products.ZCatalog.ZCatalog, line 459, in reindexIndex

TypeError: catalog_object() got an unexpected keyword argument
'update_metadata'
Display traceback as text
--
mit freundlichen GrĂ¼ssen
Robert Rottermann
www.redCOR.ch
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Re: stacks != easy to explain

2002-05-18 Thread Marc Lindahl

 Well, no, not really. Being able to edit stuff remotely is where Zope's
 real strength
 lies. WebDAV and FTP are much better than using sucky HTTP forms to do
 this ;-)

The fact that Zope has a TTW interface indicates that the software itself
has the opinion that TTW is valuable - otherwise it would not be in there.
So this statement is at odds with the software itself (in other words, it's
a wish...)



___
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: stacks != easy to explain

2002-05-14 Thread Marc Lindahl

on 5/14/02 4:43 AM, Chris Withers at [EMAIL PROTECTED] scrivened:

 Marc Lindahl wrote:
 
 Sorry, but I don't see a 'stack' of any sort being easy to explain to a
 newbie
 or not programmer.
 
 I'd disagree - HTML has this concept - for example the way table tags
 inherit properties.  Key is that the 'stack' idea is hidden within the
 hierarchy idea.
 
 Hmmm... do you knnow how many people get confused by that specifc issue?
 Especially as
 different browsers inherit different levels of formatting...


I think the confusion on that issue with tables has only to do with the bugs
in the implementation on certain browsers.  Which points to the inability of
supposedly real programmers to understand stacks, parsing, state machines -
not the poor HTML coders :)  - if you read diatribes by the layout guys
(like alistapart) you'll see their frustration is based that the heirarchy
(stacking) isn't working as expected.



___
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] 'not:' kludgey?!

2002-05-14 Thread Marc Lindahl

on 5/14/02 4:41 AM, Chris Withers at [EMAIL PROTECTED] scrivened:
 
 Okay, repeat the mantra over to yourself:
 
 Templating languages are not procedural languages

Sounds nice, but what does it mean?  AFAIK a procedural language is
something that has a definite order of execution... How does a templating
language differ?

 Can you give any material that actually backs up these sweeping claims? ;-)
 
 Prone to errors: when changing the condition, have to duplicated edits in 2
 places,
 
 No you don't. Do I have to say that a third time? ;-)

Referring to, not the construct you exemplified, but the previous one in the
thread (can't find it in the archive right now)




___
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] ZPT and 'else'

2002-05-13 Thread Marc Lindahl

on 5/10/02 1:18 PM, Jeffrey P Shell at [EMAIL PROTECTED] scrivened:

 
 Still, yuck.  It's - for better or worse - not a valid XML way.  Even XSLT
 does things like this:
snip

Well that makes this look palatable:


 
 You would at the very least need something like:
 condition
 if.../if
 elif.../elif
 else.../else
 /condition

Still I think the concept of TAL having some kind of 'stack' for condition
results makes sense and is worth exploring...  Could yield better logical
constructs, and things like case statements.



___
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] 'not:' kludgey?!

2002-05-13 Thread Marc Lindahl

on 5/10/02 11:32 AM, Chris Withers at [EMAIL PROTECTED] scrivened:

 Marc Lindahl wrote:
 
 Don't you have that now with the kludgey 'not' construct?
 
 What is kludgey about the 'not:' construct?!

For the reasons 'else' was invented in the first place, I guess:  prone to
errors, inefficient, bulky.  The biggest thing I see is: isn't linked to the
other construct, so it's prone to errors when editing the conditions.



___
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] 'not:' kludgey?!

2002-05-13 Thread Marc Lindahl

on 5/13/02 3:11 PM, Chris Withers at [EMAIL PROTECTED] scrivened:

 
 For the reasons 'else' was invented in the first place,
 
 'else' in what context?!

Meaning, in procedural languages.

 
  I guess:  prone to
 errors, inefficient, bulky.
 
 Can you give any material that actually backs up these sweeping claims? ;-)

Prone to errors: when changing the condition, have to duplicated edits in 2
places, so you could make an error which would be hard to track down.
Inefficient: have to evaluate an expression twice (unless someone makes a
jit compiler!)
Bulky: in terms of taking more space in the source file, without clarifying
what's being done.

 
 The biggest thing I see is: isn't linked to the
 other construct, so it's prone to errors when editing the conditions.
 
 Well, I've already shown the way I'd do this which only has the condition in
 one
 place

Yes you did, and re-reading the TAL wiki
(http://www.zope.org//Wikis/DevSite/Projects/ZPT/TAL%20Specification%201.2)
it's clear that your approach is the one the language is designed for.
Also, your approach can easily accommodate other logic structures like case
statement.  Well, I guess I'm convinced!



___
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] Re: stacks != easy to explain

2002-05-13 Thread Marc Lindahl

on 5/13/02 3:15 PM, Chris Withers at [EMAIL PROTECTED] scrivened:

 Marc Lindahl wrote:
 
 Still I think the concept of TAL having some kind of 'stack' for condition
 results makes sense and is worth exploring...  Could yield better logical
 constructs, and things like case statements.
 
 Sorry, but I don't see a 'stack' of any sort being easy to explain to a newbie
 or not programmer.

I'd disagree - HTML has this concept - for example the way table tags
inherit properties.  Key is that the 'stack' idea is hidden within the
hierarchy idea.



___
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] ZPT and 'else'

2002-05-10 Thread Marc Lindahl

on 5/10/02 12:47 AM, Jeffrey P Shell at [EMAIL PROTECTED] scrivened:

 
 You would need something to close off the 'if' statement, otherwise, a
 document full of 'if' statements and no 'else' ones could fill up a stack
 needlessly.

What's so bad about that?  The stack wouldn't carry over after html/html
or body/body - couldn't practically more than 1000's - insignificant!

 
 You would at the very least need something like:
 condition
 if.../if
 elif.../elif
 else.../else
 /condition
 
 Which would ensure / cut back on needless growth of stacks and/or global
 variables.
 
 Personally, I think the way Page Templates can do it (via a 'not'
 expression) is fine.  When I used it today (and in the past), I never felt
 myself missing 'else', because there's not really an 'if' to begin with.
 Just conditions.  It keeps TAL light, and lets TALES take on the lifting of
 how to write those conditions.

Point is, it's slow and inefficient, and a clunky syntax.  Reasons the whole
idea of 'else' was invented in the first place.  I worry, that ZPT is
benchmarked 4x slower than DTML and it's becoming the standard - not a step
forward.  And issue like this haven't been satisfactorily resolved.

I think, if it's going to have logic in there, make it sufficiently powerful
and efficient.  Otherwise get rid of it altogether, unapologetically, and
require Python for such things




___
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] ZPT and 'else'

2002-05-10 Thread Marc Lindahl

on 5/9/02 11:58 PM, Tim Hoffman at [EMAIL PROTECTED] scrivened:

 The big problem with the whole 'else' issue as I see
 it, is that non coders, using dreamweaver etc.. would no doubt end
 up with both bit's of html in their template.
 


Don't you have that now with the kludgey 'not' construct?



___
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] ZPT and 'else'

2002-05-09 Thread Marc Lindahl

Yecch!

Why not:
if ...
True stuff
/if
else
False stuff
/else

If leaves around boolean result, else picks up the most recent one... It's
like they push on a stack so you can nest them Something like that?


on 5/9/02 11:10 PM, Jeffrey P Shell at [EMAIL PROTECTED] scrivened:

 'else' is tricky within the block oriented structure of anything XML-ish,
 because of the concept of 'well-formedness'.  The 'if' statement would have
 to be singly wrapped, and the else block wrapped separately, looking at
 least somewhat awkward any way you go about it.  The best I can come up with
 in my mind is this, in order to have the 'else' pick up on the condition
 expressed in its surrounding container.  But, yuck:
 
 if ...
 true stuff
 else
 false stuff
 /else
 /if
 
 
 A good page template way is something like this:
 
 tal:if condition=myTalesExpression
 truth
 /tal:if
 tal:else condition=not:myTalesExpression
 false
 /tal:else
 
 The 'not' TALES namespace is valuable.  The downside is that you evaluate
 the expression twice.  A good way to work within this is something that I
 did earlier today, outside of this conversation, where I evaluate an
 expression earlier and assign it to a variable:
 
 div id=edit-area
tal:define=editItems python:here.getMenuItem(...)
 
 h3Edit Menu Items/h3
 form action=Delete method=post name=actForm
   tal:condition=editItems
 
... (form and table elements, and a loop over editItems
 contained in here if there were results) ...
 
 /form
 
 div class=emph
  tal:condition=not:editItems
  No menu items available
 /div
 
 /div
 
 
 This is something I did a lot in DTML too, setting a search result to either
 a global variable, or inside of a large dtml-let namescape



___
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] ZMI: IE6 TextArea width bug: fix on tap for 2.6?

2002-03-18 Thread marc lindahl

There's a couple good starting points for looking at this stuff...

http://www.alistapart.com/stories/fear4/
http://www.alistapart.com/stories/dao/

 From: Jeff Kowalczyk [EMAIL PROTECTED]
 Date: Sun, 17 Mar 2002 16:12:44 -0500
 To: [EMAIL PROTECTED]
 Subject: [Zope-dev] ZMI: IE6 TextArea width bug: fix on tap for 2.6?
 
 I was wondering if there was any consensus on how best to fix or
 compensate for the unfortunate behaviour of IE6 with regards to the
 width calculation of textarea boxes. For anyone who hasn't seen it, the
 full-width texareas that are everywhere in the ZMI suddenly started
 pushing the width out in IE6, causing the horizontal scrollbar to become
 active, and generally making ZMI editing life miserable.
 
 Would it be possible to include in 2.6 (or 2.5.1, even better) a user
 preference, sitewide configuration setting, or other means of
 suppressing a few pixels/percent of that default width? I'm loathe to
 apply a massive search-replace to put 95% in my local ZMI source, and
 IE6 must be a common enough platform for Zope users to warrant a
 workaround. I wouldn't hold my breath that MS would fix IE or anything
 sensible like that.
 
 It would be a shame to slow the whole thing down with browser detection
 logic for this one bug, unless that opened up the door for some of the
 Javascript/DHTML editors as a per-user preference for editing certain
 metatypes.
 
 
 ___
 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 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: MonkeyPatching in the Core (was: Zope 2.6planning)

2002-03-04 Thread marc lindahl

What about something like apple's Extension Manager, where you could
disable/enable 'sets' of products?  Though frankly, it's not too tough to
just move the subdirectory somewhere and restart...  but it would be a way
to have a TTW way of configuring your Zope, and having the option of
'loading up' the distribution with optional stuff (which might be disabled
by default?)

 From: Adrian Hungate [EMAIL PROTECTED]
 
 I think that monkeypatching goes right to the very heart of the language -
 Python was written not just to allow it, but it's opperation almost
 encorages it (Sort of). HOWEVER, I am somewhat against a monkeypatch being
 made part of the core distribution (No disrespect to the authors of such
 products - me included), these should be optional downloads, up to the point
 that the code is rolled into the core codebase.


___
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 2.6 planning - call for contributors!

2002-03-01 Thread marc lindahl

I would say, make SSL part of the standard z2.py, so you can turn on/off,
specify address, etc. of https ports just as you do with http ports (and of
course integrated with siteaccess2, etc.)


___
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 2.5.0 and VirtualHostMonster

2002-01-28 Thread marc lindahl



 From: Trevor Toenjes [EMAIL PROTECTED]
 Date: Mon, 28 Jan 2002 17:16:12 -0500
 To: Jesus Cea Avion [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject: RE: [Zope-dev] Zope 2.5.0 and VirtualHostMonster
 
 We are considering upgrading from 2.4.0 to 2.5.0.  Does the same issue apply
 to EnhancedVHM?
 

I was just testing 2.5 with that and don't see this bug


___
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 to accept an arbitrary parameter/anti-NIMDAscript

2001-09-30 Thread marc lindahl



 From: Dieter Maurer [EMAIL PROTECTED]
 thing.  But how can I get an object called default.ida to accept anything
 passed after the ? and what kind of object (python script?) should it be?
 It can be anything with an explicit or implicit REQUEST parameter.

Meaning DTML method or PythonScript, but not DTML document?


___
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] Vulnerability: attacking can get file list and directory

2001-09-24 Thread marc lindahl



 From: Chris Withers [EMAIL PROTECTED]

 The traceback should _not_ be _appended_ to the error message. If an app
 developer chooses to show it, then fine they can as they do already (mine
 sends
 me an error email ;-), but why should it be appended in all circumstances

Be careful of that -- I recently got *flooded* with error emails from a
recent bout of the Code Red worm looking for files that weren't on my server
:(


___
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] problems compiling zope-2.3.3 source under YDL 2.0

2001-07-12 Thread marc lindahl

I'm having problems compiling the Zope source under Yellow Dog Linux (PPC)
2.0 (which is basically RedHat 7.0) can anyone offer a suggestion based
on the traceback?

here 'tis:



[zope@ydl Zope-2.3.3]$ python wo_pcgi.py


--
Compiling python modules


--
Building extension modules
cp ./lib/python/Setup15 ./lib/python/Setup


Compiling extensions in lib/python
cp /usr/lib/python1.5/config/Makefile.pre.in .
make -f Makefile.pre.in boot PYTHON=/usr/bin/python
rm -f *.o *~
rm -f *.a tags TAGS config.c Makefile.pre python sedscript
rm -f *.so *.sl so_locations
VERSION=`/usr/bin/python -c import sys; print sys.version[:3]`; \
installdir=`/usr/bin/python -c import sys; print sys.prefix`; \
exec_installdir=`/usr/bin/python -c import sys; print sys.exec_prefix`; \
make -f ./Makefile.pre.in VPATH=. srcdir=. \
VERSION=$VERSION \
installdir=$installdir \
exec_installdir=$exec_installdir \
Makefile
make[1]: Entering directory `/usr/local/zope/Zope-2.3.3/lib/python'
sed -n \
 -e '1s/.*/1i\\/p' \
 -e '2s%.*%# Generated automatically from Makefile.pre.in by sedscript.%p' \
 -e '/^VERSION=/s/^VERSION=[]*\(.*\)/s%@VERSION[@]%\1%/p' \
 -e '/^CC=/s/^CC=[  ]*\(.*\)/s%@CC[@]%\1%/p' \
 -e '/^CCC=/s/^CCC=[]*\(.*\)/s%#@SET_CCC[@]%CCC=\1%/p' \
 -e '/^LINKCC=/s/^LINKCC=[  ]*\(.*\)/s%@LINKCC[@]%\1%/p' \
 -e '/^OPT=/s/^OPT=[]*\(.*\)/s%@OPT[@]%\1%/p' \
 -e '/^LDFLAGS=/s/^LDFLAGS=[]*\(.*\)/s%@LDFLAGS[@]%\1%/p' \
 -e '/^LDLAST=/s/^LDLAST=[  ]*\(.*\)/s%@LDLAST[@]%\1%/p' \
 -e '/^DEFS=/s/^DEFS=[  ]*\(.*\)/s%@DEFS[@]%\1%/p' \
 -e '/^LIBS=/s/^LIBS=[  ]*\(.*\)/s%@LIBS[@]%\1%/p' \
 -e '/^LIBM=/s/^LIBM=[  ]*\(.*\)/s%@LIBM[@]%\1%/p' \
 -e '/^LIBC=/s/^LIBC=[  ]*\(.*\)/s%@LIBC[@]%\1%/p' \
 -e '/^RANLIB=/s/^RANLIB=[  ]*\(.*\)/s%@RANLIB[@]%\1%/p' \
 -e '/^MACHDEP=/s/^MACHDEP=[]*\(.*\)/s%@MACHDEP[@]%\1%/p' \
 -e '/^SO=/s/^SO=[  ]*\(.*\)/s%@SO[@]%\1%/p' \
 -e '/^LDSHARED=/s/^LDSHARED=[  ]*\(.*\)/s%@LDSHARED[@]%\1%/p' \
 -e '/^CCSHARED=/s/^CCSHARED=[  ]*\(.*\)/s%@CCSHARED[@]%\1%/p' \
 -e '/^SGI_ABI=/s/^SGI_ABI=[]*\(.*\)/s%@SGI_ABI[@]%\1%/p' \
 -e '/^LINKFORSHARED=/s/^LINKFORSHARED=[
]*\(.*\)/s%@LINKFORSHARED[@]%\1%/p' \
 -e '/^prefix=/s/^prefix=\(.*\)/s%^prefix=.*%prefix=\1%/p' \
 -e 
'/^exec_prefix=/s/^exec_prefix=\(.*\)/s%^exec_prefix=.*%exec_prefix=\1%/p' \
 /usr/lib/python1.5/config/Makefile sedscript
echo /^#@SET_CCC@/d sedscript
echo /^installdir=/s%=.*%= /usr% sedscript
echo /^exec_installdir=/s%=.*%=/usr% sedscript
echo /^srcdir=/s%=.*%= .% sedscript
echo /^VPATH=/s%=.*%=  .% sedscript
echo /^LINKPATH=/s%=.*%=   % sedscript
echo /^BASELIB=/s%=.*%=% sedscript
echo /^BASESETUP=/s%=.*%=  % sedscript
sed -f sedscript ./Makefile.pre.in Makefile.pre
/usr/lib/python1.5/config/makesetup \
 -m Makefile.pre -c /usr/lib/python1.5/config/config.c.in Setup -n
/usr/lib/python1.5/config/Setup.thread /usr/lib/python1.5/config/Setup.local
/usr/lib/python1.5/config/Setup
make -f Makefile do-it-again
make[2]: Entering directory `/usr/local/zope/Zope-2.3.3/lib/python'
/usr/lib/python1.5/config/makesetup \
 -m Makefile.pre -c /usr/lib/python1.5/config/config.c.in Setup -n
/usr/lib/python1.5/config/Setup.thread /usr/lib/python1.5/config/Setup.local
/usr/lib/python1.5/config/Setup
make[2]: Leaving directory `/usr/local/zope/Zope-2.3.3/lib/python'
make[1]: Leaving directory `/usr/local/zope/Zope-2.3.3/lib/python'
make
gcc -fPIC  -I../Components/ExtensionClass -g -O2 -I/usr/include/python1.5
-I/usr/include/python1.5 -DHAVE_CONFIG_H -c
./../Components/ExtensionClass/ExtensionClass.c
./../Components/ExtensionClass/ExtensionClass.c:60: stdio.h: No such file or
directory
In file included from ../Components/ExtensionClass/ExtensionClass.h:114,
 from ./../Components/ExtensionClass/ExtensionClass.c:61:
/usr/include/python1.5/Python.h:57: stdio.h: No such file or directory
/usr/include/python1.5/Python.h:58: string.h: No such file or directory
/usr/include/python1.5/Python.h:59: errno.h: No such file or directory
/usr/include/python1.5/Python.h:61: stdlib.h: No such file or directory
In file included from
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.3/include/syslimits.h:7,
 from
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.3/include/limits.h:11,
 from /usr/include/python1.5/longobject.h:58,
 from /usr/include/python1.5/Python.h:76,
 from ../Components/ExtensionClass/ExtensionClass.h:114,
 from ./../Components/ExtensionClass/ExtensionClass.c:61:
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.3/include/limits.h:117: limits.h:
No such file or directory
In file included from /usr/include/python1.5/Python.h:97,
 from 

Re: [Zope-dev] problems compiling zope-2.3.3 source under YDL 2.0

2001-07-12 Thread marc lindahl

That was it... neglected to install glibc-devel
If anyone wants it, I guess I can gzip the build up...
THanks Andreas!!!
Marc

 From: Andreas Jung [EMAIL PROTECTED]
 Organization: Andreas Jung
 Reply-To: Andreas Jung [EMAIL PROTECTED]
 Date: Thu, 12 Jul 2001 15:30:51 -0500
 To: marc lindahl [EMAIL PROTECTED], [EMAIL PROTECTED]
 Subject: Re: [Zope-dev] problems compiling zope-2.3.3 source under YDL 2.0
 
 
 /usr/include/python1.5/mymalloc.h:57: stdlib.h: No such file or directory
 ^^^
 
 Looks like your compiler installation is broken or you don't have any header
 files installed. Please check if you can find the file 'stdlib.h' somewhere
 on
 your system.
 
 
 
 


___
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] Patching Zope Products .. next Question

2001-07-11 Thread marc lindahl

Would this approach be appropriate?

http://dev.zope.org/Members/Caseman/Dynamic_HotFix_News/Dynamic_Hotfix

 From: Ulrich Eck [EMAIL PROTECTED]
 Date: Wed, 11 Jul 2001 19:33:15 +0200
 To: ZOPE-DEV Mailingliste [EMAIL PROTECTED]
 Subject: [Zope-dev] Patching Zope Products .. next Question
 
 can I do this with:
 --
 import Products.CMFCore.PortalContent
 
 define myclass here 
 
 InitializeClass(myclass)
 Products.CMFCore.PortalContent.PortalContent = myclass
 --
 
 ok this works but there is another tricky thing now ...
 
 I need to patch two products: CMFCore and CMFDefault.
 
 first i patch CMFCore and I think this works (at least a portalfolder
 is a customizerfolder :)
 
 I have now 2 new Classes PortalFolder and PortalContent ..
 
 but 
 
 the CMFDefault.Document for example is still subclassed from
 CMFCore.PortalContent (the default) and therefore doesn't behave
 like a dataskin ..
 
 any ideas ?
 
 is the order in wich the modules are loaded known or changeable ??
 
 if this doesn't work .. I need to release the patches as diffs or tarballs
 replacing CMFDefault and Core .. not as nice as just patching them ..
 
 thanks
 
 Ulrich Eck
 
 
 ___
 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 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] experiments bugs with data.fs 2GB

2001-07-03 Thread marc lindahl



 From: Chris McDonough [EMAIL PROTECTED]
 
 1.  Trying the same thing with 2.4.0b2 and reporting the results

Yikes... I need CMF!  So far it's not recommended with 2.4!
Are there plans to fix this in the 2.3 branch?


___
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] experiments bugs with data.fs 2GB

2001-07-02 Thread marc lindahl

I've recently been testing a new setup with XFS
(http://oss.sgi.com/projects/xfs/1.0_release.html) and decided to try to
bloat data.fs before using this system for production.  The computer is set
up with zope 2.3.3 installed from source (the old fashioned way, with
everything in one directory), with a separate 18GB disk as /usr/local/zope.

I uploaded a couple of files -- seawolf disk one ISO image (about 650MB) and
SGI's XFS install ISO (about 300MB).  Both from another computer via ZMI via
a 10 baseT network.  (interestingly both loaded up OK, but the seawolf image
gave a client side 'page failed to load' error, while the other worked fine.
So I suppose 600MB is the hairy edge of filesize you can upload via ZMI)

Then proceeded to copy the two files and paste.  First time worked fine,
pushing data.fs to about 1.9GB.  Second time, I copied all 4, which should
push data.fs to about 4GB.  It seemed to reach about 2.29GB (perhaps copying
the first XFS ISO image), then gave this error:

--
   Zope Error

   Zope has encountered an error while publishing this resource.

   Error Type: OverflowError
   Error Value: long int too long to convert



   Troubleshooting Suggestions

 The URL may be incorrect.
 The parameters passed to this resource may be
incorrect. 
 A resource that this resource relies on may be
encountering an error.

   For more detailed information about the error, please refer
to the HTML source for this page.

   If the error persists please contact the site maintainer.
Thank you for your patience.




Traceback (innermost last):
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
223, in publish_module
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
187, in publish
  File /usr/local/zope/Zope-2.3.3/lib/python/Zope/__init__.py, line 221, in
zpublisher_exception_hook
(Object: Traversable)
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
171, in publish
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/mapply.py, line 160,
in mapply
(Object: manage_pasteObjects)
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
112, in call_object
(Object: manage_pasteObjects)
  File /usr/local/zope/Zope-2.3.3/lib/python/OFS/CopySupport.py, line 229,
in manage_pasteObjects
(Object: Traversable)
  File /usr/local/zope/Zope-2.3.3/lib/python/OFS/CopySupport.py, line 469,
in _getCopy
(Object: copy_of_RH7.1-SGI-XFS-1.0.iso)
  File /usr/local/zope/Zope-2.3.3/lib/python/ZODB/ExportImport.py, line 218,
in importFile
  File /usr/local/zope/Zope-2.3.3/lib/python/ZODB/FileStorage.py, line 745,
in tpc_vote
(Object: /usr/local/zope/Zope-2.3.3/var/Data.fs)
OverflowError: (see above)

--

Lines 744 and 745 are:

pos=self._pos
file.seek(pos)

it looks like file.seek doesn't like the long int?

Also, when going to the UNDO tab get this error:

---

   Zope Error

   Zope has encountered an error while publishing this resource.

   Error Type: OverflowError
   Error Value: long int too long to convert



   Troubleshooting Suggestions

 The URL may be incorrect.
 The parameters passed to this resource may be
incorrect. 
 A resource that this resource relies on may be
encountering an error.

   For more detailed information about the error, please refer
to the HTML source for this page.

   If the error persists please contact the site maintainer.
Thank you for your patience.




Traceback (innermost last):
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
223, in publish_module
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
187, in publish
  File /usr/local/zope/Zope-2.3.3/lib/python/Zope/__init__.py, line 221, in
zpublisher_exception_hook
(Object: Traversable)
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
171, in publish
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/mapply.py, line 160,
in mapply
(Object: manage_UndoForm)
  File /usr/local/zope/Zope-2.3.3/lib/python/ZPublisher/Publish.py, line
112, in call_object
(Object: manage_UndoForm)
  File /usr/local/zope/Zope-2.3.3/lib/python/Shared/DC/Scripts/Bindings.py,
line 324, in __call__
(Object: manage_UndoForm)
  File /usr/local/zope/Zope-2.3.3/lib/python/Shared/DC/Scripts/Bindings.py,
line 354, in _bindAndExec
(Object: manage_UndoForm)
  File /usr/local/zope/Zope-2.3.3/lib/python/App/special_dtml.py, line 236,
in _exec
(Object: manage_UndoForm)
  File /usr/local/zope/Zope-2.3.3/lib/python/App/Undo.py, line 164, in
undoable_transactions
(Object: Traversable)
  File 

Re: [Zope-dev] Speed up the learning curve

2001-06-28 Thread marc lindahl

I highly recommend the Quick Python Book if you're already a programmer,
looking to learn the new language.

 From: Shane Hathaway [EMAIL PROTECTED]
 
 When I came to Zope, within a week I was getting ready to write a Python
 product.  (And I didn't even know Python yet! :-) )


___
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] ANNOUNCE: Zope 2.4.0 alpha 1 released

2001-06-01 Thread marc lindahl


 Does anyone have any comments on the reliability of PartitionedFileStorage
 in this regard as a temporary solution?  Is anyone using
 PartitionedFileStorage in a production environment?
 
 AFAIK no.  Its functionality has already been superceded.

by?



___
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] What would *you* like to have in PropertyManagerand friends?

2001-05-28 Thread marc lindahl



 From: Chris Withers [EMAIL PROTECTED]
 
 ...and how about a list-of-objects type too?

If you had a 'objects' type, could that object be a list (of, say, objects)?


___
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] OS X support

2001-05-10 Thread marc lindahl

There's a howto on that, I recall seeing.

 Hi,
 
 Is there any plans for zope to support OS X?
 


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