notebook.kulchenko.comZeroBrane

By seeking, you will discover... -- By seeking, you will discover... Subscribe GMaps: Canvas overlays with colors 2 Jan 2017 Back in 2009 I made several small GoogleMaps-based projects to show drawing on top of maps using canvas tiles. Till this day I continue getting emails with questions about some of those projects, and one of the frequent requests was whether it's possible to extend the markers to use multiple colors. You can find the code for the "original" map with 400 markers using the same color here . This map shows the markers and allows the user to mouseover them with the cursor changing its shape when passing over a marker. A slightly different mechanism is shown here , which generates real markers, but only for those tiles that are currently displayed (to limit the number of markers displayed); the demo doesn't fully work for v2 API as it seems like isHidden method has changed its behavior. The modified map with 400 markers using multiple colors is available here . It assigns one of two colors randomly, but you can use a similar mechanism to pick the color you need based on some marker data. 0 Comments Posted by Paul Kulchenko on Monday, January 2, 2017 at 6:56 PM Filed in maps | Tagged api , example , maps , tutorial Torch debugging with Studio 14 Jan 2016 Torch is a powerful computing framework that includes various machine learning algorithms and is built on LuaJIT, so it looked like a natural fit for support in Studio. Soumith Chintala already did bulk of the work with Studio clone that included Torch7 interpreter with debugging support, but it required some core changes, so it couldn't be easily combined with Studio. As the plugin API was extended with new functions in the most recent versions of the IDE, it became possible to implement the integration with Torch as a plugin, which is now available in the plugin repository . Let's see how you can debug a Torch script or an application using this plugin. Studio configuration. 1. Get Studio (1.10+). These instructions are for Windows, but the debugging should work on Linux and OSX as well. 2. Get torch plugin and save it to HOME/.zbstudio/packages/ or ZBS/packages/ folder (where ZBS is the path to Studio location and HOME is the path specified by the HOME environment variable); the first option may also be preferable for Mac OS X users as the packages/ folder may be overwritten during an application upgrade. 3. If you have TORCH_BIN environmental variable defined, you can skip this step; if not, you can open Studio config file ( Edit | Preferences | Settings: User ) and set path.torch value pointing to the th executable or the directory with the torch library ( libtorch );for example, path.torch = [[D:/torch7/]] . You'll need to restart the IDE for the configuration changes to have effect. 4. Start Studio ( zbstudio.exe or zbstudio.sh ). Script debugging. We can now debug a simple Torch script: local torch = require 'torch' local data = torch.Tensor{ {68, 24, 20}, {74, 26, 21}, {80, 32, 24}, } print(data) Save it as test.lua and set the project directory to the folder where you saved the script ( Project | Project Directory | Set From Current File ) and select Torch as the current interpreter by going to Project | Lua Interpreter | Torch-7 (this option is only available when the Torch plugin is installed). Now if you Run the script, you should see the following output: 68 24 20 74 26 21 80 32 24 [torch.DoubleTensor of size 3x3] If you select Debug , you should see the debugging started at line 1 and should be able to step through the script, set breakpoints, look at the stack trace, and use all other debugging functionality available in Studio. If you set a breakpoint on line 7 and run to that line, you should see something similar to the following screenshot: For those of you familiar with ZBS -torch, the plugin provides similar functionality, but implements visualization of Torch elements in a way similar to how it's done in Torch REPL and also removes backspaces in Torch output that is shown in the Output window. 17 Comments Posted by Paul Kulchenko on Thursday, January 14, 2016 at 1:40 PM Filed in zerobrane | Tagged ide , torch , zerobrane Installation complete. You may need to rest... 13 Jan 2016 Found this gem in my archives. This is the snapshot I took about 6 months ago after one of the Adobe Flash installs. It's interesting that the next version didn't have this glitch. 0 Comments Posted by Paul Kulchenko on Wednesday, January 13, 2016 at 1:31 PM Filed in programming Redis Lua debugging with Studio 5 Jan 2016 Redis is a popular open-source in-memory datastore that provides Lua scripting among its other interesting features. When I first looked into getting the debugging of Redis Lua scripts to work with Studio , I wasn't able to accomplish much as the debugger used in the IDE relies on the debug library, which is not available from the Redis sandbox that runs Lua scripts. This has changed when Salvatore Sanfilippo implemented a debugger for debugging Lua scripts running by Redis. It supports stepping through the script, setting breakpoints, inspect variables, and other functions you'd expect from a debugger. It accepts commands over the same protocol as Redis itself and provides command-line interface to work with. Availability of this debugger in Redis made possible to create a package in Studio, that would act as a proxy and forward requests to the debugger, thus enabling full access to debugging features in the IDE. After being contacted by Itamar Haber from RedisLabs, we quickly put together a plugin for Studio that you can get from the plugin repository (make sure you use Studio v1.10 or later). Itamar also put together a post with detailed instructions and a tutorial on how this integration works for debugging Redis Lua scripts with Studio. Leave a comment or send me an email if you run across an issue with the integration package or have suggestions on what can be improved. 0 Comments Posted by Paul Kulchenko on Tuesday, January 5, 2016 at 1:49 PM Filed in zerobrane | Tagged ide , zerobrane Debugging Mashape Kong plugins with Studio 22 Dec 2015 Mashape Kong is open-source API and microservices management system based on Nginx and written in Lua that also supports Lua plugins. Dietmar Wolz put together a detailed tutorial on how Studio IDE can be used to debug Kong Lua plugins. If you are looking for debugging of Nginx Lua scripts in general, then check this earlier post for details . 0 Comments Posted by Paul Kulchenko on Tuesday, December 22, 2015 at 10:12 PM Filed in zerobrane | Tagged ide , zerobrane Studio in black 9 Jul 2014 A screenshot of Studio in black (Ubuntu 12.04, MATE Desktop with BlackMATE theme, TomorrowNightBright ZBS theme), courtesy of naturally as shown in Moai forums . You may click on the image to see it full screen. You can choose one from several color themes that are included with Studio. 0 Comments Posted by Paul Kulchenko on Wednesday, July 9, 2014 at 4:53 PM Filed in zerobrane | Tagged ide , zerobrane Moonscript debugging with Studio 21 Jun 2014 Moonscript is an interesting dynamic scripting language that compiles to Lua . Moonscript can be dynamically compiled and run using a component called moonloader and because moonloader keeps a mapping between the moonscript code and the produced Lua code, I thought it could be possible to extend the debugging in Studio to take that mapping into account in some way. The version of the debugging bundled with Studio v0.70+ provides a way to specify a line mapper that can be used to map the current line in the Lua code to the line number in the "original" moonscript code. This code is "injected" in the debugger when the debugging session is started, so any line number used by the debugger (whether to show the current line, set a breakpoint, or display a stack trace) goes through that mapping. Let's see how you can now debug moonscript files . Studio configuration. 1. Get Studio (0.70+). These instructio...