![]() ![]() It's important to add that it need not have been this way. ![]() In fact, I had a lot of experience of SQL and stored procedures, so my first reaction to Lua was to give up and try to achieve my objectives by SQL. While you can dig around the SQL with a 3rd party tool, knowing the table structure won't help you much as it's not particularly relational and relies on lots of text fields containing unparsed blocks of text and Lua data. You do not need any knowledge of SQL since plugins cannot access SQL directly - in fact, the active catalogue's SQLite database won't allow it. I would start by reverse engineering the sample plugins in Adobe's SDK, then focussing on creating the plugin for your specific need and using that objective to concentrate your learning process. Adobe's SDK documentation which is geared to trained programmersĬ) Adobe don't provide a coding tool which would allow you to run and debug code, and while some Lua IDEs are available they too are oriented to trained programmers The problem is that this "relatively unknown scripting language called LUA" is indeed pretty obscure:Ī) you don't get the wealth of learning material and range of examples that you get with other languages So I put a lot of effort into learning it. ![]() My experience was in less-hardcore languages like VB, PHP, JS, Flash Action Script, and for a long time I found Lua quite a struggle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |