Thanks for checking it out.
The reason we have posted beyond.js is precisely so that people get a chance to play with it and test it on verious platforms. There are two reasons why beyond.js (or the HTML page that uses it) may fail in a specific browser:
1. JavaScript incompatibility
2. DOM incompatibility
The first one has to do with JS features added in later versions of that language. As Sjoerd mentioned above one such feature, which is used extensively in beyond.js, is the function.apply() method. This method was added to IE in version 5.5 of the script engine, which is bundled with IE5.5. We have provided an implementation of this method for platforms that don't provide it but it was flawed. Sjoerd has fixed the flaw but perhaps there are other bugs in it as well.
DOM incompatibility issues are a very familiar problem to anyone doing client-side browser programming. beyond.js is more of a JavaScript utility library than a browser services library (although it does provide some browser services) so hopefully it will be less effected by this issue. In the case of the sample page, Sjoerd specifically mentioned that it wouldn't work on Mozilla because of incompatibilities in the event model. Sjoerd and I are currently looking at this issue in the hopes of leveraging beyond.js facilities to make it easier to write cross-browser code.
Sjoerd and I would really like to see beyond.js become a community effort. I personally believe that ideas expressed in this library can take JS programming to the next level (although they also take a bit of getting used to :) We are both doing this as a hobby and a learning experience so we are limited in the amount of resources we can put into this project. Hopefully this process will gain traction when Sjoerd starts explaining the capabilities of this lib on his web site.
|