> Well, personally I'm not too happy with the direction BXMLSerializer is > taking things... from UI-centric to UI-agnostic.
I think you may have missed the point. WTKX was never UI-centric, except in name. There was nothing specific to the org.apache.pivot.wtk package in there. Moving it to org.apache.pivot.beans required no refactoring other than changing the name. XAML works the same way - it isn't tied to WPF. On the other hand, MXML is tied to the mx namespace, which I think is a limitation. It makes the markup language more complex and more difficult to maintain, because it allows for "special cases". We try to stay away from special-case code in Pivot. Moving BXML support to the core package allows it to be used in other contexts. For example, I may want to use it on the server (or in some other headless context, such as a background thread). You may not have a currently use case for that, but other developers may.
