Then I think the default must be a global config value.
Sometimes it's necessary to break some compatibility, the current
behaviour is wrong, as it show for editing a different value from
database field. To make the changes small, we can put default as Escape, and create a
single config option to change default to do not escape.
The new projects will be correct, and old projects can run correctly with only a single change in config. Which can be documented in the release docs.
When showing data we check the new escapeHTML attribute :
true
escape all false
escape only quotes
After we decide the best option to be implemented, if you point me the best places to make this changes, I can change my patch and submit again.
I don't think that an attribute is necessary, as this trasformation is mandatory, and doesn't break any compatibility (ASAP). I think that we have only to find the best way to achieve this (i.e. execute the trasform only on filling value's attribute of inputs tag).
regards, sergio
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
