Been Reading Hal Helm's newsletters and they have got me thinking about objects and coupling - so using the pages FORM variable is high coupling and therefore a bad thing.
but if that is what it takes I am sure I will get over it ;-)
Yep, though the real question is, is a "publishing rule" the right tool for the job. Publishing rule's are a mechanism designed to select what content to be output into a container. Does this really fit with the idea of processing form input?
Maybe the concept of form handlers/controllers would be more suitable. For example in my Link Directory module there needs to be a way for uses to submit votes on links. Ideally I could register that form controller with Farcry so it gets called upon form submission... rather than have users create a util nav node with a set navid, then assign the form controller as a publishing rule to one of its containers (which is the current way of doing it).
Each form controller could have a unique ID embedded within it (as a getID() method maybe?), and in your <form> you could include a hidden field specifying the ID of the controller which should handle the submission.
- tim
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
