Re: Javascript repository or package for PEAR (repost)

On Fri, 7 Feb 2003 12:49:46 -0500 Analysis & Solutions <danielc@analysisandsolutions.com> wrote: > Making websites that require JavaScript in order to function thus reduce > the usefulness of the web. Although I have to agree with you here to some extent (with the exception that I think it´s okay to use JS on websites to make some small things more comfortable, as long as BC for non-JS browsers remains), you have to keep in mind that there´s not only the web. In closed intranets, it can make a lot of sense to use a lot of Javascript, as you can make application GUIs much more powerful, faster and more intuitive for the end users, which boosts user acceptance for your applications (users are normally used to offline applications who have a way faster reaction time than most web apps). So having a package that creates some commonly used JS so developers can parse this into templates on the fly ain´t too bad an idea in general (although I usually prefer to put the JS directly in the templates). Regards, Markus -- Markus Wolff <wolff@21st.de>