Re: Javascript repository or package for PEAR

> > you are right, if you would like to make web-apps user-friendly you have > > to use JS. > > I think that PEAR don't have to *depend* on JS. I mean that no PEAR > package should not work if JS is disabled in (or not supported by) the > browser, because is a PHP Repository. Even so, packages could add some > *optional* JS stuff to make the package frendlier to the end user when > JS is available. I think an application that allows customization and is specifically for generating js makes a great deal of sense. On chiaraquartet.net, we generate a dynamic menu of our concerts by extracting database information with php and generating JS that interfaces with a js frontend. It works nicely, and since we use PHP, we can also use a form-based approach for browsers that don't like js, or for people who have disabled it. Honestly though, only a few developers disable javascript, most users don't even know it exists, let alone how to disable it. So, applications targeted at developers should have the ability to work when the option to disable javascript is selected. Otherwise, working under many situations is simply a bonus that makes an application better, I think Greg