Namespace awl

This class doesn't really provide a huge amount of utility between construct and render, but there must be good things possible there. Perhaps one EntryField is created and used repeatedly as a template (e.g.). That might be useful to support... Why is this a Class anyway? Maybe we should have just done half a dozen functions (one per major field type) and just used those... Maybe we should build a base class for this and extend it to make EntryField in a better way.

Member Editor::Initialise ( $values)

It might be nice to construct a form ID

Our old approach will not work for translation. We need to have a hidden field containing the submittype. Probably we should add placeholders like ##form##, ##script## etc. which the editor can use for internal purposes.

Member Session::Login ( $username, $password, $authenticated=false)

In here we will need to put code to call the auth plugin, in order to ensure the 'usr' table has current valid data. At this stage we are just thinking it through... like ...

Member vProperty::TestFilter ( $filters, $matchAll=true)

: While this is unimplemented here at present, most time-range tests should occur at the SQL level.

Member vProperty::TestParamFilter ( $filters, $parameter_value)

: While this is unimplemented here at present, most time-range tests should occur at the SQL level.