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
How To Build #5
Comments
Something along the lines of
Changes to build (compiler options) can be made in the xml. |
Hi there, mvasilkov is correct. The build file is an ant script that basically just minifies the src using the google closure compiler. Its does not do anything too clever at the moment :) Its a good point though, I will look into updating the readme file to give people a little more info on what it is. |
And how are you debugging? Do you use source maps? |
Putting everything into one file makes debugging harder on errors(you lose vital information such as correct file name and line number), also on a slower computer building process might take a minute or two. I'd prefer a big html file that has included all source files. |
I see what you're saying, so a HTML file with all classes included? That is how I have been testing it :) Where would a file like that sit in the project structure ya think? In the build folder? |
thats a good question, right now there are no tests, but if there will be then that folder might be a good place to start |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
(Whoops, had to edit this issue because I accidentally prematurely posted it :/)
Annyways, I noticed you guys included some built files in the repo. I was wondering if you could include some instructions in the README to create our own builds.
For example, I would love to make a build that is not minified, to be able to explore the source a bit more.
The text was updated successfully, but these errors were encountered: