Re: QFC is horrible hack? [was: Can you serialize a Formbuilder object?]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jun 27, 2005 at 02:25:43PM -0700, Justin Patrin wrote: > > Would you please tell me how to repopulate the form values previously > > obtained after the new form is regenerated? > > You mean put the form values back in the form? Since > HTML_QF_Controller is a hack (yes, it's a horrible hack) it's not too > easy to do this. However, I believe that the HTML_QF_Controller > package supports this intrinsically...you can always pass the posted > array to setDefaults. > A "horrible hack"??! Ah, that's not what I wanted to hear right now. I'm in the (slow,painful) process of rewriting my whole app to make it work with QFC, because I desperately need that functionality. I find QFC annoying (object callbacks? gah.) and hard to work with, but I didn't realise that PEAR experts considered it horrible. If it's "horrible hack", am I wasting my time and limited braincells in doing this conversion? Is it a pointless exercise to use this package? Should I just write my own custom code do to multi-page forms, instead of using QFC? Is QFC going away and being replaced by something that is not a "horrible hack"? Will I have to re-write my app all over again at that time, in order to work with it? Frightened and anguished minds want to know. - -ken - -- - --------------- The world's most affordable web hosting. http://www.nearlyfreespeech.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCxhYle8HF+6xeOIcRAst7AJ4/Krq08pXtzNNbk1SkNpTcEKkEOgCeMzaX +5X3gN8r7wDJFcuAIY0NaxM= =Lh7P -----END PGP SIGNATURE-----