DjangoClick

3 views

Skip to first unread message

Rubic

unread,

Feb 27, 2007, 9:25:07 PM2/27/07

to django-hotclub

Allow me to speculate about one possible outcome
of HCoF ...

INTRODUCING: DjangoClick(tm), installed on
your debian system[1] via Synaptic.

On my Ubuntu system, DjangoClick installs in
Applications -> Internet -> DjangoClick. When
I select it, the server automatically starts
running on port 8898[2]. Closing DjangoClick
parks it minimized on my panel, perhaps with
a gratuitous LED blinker showing http activity.

A link/button on the gui screen automatically
launches the browser to http://localhost:8898,
displaying a menu of the installed apps.

Behind the covers, not much has changed with
Django. The first access to the server probably
assigns a user account (defaulting to the current
user) and requests a password, giving the user
admin privileges.

Backing up for a second ... I know this is not in
the original scope of HCoF. But consider DjangoClick
as a reference implementation of a server to
encourage reusable apps. Even after we've got a
workable HCoF convention, it's still going to be
a pain to download, install, edit configuration
files, check permissions, etc. Having something
in place to simply click and install apps (similar
to Firefox extensions) would go a long way toward
encouraging sharing/experimentation without the
installation hassles.

In all seriousness, I don't think we'd be introducing
much in the way of new technology to do this,
aside from a moderately portable front-end.

[1] And Windows, BSD, Mac, Gentoo ...
[2] Port 8898, along with everything else in this post, is purely
arbitrary.