Howdy,
In the past week I've created a new OpenLayers mapping widget for use in
Django, which works both inside and outside the admin site. It
simplifies the process of creating open layers maps for geodjango data,
and also adds some features that the current admin lacks (such as
editing geometr
On Fri, 2009-04-17 at 07:01 -0700, JL wrote:
> Just to through in my 2c (since I'm acutally in the US). I'd second
> South as being the most complete and flexible migration project.
Have you written up your comparison of South with the other major
options anywhere that we can need? Perhaps doing
On Fri, 2009-04-17 at 03:19 -0700, Richard Davies wrote:
> Ticket 399 has various patches.
>
> Not clear to me why none of these have been merged for 1.1 yet?
Because it's not on the 1.1 roadmap and the time for feature additions
is long past.
Regards,
Malcolm
--~--~-~--~~---
Hi all,
For Google's Summer of Code last year, I worked on djangosearch
(http://code.google.com/p/djangosearch/
) with the aim of extending it with more backends. It soon became
clear that the full text support in Django's database backends was
sufficient for most small sites. Considering t
I totally agree that returning an object is the way to go. I know a lot of
other folks are busy getting the next release out, but after that, I am happy
to submit a proposed patch. I think it should be straightforward to preserve
the current api while still adding new functionality.
On Apr
You can take this idea further by not providing the name but the
resolver object. This gives you much more flexibility. It might be
helpful to have it in the result of the reverse dict.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
