Reinoud van Leeuwen wrote:
On Tue, Feb 14, 2006 at 09:15:42PM +0100, Florian Lindner wrote:
I also think that pure Latex would be the best choice. It's convertible into a
lot different formats and can be edited just using a simple text editor.
Isn't Docbook a better choice? Is is specially des
Peter Bengtsson wrote:
self.queue seem is empty each time I restart Zope.
That's because dictionaries are not derived from Persistent. Try PersistentDict.
D'oh! That's confusing. Isn't there a class that gathers all of these in one.
Urm, Peter, the rules of persistence w.r.t. mutable objects
Peter Bengtsson wrote:
That's very interesting. If you understood Squid better do you think
you'd leave out apache?
Maybe, I guess I just have a soft spot for Apache though ;-)
And what about the performance overhead? Any experience you can share?
Nope, Plone gives me all the performance o
On Wednesday 15 February 2006 03:38, Chris Withers wrote:
> I find it ironic the one of the first uses of PCs was to do word
> processing, and yet we seem to always strive to edit plain text of one
> variety or another, and yes, that includes latex ;-)
That's because Word Processors just do not ha
-- Forwarded message --
From: Peter Bengtsson <[EMAIL PROTECTED]>
To: Jeff Shell <[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 13:14:58 +
Subject: Re: [Zope3-Users] What attributes are made persistent
On 2/15/06, Jeff Shell <[EMAIL PROTECTED]> wrote:
> On 2/14/06, Peter Bengtsson <
Hi,
I wrote a schema like this to have a list of objects on a content object:
class IMyContent(Interface):
mynumbers=List(
title=_(u"Cool Numbers"),
required=True,
value_type=Int(
title=_("integer")
)
default=[1,2,3,5,7]
)
myline=TextLine(
On Wednesday 15 February 2006 08:21, Peter Bengtsson wrote:
> class PersistentAnything(PersistentMapping, PersistentList,
> PersistentDict):
AA! This is so wrong! It merges two incompatible APIs: collections and
mappings. The non-persistent equivalent to this is:
>>> class DoEverything(set
On 2/15/06, Stephan Richter <[EMAIL PROTECTED]> wrote:
> So with that in mind, if you do not know how to do professional desktop
> publishing, then LaTeX is a much better options, since it results look really
> professional.
We also have lots of cool support for Python documentation in LaTeX,
whic
On Wed, Feb 15, 2006 at 01:21:14PM +, Peter Bengtsson wrote:
> I understand the mutation stuff and I always do it like this in zope2
> (I'm a complete beginner in the zope3 world eager to learn):
>
> def updatesometing(self):
>#self.numbers['Peter'] = "0779 123 456"
>numbers = self.num
Reinoud van Leeuwen wrote:
>>I also think that pure Latex would be the best choice. It's convertible into
>>a
>>lot different formats and can be edited just using a simple text editor.
>
> Isn't Docbook a better choice? Is is specially designed for documents like
> this, and easily parsable. lo
Fred Drake wrote:
>>So with that in mind, if you do not know how to do professional desktop
>>publishing, then LaTeX is a much better options, since it results look really
>>professional.
>
> We also have lots of cool support for Python documentation in LaTeX,
> which makes it really easy to work
On 2/15/06, Paul Winkler <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 15, 2006 at 01:21:14PM +, Peter Bengtsson wrote:
> > I understand the mutation stuff and I always do it like this in zope2
> > (I'm a complete beginner in the zope3 world eager to learn):
> >
> > def updatesometing(self):
> >
Am Mittwoch, 15. Februar 2006 14:40 schrieb Frank Burkhardt:
> Hi,
>
> I wrote a schema like this to have a list of objects on a content object:
>
> class IMyContent(Interface):
> mynumbers=List(
>title=_(u"Cool Numbers"),
>required=True,
>value_type=Int(
>
On 2/15/06, Peter Bengtsson <[EMAIL PROTECTED]> wrote:
> D'oh! That's confusing. Isn't there a class that gathers all of these in one.
All of who?
> It seems confusing, you derive from Persistent but only some are accepted.
> Does that mean that there's PersistentFloat and PersistentTuple too?
B
Well, one could have a base class along the lines of
class PersistSetItemOnAttributes:
def __setattr__( self, attr, val ):
oldSI = val.__class__.__dict__.get( '__setitem__', None )
if oldSI is not None:
def newSI( vself, vattr, vval ):
vself._p_chan
Frank,
I'm not sure how widgets manage to get default values; I know that
zope.schema itself doesn't set them.
There is further problem with the design for "default" -- see discussion
of "default_factory" on zope3-dev: basically, even if the widget were to
get this default, it would be *the* list
On 2/15/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
> I've never tried using OpenOffice and I'm not sure whether
> its changes would actually leave existing whitespace intact (this would
> be crucial for decent diffs).
I've worked a bit with generating OpenDocument documents for use w
Igor Stroh wrote:
> Reinoud van Leeuwen wrote:
>
>>On Tue, Feb 14, 2006 at 09:15:42PM +0100, Florian Lindner wrote:
>>
>>
>>>I also think that pure Latex would be the best choice. It's convertible into
>>>a
>>>lot different formats and can be edited just using a simple text editor.
>>
>>
>>Isn't
Swiss Easter Sprint
"Sorry for cross posting, I just will make sure that
nobody feels like not invited and has a chance to
participate."
When
The sprint starts on Saturday, April 8, at 9:00am and will end
on Wednesday, April 12 in the afternoon. The official welcome
activity will be at noon
Hi All,
I am pretty much an observer who has been to a sprint but just can't
find the time in the commercial world to contribute to the code base but
one who really believes in Zope 3 and have been using Zope 2 since its
inception and convincing people that its a worthwhile framework while
of
One could, but it's really not worth it. It's just the laws of Python
and mutability and immutability :). (It took me years to understand
those terms. I kept associating them with 'mutable' in the "can be
made quiet" sense... Eventually my music brain stepped back and I went
"oh, MUTATE! Ahhh!". Se
21 matches
Mail list logo
