[TYPO3-mvc] [TYPO3-50-general] (Result) Last minute concept fix? Incosistent class naming for domain models ...

[Robert Lemke]

Hi folks,

thank you for the interesting discussion. During our morning run  
Karsten and I discussed again the different approaches and I think we  
have found a consensus now, based on your suggestions.

I'd like to go for the following conventions now:

\F3
   \Blog
     \Controller
       BlogController
       PostController
       ...
     \Domain
       \Model
         Blog
         Post
         CommentInterface
         AbstractComment
         GoodComment
         Badcomment
         Tag
       \Repository
         BlogRepository
         PostRepository
       \Validator
         BlogValidator
         EverythingFineValidator
       \Service
         BlogPostStyleCheckService
         StupidContentDetectorService
     \View
        TagView
        ...

Another example mainly explaining the namespace structure, leaving out  
most classes;
please don't mind the actual class names, they might change / not  
exist in the real TYPO3:

\F3
   \TYPO3
     \Backend
       \Controller
       \View
     \Frontend
       \Controller
       \View
     \Webservice
       \Controller
         SiteController
         StructureTreeController
         ...
       \View
         \Site
            ListJSON
            ShowJSON
     \Domain
       \Model
         \Content
           ContentInterface
           AbstractContent
           Page
           Text
         Site
         StructureNode
       \Repository
         \Content
           PageRepository
         SiteRepository
         StructureNodeRepository
       \Service
         TimeService
         PublishingWorkflowService

I summed up the changes I'd like to see in FLOW3 1.0.0 alpha 1 already  
in http://typo3.org/go/issue/3507 .
For alpha 1 the important bit is that repositories and validators now  
reside in their own namespace,
separated from the model.

I hope you like the new solution!

Cheers,
robert