Gary Poster schrieb:
> OK. I'll give it a whirl sometime over the next couple of weeks, if
> that's soon enough for you.
Sure.
> FWIW, I'd be strongly tempted to release *without* the generation
> code, and leave it up to users to switch as they desire.
Fine with me. I'm pretty confident
On Dec 23, 2008, at 2:11 PM, Thomas Lotze wrote:
> Thomas Lotze schrieb:
>
>> Yes, and I think that we're talking about two steps here anyway. I'd
>> like to finish and release a version that uses BLists ASAP;
>
> Well, I think the switch to BLists is finished, so I'd be ready to
> merge it to t
Thomas Lotze schrieb:
> Yes, and I think that we're talking about two steps here anyway. I'd
> like to finish and release a version that uses BLists ASAP;
Well, I think the switch to BLists is finished, so I'd be ready to
merge it to the trunk after someone reviewed the changes. In
particular, I
Gary Poster schrieb:
> Hi Thomas. Very cool that you are working on zc.dict + zc.blist.
Better than letting that branch get old ;o)
> The updateOrder API is a sucky API for blists, as I'm sure you've
> realized. :-)
It is sucky even when used with a PersistentList; it's just that the
disadv
Hi Thomas. Very cool that you are working on zc.dict + zc.blist.
The updateOrder API is a sucky API for blists, as I'm sure you've
realized. :-)
FWIW, I seem to recall that Plone has a reasonable-to-nice API for
changing order in containers, and the API would be able to take much
better ad
