maybe also an extra lua dir?
The size of this uber-library could also be a problem: if all the functions are in a single file, that would be huge. (I am already forced to use require because of limitations in script size !!)So, for LUA script I suggest:1) for end users, a library of packaged scripts, each one with its libraries. ZIPPED in the distro2) for developers, a shared pool of functions in the Wiki
Hi Phox,Quotemaybe also an extra lua dir?YES, unbedingt We will also get LUA libraries for universal usage in the future - i started collecting all my LUA snippets like date / time functions, someday we can publish such libs with the build, scripting with LUA is so nice, yeah !...you can also write the same 100+ lines in all of your uBASIC scripts, again and again, but 2 lines in LUA like require "mylib" runMyFunc()are a bit smarter for lazy people like me
PhyrePhox,this is a very good idea, but some scripts are constantly changing, the maintenance could be very hard.but I must say you are very good at this :-)Anyway, a centralized library of scripts would be very useful for end users.On the other hand, a a shared library of functions/snippets would be very useful for scripters, but in this acse the Wiki format is probably better, as it's more easy to divide and catalog snippets.The size of this uber-library could also be a problem: if all the functions are in a single file, that would be huge. (I am already forced to use require because of limitations in script size !!)So, for LUA script I suggest:1) for end users, a library of packaged scripts, each one with its libraries. ZIPPED in the distro2) for developers, a shared pool of functions in the WikiI am curious to know the opinion of other developers...
Quote from: fbonomi on 17 / August / 2008, 18:50:13The size of this uber-library could also be a problem: if all the functions are in a single file, that would be huge. (I am already forced to use require because of limitations in script size !!)So, for LUA script I suggest:1) for end users, a library of packaged scripts, each one with its libraries. ZIPPED in the distro2) for developers, a shared pool of functions in the WikiI would suggest more smaller modules for the 'library', rather than one big one. Disk space is essentially a non-issue (I doubt the total of all scripts ever written for chdk amounts to one camera jpeg) but runtime memory is quite restricted. Having to "require" multiple packages is not a big deal.As for what should be included, a decent intervalometer and MD would be my top picks. Bracketing can mostly be done without resorting to script, but maybe there's some techniques that are better done with script ?You don't need to include everything under the sun. I think users would be better served by a couple good example of each general task rather than everything that's ever been written. This is especially true when the scripts need to be maintained to follow updates in CHDK. You can always include more in an "extras" directory or provide links, but IMO the ones that come pre-installed should be a relatively select few that are maintained and known to be working.I'd say that the "official" scripts and script libraries should be in an SVN repo, and the authors should have commit access.
what do you mean by ZIPPED in the distro for endusers? you mean an extra zip IN the zip?
you know there is a command to find out if the cam has a video button? i guess this way you could make only 1 script and isnt it better to use like get_ready instead of using get_propset? i added get_propset for these cases that people find propset that i didnt include with special get_ commands yet. on the other hand, i havent really looked @ your script yet, no time yet
Started by mattkime General Discussion and Assistance
Started by mattkime LUA Scripting
Started by tkeeg « 1 2 3 » General Help and Assistance on using CHDK stable releases
Started by nikivan Script Writing
Started by JeepFreak General Help and Assistance on using CHDK stable releases
