[TYPO3-project-formidable] majix: <datahandler:LISTER> = error

[Asbjørn Morell]

Hello,

Thanks for clearing things up. Much stuff I did not know :) That "chapter" 
should definitely be included in the next version of the manual! I have 
created a SERVER EVENT as you explained. Is it correct that a <userobj> will 
fire the next time the form object is initialized? What I would like to do 
is set a variable before the main plugin starts to initialize. User clicks 
edit - my <userobj> set $this->_oParent->action = "artEdit"; I then have a 
switch in my main plugin that decides what to do. (list, artEdit, artDelete, 
imageEdit, imageDelete etc.)  But what happens is that the switch jumps to 
the default action. I did some debugging, and the action variable won't be 
set before the form is initialized again :/ which is to late.Could this be 
done with the params attirbute? params="uid, action = artEdit"


More information:
This is what I am trying to do:
form A is a list (edit, delete)
form B is an input form.
form C is a singleView list of a single record

How would you structure this? Each form should have its own page! Only 1 
form should be showed at a time.



Best regards.
Asbjørn Morell.




"Jerome Schneider" <j.schneider at ameos.com> wrote in message 
news:mailman.1.1180367035.17361.typo3-project-formidable at lists.netfielders.de...
> SERVER EVENT: ----------------------------------------------------
> You provide a php-userobj to tell Formidable what to do when button 
> clicked. The PHP is not executed when page is generated. Formidable will 
> rather notice that a server event is declared, and will automatically 
> attach a tiny piece of JS code (that is, the server-event header) on the 
> onclick event for the button. When  the button is clicked, this JS is 
> executed, placing data in the POST telling formidable that the 
> onclick-event of the button has been fired, and then making the page 
> refresh. When PHP receives the POST of the just submitted page, it notices 
> that this server event has been thrown, and will then execute the attached 
> PHP do what you wanted it to do on button click.
>
> Logical scheme:
>
> 1 - Formidable reads XML configuration for the button
> 2 - F. generates a server-event header ( tiny piece of JS ) and places it 
> on our button's onclick event
> 3 - When clicked, parameters are fetched (if any declared), page refreshes 
> and F. executes the PHP code attached to the event fired (determined by 
> the sent server-event header)