If a LLx template with script embeded is installed in LL, then what will happen?
If a LLx template with script embeded is installed in LL, then what will happen? LL just ignores script, and no problem ?
]]>
© 2024 Lightning Launcher Google+ Archive | DISCUSSION Theme by: 
D5 Creation | Powered by: WordPress
D5 Creation | Powered by: WordPress
< ![CDATA[
Yes, they will be kept but never run
]]>
< ![CDATA[
Pierre Hébert LL Home does not have include the Script Engine? Not even the “runtime”? So templates with scripts exported with LLx require LLx to be used?
Thought when you began implementing scripting you said otherwise. I understand from “commercial” point of view (Must. Buy. LLx.), but is an important point designers using script must note.
]]>
< ![CDATA[
LL can run script, but can’t edit it.
Hmm, it might be good, although the decision is totally up to Pierre Hébert .
]]>
< ![CDATA[
Indeed I changed my mind about scripts in LL. At the beginning, with the first script implementation, I thought this would be possible to allow it.
Later, with the updated implementation I understood this wouldn’t be possible to let LL run scripts. This is not a commercial nor a technical reason (even if obviously the engine adds a significant weight to the app). The thing that really made me changed my mind is that scripts have the capability to slow down the app (or not), or even break it. They must be used with caution and if an inexperienced user load a template with scripts and something does not run as smoothly as it could, then it will blame the app, not the template. My fear is that a non expert user may not understand the difference (even if LL already requires some sort of functional brain 😉 ). As LLX is geared toward advanced users, I hope that this script feature, which is very particular, will generate less confusion and less frustration in LLX.
]]>
< ![CDATA[
Pierre Hébert Perfectly understood. A suggestion: when exporting a template, please at a dialog one has to choose whether the template can run on LL or whether it requires scripting. Templates with the “scripting required”-flag should not be possible to be imported in LL. This helps the designers to avoid complains if users import a script-dependent template in LL and nothing works.
]]>
< ![CDATA[
Indeed, I planned to add this right at the beginning, but as detecting whether scripts are used or not is difficult I had to delay its implementation. This will be implemented one day though, and I agree that the sooner will be the better.
]]>