I'm using django profile v0.6 for my social network (w0manpower.com).
And I've recently switched to google map api v3 for performance enhancement.
Here is a non-exhaustive list of advantages I've observed using it:
- much lighter (therefore it's also faster)
- it's "clever" (loading dynamically additional/external JS if needed)
- mobile device friendly
- YSlow/Page-Speed friendly (e.g. bit more caching friendly)
- google map api key free (not anymore required)
The only inconvenient I've found so far are some backwards incompatibilities.
Few "inline" helper methods were removed from some objects but that's the price
to get it lighter.
I've only migrated my front page view so far as it's the most used one and I'm
very happy with what I have.
I'll migrate all the other views (including default Django profile ones) when I
get a chance and I can give away a patch once I've done.
Original issue reported on code.google.com by andre.mi...@gmail.com on 9 Jun 2010 at 1:56
Original issue reported on code.google.com by
andre.mi...@gmail.com
on 9 Jun 2010 at 1:56