[Flow] Best practice: How to organise packages within a flow application

[Mathis Hoffmann]

Hi Robert,

I'm also thinking about how to find a satisfying subpackage structure 
for my application. I have been thinking in a same direction as you did. 
My question now is, how to manage that technically. If I have two 
Flow-packages, I think it would make sense to define one as a master 
package that provides layout and configuration for all other packages 
that are related to my application. How do I use a master-layout-file 
(layout in terms of a fluid layout file) in different packages?

Another question concerning that topic is how to define a subpackage 
structure in Flow. Would you do it like the following:
Classes/VendorName/PackageName/SubpackageName/
     /Domain
         /Model
         /...
     /Controller
     /...
Resource/Private/Templates/SubpackageName/ControllerName

If I do it like that, do I have to configure anything - for example that 
a subpackage-controller "finds" it's corresponding template files etc?

Thank's in advance for your help!

Yours
Mathis

Am 13.05.2013 15:08, schrieb Robert Lemke:
> Hi Axel,
>
> Qbus | Axel Wüstemann wrote:
>
>> what might be a best practice to organise an application in flow? If I
>> have several application components, each of them might consists of
>> modules and plugins etc.
>>
>> Is it good practise to build each applicaion item as a separate flow
>> package? How I can access central ressources of the application from a
>> component package like layout templates, theme files etc.?
> I would keep the amount of packages to a minimum as each additional
> package generates overhead in terms of additional Git repository, issue
> tracker and so on.
>
> My criteria for extracting functionality into a separate package:
>
>   - is it standalone / decoupled enough so it could be used in a
> different project?
>   - would it simplify the work of another team / developer if it was a
> dedicated package?
>   - is it a plugin which should be possible to install optionally?
>   - is my main package really too bloated so it needs to be split up?
>
> If any of these matches, I'll create a separate package.
>
> Cheers,
> Robert
>