I've tried planning sprint efforts in the past and my experience tells
me that it's not an overly good idea. There's enough time to define a
project at the actual sprint; but it doesn't hurt to prepare something
for the sprint.
I might be doing some work on resource handling in a joint
plone/vudo/wsgi context and another topic is to continue the layout
package, also in a wider context of putting webpages together (this is
something David Pratt has brought up several times).
\malthe
Regards,
David
We made a demo called ``repoze.demo.gallery``; it's in the repoze svn repo.
malthe
2008/10/10 David Pratt <fairwi...@gmail.com>:
--
--=====================--
mail: mbo...@gmail.com
homepage: zeitmaschine.dk
--=====================--
Right true; we don't have a demo up yet. It's on the drawing board.
I'll post to this list first thing when we have something to show.
This should be quite soon.
\malthe
2008/10/12 David Pratt <fairwi...@gmail.com>:
Okay I'll look into that.
> 2) You may want a try/except around import for Image in
> repoze.bitblt.processor and to try from PIL import Image. I am using
> PILwoTk for example and its happy with the alternate form of import.
> Not sure if there should be a hard dependency on PIL if PILwoTk is
> also a possibility
We sort of decided that if you use repoze.bitblt, then you really must
have PIL. We do ``import PIL`` before ``Image`` in order to show you a
meaningful error message.
> 3) I put a secret in the gallery.ini to get this working. It might be
> helpful if a bit of explanation and example are given in bitblt
> package documentation.
Great, I forgot to update the demo with that.
Thanks for trying this out.