[FLOW3-general] Packages - best way to use them

["Christian Müller (Kitsunet)"]

Yes totally depends on the structure. If some part could be used alone 
make a separate package otherwise if some components rely on each other 
heavily better make a package with subpackages to split domains.

Christian
TYPO3 v5 Core team

On 28.03.2011 11:56, Michael Sauter wrote:
> Hi,
>
> I'd say it depends ... IMO if a part of your app makes sense without
> your whole app, then make it its own package.
> If not, structure your app in subpackages (much like the FLOW3 package) ...
>
> ~mic
>
>
>
> On 28.03.11 10:09, Regine Rosewich wrote:
>> Hi Dawid,
>>
>> I have the same opinion and do already work in this direction. As far
>> as I
>> can see from the "packaging" concept of FLOW3 (e. g. the
>> Party-Package, the
>> TYPO3CR Package or the ExtJS Package), the possibilities to work with
>> namespaces and Dependency-Injection offers a lot of freedom to split up a
>> huge application into logical Parts which make it easier to understand
>> the
>> main concept of the application. The only thing I always would try to
>> keep
>> consistent is the DDD approach with the underlying folder structure.
>>
>> Regine
>>
>> -----Ursprüngliche Nachricht-----
>> Von: flow3-general-bounces at lists.typo3.org
>> [mailto:flow3-general-bounces at lists.typo3.org] Im Auftrag von Dawid
>> Pacholczyk
>> Gesendet: Montag, 28. März 2011 10:45
>> An: flow3-general at lists.typo3.org
>> Betreff: [FLOW3-general] Packages - best way to use them
>>
>> Hi all,
>> I have a little argue with someone about packages in FLOW3.
>>
>> In someones opinion the packages should be used like this: 1 application
>> -> 1 package. So you have in it every model, controller, repository,
>> other class that your app could use.
>>
>> My opinion is much diffrent. I think it should be used like group of
>> tool so 1 app can be build from many packages. For example when you have
>> a big portal I would build System package that is controlling some FE
>> proccess and dispatching special assigment to other packages. I would
>> also have Profiles package where I would put users, user groups,
>> priviliges etc. (i thinks its a bit like in JAVA. Packages are grouped
>> by role, tools are grouped in packages)
>>
>> What do you think ?
>>
>> best regards,
>> Dawid Pacholczyk
>> _______________________________________________
>> FLOW3-general mailing list
>> FLOW3-general at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
>>
>>
>