bbaetz at student.usyd.edu.au
Thu Sep 12 12:34:31 UTC 2002
On Thu, 12 Sep 2002, Gervase Markham wrote:
> > Another part of this is the moving of the localconfig enumerations into
> > the database, and giving them descriptions, sortkeys, isactive flags and
> > IDs, also preventing the enumeration deletion problem. This will
> > probably be the second part, and is bug #146104.
> Doesn't moving localconfig to the DB fit in with customised fields?
Well... Having customised fields in will eventually allow us to move some
of the stuff in localconfig into the db. I don't think that this first
round of patches goes that far, though.
> > The administration rewrite is fully templatised and taint mode enabled.
> I am of the view that total templatisation and l10nability should be a
> hard 2.18 target. If admin can be done, I've got the rest under control.
Admin really needs to be done. The code is a mess, and trying to touch it
is impossible. Also, mod_perl doesn't allow us to run some scripts in
taint and some not, so these would have to be left un-mod-perl'd.
> > I believe it isn't "customised fields" but rather "customised
> > enumeration type fields".
> IMO, any decent custom fields patch should be able to support:
> - enumerations (multi and single)
> - text
> - email address
> As far as I can see, these are the three most common requested types.
The first round only does the first two, IIRC.
> > A big issue with this is how they interact with templates. Requiring
> > admins to edit templates when fields are added or removed, is, I think,
> > unacceptable long term. I believe we can make our templates adjust to
> > new fields, given there's a fixed set of field _types_.
> I think this is unlikely to please anyone. I don't think it's
> unreasonable to ask an admin to add the UI for a new field type to e.g.
> the query template, as long as we do _everything_ else (notice it's
> there, do the right thing etc.) Any sort of auto-generated layout is
> bound to suck.
Not really. We do it currently, don't forget. Whether its read in from teh
versioncache, or from the db shouldn't matter.
More information about the developers