Re: What about javascript
| From: | (Stig Sæther Bakken) | Date: | Thu, 09 Aug 2001 12:05:41 +0000 |
| Subject: | Re: What about javascript | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-1338@lists.php.net to get a copy of this message | ||
[Bertrand Mansion <bmansion@mamasam.com>]
> Hi,
>
> Adam Daniel and I are finishing an html form class for PEAR. It is
> more powerful and more complex than the current form class in PEAR
> but I believe users can need both of them depending on their needs.
Cool. Would it be possible to use and extend the current HTML_Form
API (I mean the API, not necessarily the implementation), or do you
need a different API? Could you post a url to a prototype to the
list?
One of the things I'd like to do with an HTML form class is to connect
it with either DB_storage or Tomas's new DB_row class, so you can
define relationships between forms and database tables. So far I've
only defined a "storageObject" attribute and then I got lost thinking
how it should work... ;-)
> My question is about a javascript file we use for javascript validation on
> the client. Part of the javascript is computed by the php class and the
> rest, two core functions, are in a small external javascript file. I think
> this is faster both on client and server than to generate this file contents
> with a php script.
>
> Are there any problems with .js file in current repository ? Will the
> infrastructure (package installer...) know how to handle them ?
It would be good to know what pieces we are trying to organize before
deciding on how to deal with Javascript. Form validators are typical,
but I think they are specialized enough to make them part of the html
form package.
- Stig
--
Stig Sæther Bakken <ssb@alltheweb.com>
Fast Search & Transfer ASA, Trondheim, Norway