| 8:35 pm on May 28, 2003 (gmt 0)|
No promises about if or when -- this is free labor here, after all ;) But knowing what's on your mind will help direct future intallments.
| 9:58 am on May 29, 2003 (gmt 0)|
| 4:58 pm on May 29, 2003 (gmt 0)|
| 11:09 pm on May 29, 2003 (gmt 0)|
I will say that I still write all my own js and think it is as important as the scripting (well, almost). They are all pieces of the puzzle.
Content, HTML, JS, PHP, Graphics CSS, etc are all needed to make a site. Each has its own part to play. I don't need to script something that js could do better, right tool for every job.
What about basic event handling as a topic?
What's a WYSIWYG?;)
| 10:47 am on May 30, 2003 (gmt 0)|
You can't handle real time events and real time interactivity with a server side script - you need a client side script.
As for off-the-shelf code, it's great, but in order to customise a script you need to understand the technology. A lot of the free for use script are hugely bloated due to the need for ease of use (for example the dHTML menu scripts).
| 3:23 pm on May 30, 2003 (gmt 0)|
I'll ditto BlobFisk above. You need to have both solutions available - client and server.
There's no reason to send a request to the server only to return it because a field is left blank, or a person only put 6 digits where 9 were required. Those can be trapped faster client side.
Locales are another reason to use client side scripts. Today's date and current time are not the same on my server as they are on the client machine.