Re: Django client

Hallöchen!

Bruce D'Arcus writes:

> [...]
>
> So what, then, are relevant class models you are thinking of?

The low-level Python module will implement the classes Reference and
ReferenceList.  Reference itself contains the classes Part,
Publication, Set, PubInfo, LibInfo, and Author.  The other elements
and attributes of RISX are realised through class attributes.

> Might there be a way to design them in such a way that someone
> could later use a Django-native model instead (for those that
> don't want to install RefDB)?

No.  I cannot -- and don't want to -- re-engineer the 1,000,000 LOC
of RefDB.  On the contrary, the current plan is to have no database
models in the Django app at all.

> BTW, awhile back I started working on a collection of little Django
> apps to manage my own academic content. The "document" app model code
> is here:
>
> <http://github.com/bdarcus/django-scholar/blob/7c06b6b2fd8cda77299e25406d6dc163a8e6ec71/documents/models.py>
>
> I went with a much lighter-weight alternative though, so gave up working on it.
>
> <http://github.com/bdarcus/mysite/tree/master>

Nice, but this looks very different, more like a scholar version of
a Personal Information Manager.  ;)

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: [email protected]


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H