Michiel Meeuwissen wrote:
Kees Jongenburger wrote:
Kees Jongenburger wrote:
How will default values be handeld on a not commited node?
Where will validation of node values take place?
Any changes that EditState made only worked if you used the SCAN
editors. I guess it is for those who use it to make out where to move
that code.
The "old" scan editors supported default values. the new jsp editors
don't. so we are loosing some functionality I don't know if that
worked because of editstate or geDefaultValue...
Are you sure that they did? Or did they only fill in the blanks after a
commit? That should also work in jsp-editors with 'setDefaults'.
It is not very useful for an editor; you want to know the default value before
having a node object. I suppose we will add:
Object default =
cloud.getNodeManager(<nmname>).getField(<fieldname>).getDefaultValue();
in field-types. Then you can make actual default-values in your editor. (As
soon as the above method is available, it is a piece of cake, actually).
It seems rather straight-forward, I have good hopes that this will be
implemented before the release of 1.8.
This is already part of the field-types project isn't it?
Gerard
