Zerobrane configuration

Solar2D General Questions/Discussion
#1

I really tried to use the official Corona editor, but for all sorts of reasons it doesn’t suit me well so I’m using Zerobrane a lot as my IDE.  The only thing that I haven’t been able to get it to do is change the text colour of function calls.  I find it very helpful in Sublime Text that the function calls really stand out.  Does anyone know how to do this?  I’ve figured out that you can add “indicators” (e.g. underlining) to function calls in Zerobrane, but I don’t think this looks nearly as good.

Any Zerobrane ninjas out there able to share the necessary secrets, or is it not possible?

#2

@epicurus101, this is not currently supported by the version of Scintilla (the editor component) included in ZeroBrane Studio, but the next version of the IDE is planned to include a more recent version of Scintilla that supported changing text colors using indicators. I’ve included an example in the announcement (http://www.freelists.org/post/zerobrane/Upgrade-to-wxwidgets-31x), but you’ll need to use the branch from the repository if you want to give it a try. Paul.

#3

@epicurus101, to save you a bit of time, you’d need to have something like the following in the config (assuming you are using the upgrade branch):

styles.indicator.fncall = {fg = {255,0,0}, st = wxstc.wxSTC_INDIC_TEXTFORE}
editor.showfncall=true
 

Change the foreground (fg) color accordingly using r,g,b values. I may remove showfncall in the future, but for now, this is what you need to specify.

#4

In an effort to try and keep topics centralized, I’m posting to an old thread. (Perhaps ZBS needs it’s own subforum?)

I used (and loved!) Lua Glider in the past, but due to poor performance and lack of support have been forced to switch.  I’ve been using ZBS for 2-3 months and everything was working pretty well until 30 min ago.  Was running ZBS just fine for about 3h this morning, and literally between a “stop debug” and “start running again” the Corona Simulator doesn’t make it past the splash screen.

There have been no windows updates, anti-virus updates, and have confirmed that ZBS is not blocked by the firewall.  I’ve updated the User Preferences so that the debugger server starts at localhost in an effort to fix, but no joy.  Interestingly, I used to get the “can’t bind on port 8172” message, but now I’m getting “binding to port 56562” “listening on port” 56562.  

Any advice/troubleshooting would be appreciated!

#5

@lisa.briona, I’d check on a couple of thing. First, check if the other instance of the IDE is running as this may interfere with the ability of both instances to listen on the same port (it will look like one instance starts, but the other instance in the background is actually getting the debugger requests, but doesn’t respond to them, so the application looks suspended). If you are on Windows, then check Task Manager for “zbstudio” processes, close them all (if there is more than one), and then restart the IDE.

If that doesn’t help and you want to check the port number to try a different port, then you need to change it in two places: the IDE configuration (debugger.port=55555) and the debugger call in the application (require('mobdebug').start("localhost", 55555)). If you are not trying to change the port, then I’m not sure where “binding to port” messages are from as they are not generated by the IDE.

If none of this helps, then I’d like to see the output from one of the failed sessions (the content of the Output panel); just make sure that there is no other instance running and try with an empty configuration file. Thanks. Paul.

#6

@epicurus101, this is not currently supported by the version of Scintilla (the editor component) included in ZeroBrane Studio, but the next version of the IDE is planned to include a more recent version of Scintilla that supported changing text colors using indicators. I’ve included an example in the announcement (http://www.freelists.org/post/zerobrane/Upgrade-to-wxwidgets-31x), but you’ll need to use the branch from the repository if you want to give it a try. Paul.

#7

@epicurus101, to save you a bit of time, you’d need to have something like the following in the config (assuming you are using the upgrade branch):

styles.indicator.fncall = {fg = {255,0,0}, st = wxstc.wxSTC_INDIC_TEXTFORE}
editor.showfncall=true
 

Change the foreground (fg) color accordingly using r,g,b values. I may remove showfncall in the future, but for now, this is what you need to specify.

#8

In an effort to try and keep topics centralized, I’m posting to an old thread. (Perhaps ZBS needs it’s own subforum?)

I used (and loved!) Lua Glider in the past, but due to poor performance and lack of support have been forced to switch.  I’ve been using ZBS for 2-3 months and everything was working pretty well until 30 min ago.  Was running ZBS just fine for about 3h this morning, and literally between a “stop debug” and “start running again” the Corona Simulator doesn’t make it past the splash screen.

There have been no windows updates, anti-virus updates, and have confirmed that ZBS is not blocked by the firewall.  I’ve updated the User Preferences so that the debugger server starts at localhost in an effort to fix, but no joy.  Interestingly, I used to get the “can’t bind on port 8172” message, but now I’m getting “binding to port 56562” “listening on port” 56562.  

Any advice/troubleshooting would be appreciated!

#9

@lisa.briona, I’d check on a couple of thing. First, check if the other instance of the IDE is running as this may interfere with the ability of both instances to listen on the same port (it will look like one instance starts, but the other instance in the background is actually getting the debugger requests, but doesn’t respond to them, so the application looks suspended). If you are on Windows, then check Task Manager for “zbstudio” processes, close them all (if there is more than one), and then restart the IDE.

If that doesn’t help and you want to check the port number to try a different port, then you need to change it in two places: the IDE configuration (debugger.port=55555) and the debugger call in the application (require('mobdebug').start("localhost", 55555)). If you are not trying to change the port, then I’m not sure where “binding to port” messages are from as they are not generated by the IDE.

If none of this helps, then I’d like to see the output from one of the failed sessions (the content of the Output panel); just make sure that there is no other instance running and try with an empty configuration file. Thanks. Paul.