On 14/03/2012 02:03, Marvin Humphrey wrote:
Everything that is used to model the class hierarchy moves under "Clownfish::CFC::Model":
+1
Then, "Clownfish::CFC::Binding::Perl" gets renamed to "Clownfish::CFC::View::Perl" and "Clownfish::CFC::Binding::Core" gets renamed to "Clownfish::CFC::View::Core":
I'd prefer to keep "Binding". "View" is a bit too abstract.
The punchline: To add a new host language to Clownfish, write a new View for CFC. I hope that helps to clarify both how CFC is organized and what it takes to contribute a new host language.
Hmm, the sentence "To add a new host language to Clownfish, write a new Binding for CFC" seems clearer to me.
Nick
