Recent Posts

1

Toolbox / Visual Studio Code

« Last post by John on August 18, 2017, 11:30:38 PM »

Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. It comes with built-in support for JavaScript, TypeScript and Node.js and has a rich ecosystem of extensions for other languages (such as C++, C#, Python, PHP, Go) and runtimes (such as .NET and Unity).

Free. Open source. Runs everywhere.

2

Interpreters / Re: MY-BASIC

« Last post by wangrenxin on July 24, 2017, 04:53:45 AM »

Sure.

There are some minor bugfix, and some other major improvements for MY-BASIC since my last updating here.

   * Added support for applying `ITERATOR/MOVE_NEXT` and `FOR x IN y/NEXT` for collections, class and referenced usertype. https://github.com/paladin-t/my_basic/wiki/Use-iterators
   * Added support for using a non-referenced usertype larger than `sizeof(void*)`. https://github.com/paladin-t/my_basic/wiki/Use-usertype-values#structure
   * Added interpreter forking functions.
   * Added a structured exception handling ability with interpreter forking. https://github.com/paladin-t/my_basic/wiki/Structured-exception-handling
   * Added a multiple condition branching, which is implemented in MY-BASIC code. https://github.com/paladin-t/my_basic/wiki/Multiple-condition
   * Added support for defining an alias for the `LAMBDA` keyword, which is helpful to write neat code. https://github.com/paladin-t/my_basic/wiki/Lambda-abstraction

Recently I'm working on an App powered by MY-BASIC, which will allow users to write game or application in an IDE with modern BASIC syntax. It's aimed to be similar as PICO-8. I'll initially release it for desktop (Windows), still WIP, yet details and releasing date are TBD.

There are also few API changes, which are easy to figure out.

BTW. don't forget to share your use cases with us via https://github.com/paladin-t/my_basic/issues/13.

3

Interpreters / Re: MY-BASIC

« Last post by John on July 23, 2017, 01:04:23 PM »

I recompiled the My-BASIC extension module for Script BASIC and all seems to have went well. The only thing I had to do is add the extra true argument to the mb_run() function wrapper.

Can you give us an update where things are with My-BASIC?

4

Scripting Languages / Re: Script BASIC Windows 32 bit - Download Available

« Last post by John on February 14, 2017, 02:40:28 PM »

I have finally assembled an Inno install for Script BASIC for Windows 32 bit with extension modules and their dependencies included. This is my first public release in this format and would appreciate any feedback you're willing to offer to make Script BASIC even better for everyone.

If you plan on using the MySQL extension module or use the SBHTTPD proxy web server, I highly recommend installing the 32 bit version of the XAMPP package (and any of the other free packages they offer) for your local  database and Apache web server environment.

Script BASIC Examples and Source


Download Attached

5

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by John on February 10, 2017, 01:04:35 AM »

All I have to do now is create the README file and I should be ready to post a public beta of Script BASIC Windows 32 bit packaged  with the Inno installer. (SBWin32_Setup.exe)

6

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by AlyssonR on February 09, 2017, 03:15:57 AM »

*big Thumbsup*

7

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by John on February 08, 2017, 05:43:30 PM »

The next release of the Script BASIC IDE/Debugger will be done with IUP so it's cross platform. I can't see anything special to VB6. It was just what Dave was comfortable writting his UI code in. I will also be including the IUP dialog editor integrated into the new IDE.

8

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by AlyssonR on February 08, 2017, 02:23:29 PM »

I haven't used FBSL, but that sounds very much like the story with many IDEs by the time they reach full maturity.

Like you, Mike, my programs tend to be composed of lots of reusable chunks of code that are arranged by purpose.

With some big, multi purpose code, I will even use #IF NOT([variable]) to exclude sub-functions that don't need to be included.

I do like the idea of mutiple windows into a large file, but I have never used it (and don't know wheter I ever would, now that my habits are pretty set).

9

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by Mike Lobanovsky on February 08, 2017, 11:41:33 AM »

I didn't want anyone to assume an Arduino-type interface.

In fact, a multi-tabbed MDI or SDI editing interface is very handy. I tend to split all my scripts in Eclecta (FBSL's stock IDE) into the main project file -- typically the one with the Main() function or the Events loop -- and a number of includes that would group the other functions logically according to their purpose in the application, pretty much like a Visual Studio would. That's what UltraEdit is designed to do too. UE is a great tool but it being a powerful all-purpose text editor seems a little bit of an overkill for a BASIC IDE.

Alternatively, a usable IDE might have splitters to divide the viewport into 2 or 4 distinct areas scrollable to their own portions within a long script, which would minimize time and effort to scroll the script back and forth while editing its portions. The most advanced setups would even allow the user to load different files into the different sub-windows of the split viewport. But still I find the multi-tabbed IDEs to be the most intuitive and easy to handle of all.

10

Scripting Languages / Re: Script BASIC Windows 32 bit

« Last post by AlyssonR on February 08, 2017, 05:25:30 AM »

Which is fair enough.

My comment about one-file-one-window was aimed more toward the folks who are used to having several files open at the same time (such as the main program and several #INCLUDEs).

I normally edit my source code in ConText, but when working with Arduino code, the IDE is an MDI container, allowing tab-switching between main program code and #INCLUDEs. I didn't want anyone to assume an Arduino-type interface.

I do prefer this interface.