On Wed, 20 May 2009 17:38:41 -0400, Michael DeHaan <mdehaan(a)redhat.com>
wrote:
I have the list pages and edit pages /mostly/ working from a common
field definition now.
We've rearranged the Django structure a lot to make it conform better,
so we can use (among other things) custom Django template tags.
Fields like interfaces are all rendered out, and drop downs are
populated... the next step is to make the interface editor widgets,
which were a little complex, once more work for browing
interfaces and editing/creating new ones in (browser) memory.
After that we can look at reworking the save code and most things will
once again be functional.
There are probably a lot of cosmetic things to be done, plus just
checking to make sure we restore feature parity with what we originally
had -- that will take some time.
Though the Django templates are looking crazy nice and simple -- this
should be very good for people adding new fields and should (long term)
get us out of the business of doing much (hard)
work on the web app.
Huge thanks to Dan Radez for helping me out today with the django
pathing migrations and getting the custom template tags working.
Went through the code and cleaned up a few things, pushed to github:
commit 9c14eaa2579f827263e5e6adb2df9ecb2e696226
Author: James Cammarata <jimi(a)sngx.net>
Date: Wed May 20 19:43:36 2009 -0500
Django cleanup, fixing a few broken pages
* added choices field to fields list in network objects
* corrected a missing arch list in repos (may need to be trimmed
down/fixed)
* re-enabled correct apache auth handling
* fixed broken system edit caused by null-object
Not sure if you want the auth handler fixed, it looks like you broke it for
testing purposes, but I fixed it anyway :)
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.