Re: More HTML_AJAX

Is this going to be broken into HTML_Javascript_JSON? The whole AJAX side is kind of trival to implement, and over-complicating a simple solution. The JS lib's look potentially usefull, however the present bundling of them into a single file make it difficult to follow (and please put usage examples in the comments above the code..) I would like to hear better ideas for how to deal with JS in PEAR - just bundling them in a package seems rather counter to distributing and maintaining PHP libraries.. I saw http://www.openjsan.org/ the other day and although it uses horrible Perl comments and '.' as the namespace seperators - It made me wonder if PEAR_Server could be used somewhere to host this seperately... - Quality JS code with Standards..?! Regards Alan On Tue, 2005-07-19 at 10:22 -0700, Joshua Eichorn wrote: > I've talked to Luca and we agree that the way forward is from my code. > The main reason for this is that in PEAR a library that covers a greater > number of use cases, by using drivers for encoding input and output and > other optional features. > > So if we can move on with some technical discussion on the code at > http://bluga.net/projects/HTML_AJAX/ > > I would like to get to a proposal soon but that will take a day or two > so Luca has time to pull his down, and I'll need a bit to get things > packaged, since Greg has always done it so I have no clue how. > > The one big thing I could use help on is where does JavaScript belong in > a PEAR package. > Also how do you guys manage doing development from a cvs checkout, I'm > on windows at the moment so I can't do symlink tricks, and all the > includes rely on the full path. > > Also I added some new features last night, the biggest one being driver > based serialization (right now just JSON and Null) and proxyless operation. > -josh >