-
Notifications
You must be signed in to change notification settings - Fork 2
Added dogescript #12
base: master
Are you sure you want to change the base?
Added dogescript #12
Conversation
wow& hideLoadingScreen() | ||
|
||
very animations = [/* | ||
*/ "spin", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't need that comment anymore tbh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment is needed because dogescript adds a semicolon to the end of every line starting with "very". I'll change this to statements constructing the array instead though e.g animations dose push "zoom"
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done this in 9044cde
We can't had a dependency on npm, because GitHub won't run that for us. |
The npm dependancy is only for showing how to compile the source file, all npm dependant things have been compiled using webpack into the included file - compileDJS.js |
This is a much less hacky method of setting the value of animations than using a javascript initialiser list
42fa40f
to
be12f67
Compare
Server side/developer side, same problem. Can we avoid having to run tools? |
Only the dogescript compiler (and a small helper file) is being compiled using npm on the developer side, the dogescript source file is still being compiled on load by the compiled dogescript compiler - I don't think compiling dogescript on the developer side is going to be much of a problem. If it is, I could manually concatenate all files and dependencies of dogescript into one javascript file, but this is basically what webpack does in it's compilation process. |
No description provided.