← Other weblog tools

Making MT into a CMS →

More FormProcessor development

August 12th, 2003 | Quests/FormProcessor

OK, let me list where I’ve got to now.

* The FormProcessor Class is no longer passed a string containing the form fields. Instead you now load an XHTML file and select the form in that file you want to manipulate. The selection is based on the id given to the @

@ tag. This was implemented because
## I don’t want to have to store my forms in separate files
## I may have more than one form in the document
I am thinking about making it work like before if the document contains only one form, but have not reached a decision yet.
* All business logic attributes have been removed from the form tags, which was my original goal when modifying Simon’s code. Eventually they will be stored in a separate XML file (and I will provide a frontend to help you build these files); however, until the validation (and hence the necessary array structure) has been sorted, and until I can decide on the structure of the XML file, I’ve just implemented FormRuleExtractor to return an array identical to that it used to generate.

I’ll post some code shortly. I’ve spent the past 5 and a bit hours on it, so I’m going to take a break :-)
h3. Update [2003/08/13]

Version 0.3 code “now available”:http://peter.mapledesign.co.uk/quests/formprocessor/code/0.3/

3 comments ↓

#1 Carlo Zottmann on 08.14.03 at 1:47 pm

Umm, were exactly are the rules stored now? The repository doesn’t contain any rules declarations…?

#2 Peter Bowyer on 08.14.03 at 6:02 pm

They’re currently stored as arrays in the FormRuleExtractor class. Until I’ve sorted the XML format, you’ll have to modify these arrays directly.

#3 Christian Sobetzko on 08.16.03 at 3:00 pm

Hello.

I’m Chris82 from sitepoint. Sorry, for replying so late. I have a posted some comments over at sitepoint here: http://www.sitepointforums.com/showthread.php?postid=886706#post886706

Leave a Comment