> a) Create a new serializer resource naming approach that does not use file > extensions and they are automatically appended when the user specifies a > string for a resource location.
Sounds a bit complicated, and may seem foreign to many developers (myself included). Also may have hidden negative implications. > b) Encourage the use of a serializer interface (to be created). A specific > instance of the serializer is then created. The old serializer just inherits > from the new one for awhile until it is deprecated and removed as you > mentioned. I think this would be over-designing it, since a simple refactor or search/replace will suffice and will allow the user to begin using the new classes immediately. I understand that it is not ideal, but I think that a wholesale migration to BXML is going to work best. As long as we provide a script (or some other utility) to ease the transition, I don't think it is going to have much of an impact on developers.
