Den 08.07.2011 18:34, skrev Greg Brown:
I would just use my custom version of BXMLSerializer to process all
BXML files whether they are official '.bxml' files or '.ebxml'
If the BXML file doesn't contain any 'Transformable' objects, then it
will behave in exactly the same way as the official BXMLSerializer.
I think this kind of forking could be a healthy way to add "exotic" features
that might skew the perception of that the Serializer interface encapsulates.
Not sure what perception you are referring to. Can you clarify?
IMO forking in any capacity is not "healthy". It only serves to fragment the
code and community.
"that the Serializer interface encapsulates." -> "what the Serializer
interface encapsulates."
As you stated earlier, the Serializer is not supposed to perform
transformations and such, just create object instances based on the
source. Chris's suggestions might go beyond what the Serializer contract
describes.
> Prototyping - yes. Forking - no.
I absolutely agree, but if Chris forks or otherwise adds this
functionality to enhance "BXML to object creation", maybe his
experiences could benefit BXMLSerializer or Pivot outside of
BXMLSerializer in some way further down the road.
-- Edvin
