No, what David meant was "don't write the whole xml parsing Code yourself and don't do it in the application Code - write a config handler"
Cheers and good night Felix Sent from my iPhone On 17.02.2009, at 01:33, "Craig Fairhurst - youds.com" <[email protected]> wrote: > � wrote: >> Two things I'd like to add: >> >> - never, ever, use the XML config stuff directly - write a config >> handler instead > Are you saying do not edit validator XML configuration files > directly??? > I am planning to write out validators XML configuration directly from > PHP from a pre-built Object, with validation based on the > limitations of > FormCheck (MooTools) which I will then extend in order to be able to > fully support the Agavi validation gotchas............ > Presume the config handler would reside with the rest of the code, > which > is currently in lib, but on your advice, will soon be a model. Is this > correct? > So my question is, is my assumption correct; never, ever edit the XML > validation configuration files directly, but instead use a config > handler to what? Write their output? Where would it go. > > ............ > > I thought was being completely innovative (perhaps naive) when I > started > this project, but the more I do it, the more it works. In so many > different ways. > > All feedback is appreciated aslways. Thanks. > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
