Re: Offline Django Apps

Cool.  What's the best way to coordinate the effort?  A wiki
page to
start with?

Coming up in the next month or so I'm going to have to
dedicate work
time to this but for now I'd like to just lay out the
groundwork and
do it in such a way that it benefits the Django community.

1) Cross Platform Libraries...

In looking at DjangoKit a little I see he's using PyObjC.  I
do like
the idea of using whatever the native widget library is for
each
platform.  I'll have to look at the Democracy Player as an
example but
they did something similar (Mac: PyObjC, Linux: PyGTK,
Windows: ???).

2) Database...

It makes sense to me to require SQLite for this to work. 
Moving your
data to SQLite is also a requirement for Slingshot.  I'm
pretty sure
we can use the fixtures library to serialize data from
databases other
than SQLite (MySQL, PostGreSQL), then load it up into
SQLite.

3) Anything else?

Thanks,
Rob


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Rob Hudson wrote:
> Cool.  What's the best way to coordinate the effort?  A
wiki page to
> start with?
>   
Current trends seem to be to use Google Code for projects
that aren't 
likely to become part of the core django distro. A link from
the Django 
wiki is probably a good idea though.
> 1) Cross Platform Libraries...
>
> In looking at DjangoKit a little I see he's using
PyObjC.  I do like
> the idea of using whatever the native widget library is
for each
> platform.  I'll have to look at the Democracy Player as
an example but
> they did something similar (Mac: PyObjC, Linux: PyGTK,
Windows: ???).
>   
wxWidgets is one cross-platform option. PyGTK runs on
windows too.
> 2) Database...
>
> It makes sense to me to require SQLite for this to
work.  Moving your
> data to SQLite is also a requirement for Slingshot. 
I'm pretty sure
> we can use the fixtures library to serialize data from
databases other
> than SQLite (MySQL, PostGreSQL), then load it up into
SQLite.
>   
Yeah, that's perfectly reasonable IMHO.

Rob 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 22, 11:47 pm, Rob Hudson <treborhud...gmail.com> wrote:
>
> 1) Cross Platform Libraries...
>
> In looking atDjangoKita little I see he's using PyObjC.
 I do like
> the idea of using whatever the native widget library is
for each
> platform.  I'll have to look at the Democracy Player as
an example but
> they did something similar (Mac: PyObjC, Linux: PyGTK,
Windows: ???).

DjangoKit is a native-widgets project, and will probably
stay that
way. I very much like the idea of Windows and linux-specific
native-
widget projects to complement it. The core of the thing was
very easy
to write - the hardest part was getting the packaging system
to
behave, so there probably won't be a lot of effort
duplicated between
the platforms here.

> 2) Database...
>
> It makes sense to me to require SQLite for this to
work.  Moving your
> data to SQLite is also a requirement for Slingshot. 
I'm pretty sure
> we can use the fixtures library to serialize data from
databases other
> than SQLite (MySQL, PostGreSQL), then load it up into
SQLite.

This, on the other hand, _can_ be shared nicely. And has
nothing to do
with a GUI wrapper. A framework that will do 2-way sync
between 2
django applications / databases can be worked on in the
absence of
working wrappers.

> 3) Anything else?

(a) One thing I've been finding is that many django apps
I've found
aren't really written as apps, but tend to be tied very
heavily to the
project they're developed in. I've only just joined
django-users, so
maybe this is covered a lot. But because djangokit provides
it's own
project and expects the thing you're packaging to be a
stand-alone
app, it's hard to find nice demos.

(b We're going to find lots and lots of different deployed
versions of
the app's DB schema in the wild, so upgrades will be nasty.
With
proper 2-way sync, you could just tell the remote user to
sync, blow
away their DB, then re-sync, but if you're trying to write a
simple
stand-alone app, you'll need upgrade scripts.

tom


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 23, 2:51 am, Robert Coup <robert.c...onetrackmind.co.nz>
wrote:
> Rob Hudson wrote:
> > Cool.  What's the best way to coordinate the
effort?  A wiki page to
> > start with?
>
> Current trends seem to be to use Google Code for
projects that aren't
> likely to become part of the core django distro. A link
from the Django
> wiki is probably a good idea though.

I've created a google code project - http://code.googl
e.com/p/djangokit/
- anyone who cares is welcome to membership.

tom


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 31, 1:20 am, "Vagmi Mudumbai"
<vagmi.mudum...gmail.com> wrote:
> Check out Google Gears.http://gears.google.com

There's a lot of interesting things about Google Gears...

It provides a browser local SQLite accessible via
Javascript.

It provides a local HTTP server for storing/retrieving
cached content.

Simon Willison dug up some interesting Google Gears
tidbits:
http://sim
onwillison.net/tags/googlegears/
including:
Adobe's Apollo will use Google Gears technology, Dojo was in
on the
Google Gears collaboration uses it.

Looks like a lot is happening in the world of offline web
applications.

Great stuff.

-Rob


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---