Today I started to code version 2.3. I spent a lot of time categorizing all the suggestions (if you have your own, feel free to submit it here) with my own list (for your info, there are almost one hundred tasks in the complete list) and deciding what will make 2.3 cut.
With more and more people willing to extend our plugin’s native options, I am focusing on benefits for individual and teams adding external code into Kwik.
By the way, the fact of a feature not coming in this version does not mean that it will not come in a future release. However, it is also important to understand that some suggestions may not appear anytime soon because a) they are not a priority to the majority of users (some suggestions are specific to a project or a particular, non-reproducible, need), b) Corona cannot render (page curl, for example) or has known issues rendering it (masks, for example) or c) requires longer design times than others.
So, what is in the pipe?
Besides several bug fixings (some very annoying for a while), this is the list of things already coded (it will be available in next week’s first beta):
- Ability to create a project only for the new iPad (meaning Kwik will not generate @2 images for older iPads);
- Option to add external code from an external file (besides writing/pasting the code into the editor) – this will help a lot teams that will be able to share a Lua (or txt) file in a folder. When publishing, Kwik will read the file content and integrate the external Lua code with the auto-created one;
- Add external code in the main.lua file (I am hearing some “yay!!”s already);
The list below contains the things I am planning to add (hopefully no big issues will appear and I will be able to deliver all of them):
- Automatically make all layer sizes even (to avoid blur when zooming to other devices) – thanks to Julian Stokoe sample code!
- Compatibility with the new Widgets 2.0 library from Corona;
- Few new options for the drag interaction (clearly one of the top used features in Kwik 2);
- A few complex features that I prefer not to disclose/commit now;
- A couple of non-code related, “ready to use” new options
As always, I am looking forward to your feedback!