>> I think the idea of separating code and markup is different from separating logic and presentation. The latter (which is common in JSP and HTML) can produce unreadable and unmanageable code. >> However, the former can help create more maintainable code. >> For example, if you create a button and add event listeners to it in >> BXML, the association between the button and the listeners is clearer >> than if you create the listeners in your initialize() method. Yes, I agree
>> OTOH, it is also a good idea to keep event listeners as short as possible >> and have them call into domain objects that are exposed by the >> application (and these would generally be implemented in compiled code >> vs. script). This is the point: this setting could be useful to ensure that in BXML files are put only references to existing (in code) methods and nothing other. Like enforcing a best practice. Sandro -- View this message in context: http://apache-pivot-developers.417237.n3.nabble.com/BXMLSerializer-Flag-to-turn-off-script-parsing-tp1945087p1946271.html Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
