[TYPO3-project-formidable] structure in formidable

[Jerome Schneider]

Luc Muller a écrit :
> Hello,
> 
> By my side I would suggest to seperate each "sections" indise on plugin.

+1 here

I would also go for a plugin-based structure, as it has proven to be 
really flexible in my works.
Another advantage is that it would allow lists to be cached by T3 when 
they're not bound to a searchform ( ie, when their content is static ) ; 
I guess that's the case for your "browse" section

Greets from France,
Jerome

PS: do you use a SVN client to get the code, or the SVN builds ?

> 
> I think it would result in less PHP code to select the XML to use in 
> formidable.
> In this way each pi can have mainly the same structure and (almost) 
> everything can be done inside you XML file.
> 
> Using different plugin will allow you to easyli add one new pi, just in 
> adding on more folder to your extension (and naming correctly your files and 
> so on). You won't have to check you php code to insert some new XML.
> 
> If you use a different plugin, you'll be sure that every method inside your 
> pi is going to be used inside the PI, what you can to is to have a main php 
> class that you can include (require) inside each of your plugin, for global 
> methods that are going to be used inside every PI if you need.
> 
> But of course, you can do it inside the same pi as you're suggesting it. in 
> fact the final result is going to be the same.
> 
> Hope this helps!
> 
> Luc
> 
> "Asbjørn Morell" <atmorell at gmail.com> a écrit dans le message de news: 
> mailman.1.1184585210.4839.typo3-project-formidable at lists.netfielders.de...
>> Hello,
>>
>> What would be the best way of structuring a formidable extension. Should I 
>> create a frontend plugin for each of my main menu sections, or create a 
>> single plugin and do the logic in my construct with a GET url?
>>
>> main menu: (example)
>> browse | search | top list | users | new users
>>
>> I am rebuilding my extension with the new list/search concept - so I want 
>> to structure everything as correct as possible.
>>
>> Best regards.
>> Asbjørn. 
> 
>