dolodobendan wrote: > Yes. Call me lazy. :cool: > > > > Different paths I could understand. > > > > Wouldn't it be easier not to use different resource names instead? > Sounds like problems in the making.
It is common to apply Minification to production JavaScript and CSS code. Minification removes unnecessary or redundant data without affecting how the resource is processed by the browser - e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on. The server has to send all this code in text form to the browser, so minification improves performance. On the other hand the resulting code after minification is not what you want to work with when you are reading/modifying the code. So I think the way Craig does it with Material Skin is perfectly correct. He runs his code through the minfy process and the result are the same files with .min included in the name. The Material Skin filter in SLX is just watching for when the browser requests specific .js and .css files. When it does, SLX just provides modified versions instead. So this is an easy fix in SLX to handle either naming convention, minified or not. R Greg Dawson Squeezelite-X ------------------------------------------------------------------------ rgdawson's Profile: http://forums.slimdevices.com/member.php?userid=65236 View this thread: http://forums.slimdevices.com/showthread.php?t=108550 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
