[FLOW3-general] Additional fields

[Robert Lemke]

Hi Erik,

yes, it's an architecture question which we're aware of for some time  
already. I've been discussing it again yesterday with Karsten and Andi  
and will probably have a solution for you soonish.

I'll keep you posted,

robert

Am 04.03.2010 um 19:32 schrieb Erik Frister <ef at aijko.de>:

> Anyone have any thoughts on this?
>
> I think this is a general architecture question concerning FLOW3.  
> Maybe someone of the FLOW3 team can help me out on this.
>
> The thing I am trying to do is: I want the application I am building  
> to be highly modular, and FLOW3 seems ideal. So e.g. I want to have  
> a FLOW3 package that maybe helps me to manage projects, tasks and  
> employees. And then any given amount of new FLOW3 packages should be  
> able to extend this package, e.g. add some more properties to the  
> "project" domain (maybe with decorator pattern), add some more menu  
> items to the main navigation, add more form items for when we create  
> new projects and so forth...
>
> Would I even use FLOW3 packages for this? Or would I rather write  
> one big package and implement my own "module" function?
>
> What is the way I would handle this stuff with FLOW3? Where WILL  
> FLOW3 help me and what will FLOW3 never do for me?
>
> Thanks in advance, I hope someone can shed light on this issue.
>
> Erik
> _______________________________________________
> FLOW3-general mailing list
> FLOW3-general at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
>