Ebase to recognise the fieldname.attribute format

[Hovik]

Posted by a customer on 06/08/2010

I've noticed an inconsistency in the way that field control attributes are set from FPL. If I want to make a field control visible, invisible, display only, mandatory etc I do so with reference to the actual field name itself, e.g.

(un)set MYFIELD displayonly ;

and Ebase automatically applies the instruction to the first instance of that field on the current page (or throws an error if the field does not appear on the current page). However, if I want to set a property such as the editor cell class from FPL, I have to explictly specify the field control name:

set MYFIELDCONTROL.editorCellClass = 'MyClass' ;

Could Ebase be enhanced to recognise the fieldname.attribute format as well as the fieldcontrolname.attribute format, so that we don't have to keep a track of which attributes are handled in which way and can write generic scripts that apply to more than one page without complex workarounds?