Daniel Poelzleithner wrote:
> If such a Interface is specified, it should be flexible enough to switch
> backends. In my optinion PIL has a total terrible quality when compared
> to ImageMagick.
that's a rather broad statement, don't you think? what are you doing
with PIL, and how are you doin
Adrian Holovaty wrote:
> Some of these ideas sound really cool! I'd suggest focusing on one or
> two of them rather than attempting to do the whole shebang. In my
> opinion, the Python Imaging Library functions as generic views would
> be a really useful thing to have.
If such a Interface is spe
On 11/16/06, binberati <[EMAIL PROTECTED]> wrote:
> This is what came to my mind a second ago (maybe two) after reading
> James Bennett's blog entry 'Django tips: get the most out of generic
> views'[0].
Some of these ideas sound really cool! I'd suggest focusing on one or
two of them rather than
Hello,
This is what came to my mind a second ago (maybe two) after reading
James Bennett's blog entry 'Django tips: get the most out of generic
views'[0].
Wouldn't it be nice to have generic views (REST APIs) for:
- Filesystem operations (on *nix for a start). Loose coupling with
Python's OS mo