compiled with advance optimization#96
Conversation
|
Thanks. It will take me some time to properly review this. If you need something quicker then you can make other PRs with smaller chunks of code. Some quick notes:
I really appreciate the work you've done and especially would like to get all the commenting fixes merged in but we need to clean this up. Also I can't accept API changes that would break some old code without a good reason. Chunks that should be in separate commits(and ideally in separate pull requests):
|
|
Thanks for your very nice game engine and comments. It was quick pull request to see if maintainer are interested in such changes. I will send a new pull request, but there are some breaking API changes, of which I could be not removed.
will remove
has been removed.
No. instanceof method can be used.
OK, but I still think decouple with goog.DEBUG. perhaps, introduce lime.DEBUG.
it is not mine.
OK Regarding, coding style, I strictly follow Google JS guide and gslint. So it will be 2 space indenting and 80 char per line. The code must be compiled with the most restricted closure compiler setting. Thanks again for great library. |
|
History also needs to be cleaned so try to start from a new branch and cherry pick/squash. 4 spaces. This isn't up for discussion. I also use 2 spaces myself but theres nothing worse than reading a file that has has some lines using 2 spaces and some lines with 4 spaces. And we can't convert the whole project because it will screw up all merges from other branches. |
|
of course, 4 spaces, for this project. It will take a while to get new PR. I contribute open source projects on my spare time. |
Add few param annotation and make some changes in object inherit pattern similar to closure library.