HTML_AJAX next steps
| From: | Joshua Eichorn | Date: | Mon, 18 Jul 2005 01:58:08 +0000 |
| Subject: | HTML_AJAX next steps | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-38682@lists.php.net to get a copy of this message | ||
So I got a bit more done on HTML_AJAX.
Async calls now work and the javascript is cleaned up a bit though this is an area when more work is needed.
I also wrote a server class so you can include your javascript instead of having it inline.
The code is all at: http://bluga.net/projects/HTML_AJAX/
The stuff I would like some feedback on is:
http://bluga.net/projects/HTML_AJAX/HTML_AJAX_Server.phps, http://bluga.net/projects/HTML_AJAX/test_auto_server.phps
Does this init{className} api seem like a solution that will work longterm for managing exporting tons of different classes
http://bluga.net/projects/HTML_AJAX/build_javascript.phps
Whats the long term way of managing this script, shoud it be cvs only and build the js before releasing or should I turn this into a javascript class and package it up
Speaking of javascript the server can hide its true location on the disk now, but how do I find it and where is the proper place for this
Finally what do I do about pepr, there is already and Ajax proposal http://pear.php.net/pepr/pepr-proposal-show.php?id=275
Do I wait for Luca to respond, can I just put in a competing proposal?
I'll package this up as a PEAR tarball once someone helps me figure out where to put the javascript
-josh