Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XUL support with test #13

Merged
9 commits merged into from
Dec 24, 2010
Merged

XUL support with test #13

9 commits merged into from
Dec 24, 2010

Conversation

aurium
Copy link
Contributor

@aurium aurium commented Oct 3, 2010

Hi James,

I make the specific loader object as you asked for and some other little improvements. I also add a mini-XUL App to test on this environment.

@jcoglan
Copy link
Owner

jcoglan commented Oct 3, 2010

How do I run the XUL app to see the tests working?

@aurium
Copy link
Contributor Author

aurium commented Oct 3, 2010

Easy :-)
xulrunner -app test/xulenv/application.ini or xulrunner -app test/xulenv/application.ini

I add this information on the README.markdown to help others

@jcoglan
Copy link
Owner

jcoglan commented Oct 8, 2010

Looks great. I'm working on a new core at the moment (see my three branch) and hopefully I'll be able to merge this in once that work is done.

Thanks for contributing!

@aurium
Copy link
Contributor Author

aurium commented Oct 8, 2010

Cool! Locks like you are making big changes with this number of commits!

I can't wait to use the official JS.Class on my project! :-D

@jcoglan
Copy link
Owner

jcoglan commented Dec 24, 2010

Just merged this into master - thanks a lot for contributing!

At the moment, master is where new libraries for the next release are being added. This release will either be 2.2 or 3.0 depending on how work on the 'three' branch is going. 'three' is mostly a rewrite of the core plus some new features that this rewrite makes possible. It's still experimental: it works but needs some big performance improvements before it can go into master. If this branch can't perform as required I'll probably do a 2.2 release instead.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants