[TYPO3-ect] ajax and class per controller model

[Elmar Hinz]

Hi,

Am Tue, 26 Jun 2007 16:07:32 +0200 schrieb Christian Welzel:

> hi there!
> 
> currently i'm trying to integrate some ajax stuff into the kickstarter__mvc
> to make the it easier for new exts to use that technology.

ajax in kickstarter__mvc. Wow. Hope that isn't to oversized for the users.
Hower, it could become a bestseller. 

> for the "method per action" model i found a clever solution to get this
> done (at least i think so :)), but for the other model where each action
> is an own class i have to clever idea, how to make this.

Do we have this? Guess you think of one of the following cases:

All 4 cases have one method per action. Actions call action methods. That's
fundamentel.


1.) Standard (example banans):

 * One controller class per plugin. 


2.) Switched (example efaq):

(Like standard, but with flexform controlled subplugins below one plugin.)

 * One controller class per subplugin.


3.) Shared:

(This is not recommended, but can save time, if you deal with
multiple "passiv" plugins - plugins without real actions.)

 * Multiple plugins, one controller class.
 * No real action functionality.
 * Setup abuse of the actions to mark and distinguish the plugins.


4.) Switched-Shared (example efaq 0.0.3):

(3. and 4. combined. Not recommended, see 3.)

 * One switch, one controller, multiple subplugins.
 * No real action functionality.

Have a nice evening.

Elmar





















> 
> i would like to use the same contruct which is used for normal processing
> (lib_switch), but the switch is not configurable through get/post parameters
> and totally relies on flexforms.
> 
> so my question: i there another clever way to enable ajax or do we need
> to modify tx_lib_switch::main() ?
> 
> PS: the new code can always be found in svn.
>