What are my goals with this: I have an Contao-CMS-based Homepage. There are registered Member (staff). I can add events (days the staff might want to work, freelancer). These events are provided in the front-end via an template, shown in /3. This creates a side with x multiple forms, as long as this is the only way i found yet, where i can pass some variables back to the cms, to use its internal var-structure, as database, member-ids and so on without a wider range of page-redirects. And, if the Member successfully hit "take part", as long as the serverrequest runs, i want to disable the button to prevent multiple hits, and if the server sends success, i want to change value of button to "cancel" if he or she accidently hit the button or maybe realised that he/she dont have time for this anymore.
To sumarize that: Memeber comes, logs in, see 1 to x possibilities where he could work, hits 0 to x buttons to tell me he wants to work there without any side-reloads, goes away! Am Sonntag, 10. Juni 2012 23:05:08 UTC+2 schrieb Sanford Whiteman: > > I'm mobile so I can't recheck your Fiddle now, but it creates a bit of a > moving target if your "example" code isn't really to spec. There is likely > a design re/decision that we can help you make if you can describe the > wider UI/client-side goals of your app. Moo has more abstractions/macros > than just call()/bind() type stuff (for example, the Form.Request class). > > -- S. >
