The AXR Project is a revolutionary open source project that will fundamentally improve our tools to create web sites and apps.
It's much in the style of current web standards, using plain text files linked together to create the final site, but with a complete separation of content and presentation, where the content is pure semantic data written in XML, and the presentation and behavior layer is written in HSS, a new language based on CSS, but with many powerful features, such as hierarchical notation, object orientation, modularization for code reuse, expressions (math), vector graphics, references (bindings between objects), and a very long etc.
This is the repository where we keep tools, and extras for the AXR project. This can be Code Completion and Syntax Highlighting for text editors. Basically anything that does not fit in the other repositorys. If you are in doubt, you can consult the wiki or contact the respository manager.
For more infomation about available plugings and extras, see the wiki page here: http://wiki.axrproject.org/Extras.
This repository is managed by Miro Keller ([email protected]). Please read through the entire readme before contacting him, since this may answer your question.
You can find work on the github issues tracker: https://github.com/axr/Extras/issues. If there is an unassigned or an old task, post a comment asking for assignment. Make sure you follow the coding standards and our workflow, which you can find below.
If you are not used to git, go ahead and read more here: http://help.github.com/ . Relevant to our workflow: http://help.github.com/fork-a-repo/ , http://help.github.com/send-pull-requests/
- Go ahead and fork the AXR/Extras repo. You will use that repository as your working repo.
- You can do any git changes you like to it.
- When you finish, go to your fork and send a pull request. We'll review it as soon as possible. After it has been reviewed and accepted, we will merge it into our repo.
Please create a new issue here: https://github.com/AXR/Extras/issues/new. To make the process of fixing bugs easier, developers need to know what causes the problem and also on what platform it happens. Be as detailed as possible, and make sure to include the following points in your bug report:
- What is happening.
- What did you expect to happen.
- How to reproduce.
- Your operating system's version.
- Which version of the prototype is affected.