I have little idea of what best practice is in the JavaScript world, but
I wonder if we could clean up the core JavaScript code a little, perhaps
even introduce some coding standards, etc.
I've been perusing "Prototype" - a JavaScript library that supports much
AJAX goodness, and really like what I see:
* Use of top-level objects (often empty) as namespaces
* A Class.create() function that makes class declarations seem more
natural
* A Ruby-like "extend" function for mixins
See http://prototype.conio.net/dist/prototype-1.2.0.js ... I'm not
suggesting we integrate it, just wondering if people like the
coding-style used.
What do you think of introducing a top-level "Selenium" namespace, and
pushing BrowserBot etc underneath it? It might mean pushing the
existing "Selenium" object down a level, though - "Selenium.API"?
Can we agree on no TABs in code/tests, or is that contentious?
Also, I was chatting offline with David Kemp and Daz Deboer about the
possibility of reducing the number of Selenium javascript files ... at
least for distribution, if not for source-control. I suggested a
"selenium-fitrunner.js", with "selenium-core.js" containing everything
else, which would make deployment easier. We could even version-control
it as separate files, and combine it in a build step. I don't think I
convinced anyone :-(
--
cheers, MikeW http://www.dogbiscuit.org/mdub/
_______________________________________________
Selenium-devel mailing list
[EMAIL PROTECTED]
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-devel
