Reply to thread

Message: [QUOTE="Peter Michaux, post: 4961938"] Very and especially when testing on a wide set of browsers. I think the code in this repository should be tested on a wider set than the following which took me days manually. <URL: [URL]http://forkjavascript.org/welcome/browser_support[/URL]> [snip] I think some pacing is needed anyway. In just couple weeks from now we can have a full Ajax module and that is a substantial component to any code base. Given what we've already discussed in the various threads, I would like to shoot for the following for the first milestone. * DHTML setOpacity * DOM queries getEBI getEBTN getEBCN (getElementsByClassName) getEBCS (getElementsByCSSSelector) (a very simple one) * Ajax form serialization XHR * automated testing * parsable documentation We will need to have threads on Ajax and documentation over the next while when the current threads have died down. That is sufficient for the first round and enough to reflect on how the process is going and if things need to be changed. After that I will certainly make my own build process and start using the code where I can in my own work. I hope so! I have already learned enough to justify my time invested. I'm not so concerned with that and that requires marketing which I learned I am not interested in doing. I'm interested to see if "Code Worth Recommending" is deemed to be code worth recommending by many comp.lang.javascript contributors. [/QUOTE]