Re: RE: Form.php - why returnStart ?
| From: | Bertrand Mansion | Date: | Sat, 27 Jan 2001 10:29:52 +0000 |
| Subject: | Re: RE: Form.php - why returnStart ? | ||
| References: | 1 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-1199@lists.php.net to get a copy of this message | ||
Hi Mikhail,
le 27/01/01 1:19, Mikhail Zabaluev à mookid@sigent.ru a écrit :
>>> In the code, this supposes I have created a table and I want my header
>>> beside my text field (which is how it is most of the time) but if
>> ... that's probably, where you begin to limit the class to some certain
>> applications. i have never been so flexible and fast designing forms as
>> with this class ;)
>
> You could be even more fast if you could build forms from XML descriptions
> like I do. Also, mixing output functionality with core representation of a
> form sucks IMHO. There should be configurable and extensible
> faces/frontends/etc.
Thanks for summarizing my worries which apparently Urs did not understand. I
think a form class should only manage fields, fieldnames, buttons, errors
and other form elements but no html formatting even if it is much faster to
create a form with embedded html.
The idea of faces is quite interesting and I think there should be a way to
link template classes and form classes. It is not the case today and it
makes Form.php not very useful for me. I am pretty sure that soon somebody
will get rid of returnStart or Start in the class, that is why I can't use
that class.
Of course, building forms from XML descriptions could be useful for some
people but should not be the only way.
I was also wondering if there was a way to cache templates so that they
won't have to be opened from the disk every time a page is opened. This is a
topic I am completely ignorant of.
Bye,
Bertrand Mansion
tapage.fr