enyo.load() may be able to help you but it's pretty low level so you'll likely have some work to do to use it effectively. Here's some rather dated work I did with it but the concepts should still be applicable even if the code doesn't work (yymv there).
I found out that LESS wastes a lot of time to compile the .less files. How can I load the compiled "css" files rather than "less" files? I don't want to run the deploy script every time. I want to load the "css" files of Enyo, but my source code will be remain "less" files. I hope you can understand my poor English. Thank you very much.
You could include the compiled .css files in your package.js file(s), rather than the .less file. If you don't list the .less files in your package, enyo doesn't touch them.
I'm using a custom build process to parse my less files before running enyo's own build script.
That works too. I had assumed you wanted to avoid updating the lib source directly but that's a pretty innocuous change.
Not sure what you mean by your follow up question. If you don't wish to have the code minified during the build, you can pass the -B option to the deployment script which will beautify it.
If you just want beautiful code to start with, choosing Enyo was a great choice!
I mean, the source code in this forum. I insert the source code using "code" bracket, but it's quit ugly. How to insert source code like your beautiful source code?
Comments
enyo.min.js
enyo.min.css
app.min.js
app.min.css
http://blog.technisode.com/post/41331812157/enyo-remotecontrol
I don't want to run the deploy script every time. I want to load the "css" files of Enyo, but my source code will be remain "less" files.
I hope you can understand my poor English.
Thank you very much.
I'm using a custom build process to parse my less files before running enyo's own build script.
Instead of your advice, I modified the package.js under onyx/css to:
enyo.depends( //"onyx.less" "onyx.css" );
Also the package.js under moonstone/css to:
enyo.depends( "moonstone-light.css" );
Is this correct?
Not sure what you mean by your follow up question. If you don't wish to have the code minified during the build, you can pass the -B option to the deployment script which will beautify it.
If you just want beautiful code to start with, choosing Enyo was a great choice!
I insert the source code using "code" bracket, but it's quit ugly. How to insert source code like your beautiful source code?