- new editor has now everything the old one had, beside editing of embeded stylesheets
- new possibility to define a confirmation for buttons via javascript
- finetuned the garbadge collection for php4 sessions
- widget editor works quite nice
- beware it can create Templates the old editor cant understand and destroy if you save or export them from the old editor!
=> need to move the other functionality (import, export, dump, ..) of the old editor to the new one, so the old editor can retire ;-)
- based on existing show function the template can be edited in place
- dblclicked widgets will be edited in a popup
- new editor supports not only one grid, but a hirachical tree of widgets
still missing:
- editing and operations of grid rows and columns
- type-specific templates for the popup, to make the options more intuitiv
In the meantime the old editor is still functional
2) Step #1 of removing eTemplate's limitation on allowing only a grid as root element of the widget tree (which can NOT directly contain further grids, thought references to other templates/grids are ok). The storage layer allows now a real tree. Redering and editing only works on the old data variable, which is now a reference to the first grid in the tree.
More to come ...
2) validation only loops now, if a button (not cancle) is pressed, selectboxes with onchange dont get stoped by validation errors ==> fix for bug [ 1001568 ] status is not updated
- knowledgebase is not working: select distinct is not possible with text-columns
- fudforum is not working: is does not use ADOdb and has no own db-layer for mssql
- other apps seem to work, everthing needs through testing - incl. our "old" db's
- needed (= not to be empty) fields are enforced now
- min and max values and format of int and float fields
- validator for text-fields (perl regular expression)
The input-validation is handled completly withing eTemplate, the application dont need to implement any code, just set the right attributes in the template. Validation-errors are displayed in red behind the concerning field, try the template 'etemplate.validation-test' in the editor.
