[Neos] TYPO3.Boilerplate and FluidBuilder naming (domain stuff)

[Rens Admiraal]

Hey Jacob,

 From the PackageBuilder team perspective and stuff we are aiming for 
there (having a generic UI code named Ice for now) I can only say that 
I've a warm welcome for a generic approach. I do feel like a bit too 
much time is being spend on finding the right naming though ;) It's 
fairly easy to refactor the name afterwards.

So my advice would be to stick to the FluidBuilder something approach, 
and rename it when it matures and connection to the other builders is 
found. I would LOVE to join your effort partly and spend my 
PackageBuilder time in close relation to your project, but keep it 
simple for now ;-)

Not meant for nagging, but hope this reply prevents you from loosing 
time / momentum ;-)

Greetz,
Rens


Op 5/29/13 18:58 , Jacob Floyd schreef:
> Quote: Jacob Floyd (techgurufloyd) wrote on Wed, 29 May 2013 17:44
> ----------------------------------------------------
>> Yah. This is how Kickstarter and Builder are used.
>> Builders will depend on TYPO3.Boilerplate, but Boilerplate packages
>> will depend on the Builders, not on TYPO3.Boilerplate. So, we need a
>> new name for TYPO3.Boilerplate that suggests that Boilerplate is more
>> closely related to Builders than to Boilerplate packages.
>> TYPO3.BuilderBase
>> TYPO3.BaseBuilder
>> TYPO3.BuilderFramework
>> TYPO3.Builder???
>
> What about:
> TYPO3.AbstractBuilder
>
> All of the Builders will essentially be extending this builder similar
> to how Classes can extend AbstractClasses...