| Justin Patrin 2006-04-20, 7:01 pm |
| On 4/20/06, Charlie van de Kerkhof <pear@mowd.nl> wrote:
> Hi,
>
> On 20 Apr 2006, at 23:07, Justin Patrin wrote:
>
>
> That's true. I use my own form because I want to use a standard
> QuickForm renderer.
> And now for me everything is clear. Because I use my own form I can't
> use the benefits of DB_Table.
>
>
> It is my first time using PEAR packages and yes, still figuring out
> how some of them works.
> But how can I understand how *it* works? By reading documentation etc.
By reading the documentation, yes. There are docs for QF and there are
examples for the packages which should give you an idea of how they
work.
> Am I the only one that don't want the standard form with table output
> of getForm()?
Probably not.
> Should I understand how it works from the source code if I want to do
> something 'slightly' different?
> No one to blame btw... ;) Only myself.
>
>
> getForm() works perfect. But as I know now is that I can't use
> renderers from QuickForm in combination with DB_Table.
> Am I right?
No. Of course you can use another renderer. DB_Table simply gives you
a QF object which you can do whatever you want with, including
adding/removing elements, rules, setting options, etc. etc. Do the
same thing you're already doing except with the form that DB_Table
gives you.
>
>
> Thanx for the tip!
>
> I very sorry if I bothered you all with so much confusion and trouble.
> And I thank you all for your help and your patience.
>
--
Justin Patrin
|