>Good point. I suppose it could be BXMLCommand? Yes, this could be a better name :-) ...
>>>This proposal also opens the possibility of >>>internationalizing/translating bean class and property/styles names >>>via simple alias classes. Styles can be exposed as bean properties to >>>simplify things even further as demonstrated below. >> On this I have no idea, could be powerful but I don't know if could >> generate >> code too much "strange" to read, for example on anyone has to give >> support >> ... but probably with a real (minimal) example could be easily >> understood. > >Yes, it could certainly lead to some weird BXML files that are written >in multiple 'human languages', but right now it is possible to use >BXMLSerializer to create graphs of objects that have 'non-English' >class names. Ok, for me you can try and see what happens ... but for what I can suggest, in international projects usually a good practice is to have English names everywhere, otherwise maintenance will become a nightmare. On the inclusion or not in Pivot I don't know, we have to see what others say. But in any case you'd have to publish in another place, please consider one of our apache-extras projects ... so a custom class could be a good idea, at least now. Bye -- View this message in context: http://apache-pivot-developers.417237.n3.nabble.com/Idea-for-a-useful-change-to-BXMLSerializer-tp3133361p3137431.html Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
