Development

In the previous blog post I presented areas in which thinBASIC ecosystem could be improved in order to harden the stability of both the core and modules, including those developed by you using ThinBASIC SDK.

Today, I would like to share my views on how looking at the end might give us ideas what we need to count with before we will start implementing first line of test supporting functionality.

What kind of information do we expect from tests?

We need to raise ...

ThinBASIC project will celebrate 15 years since its first public release this year in August. It is really a joy to see how much it evolved, how the user base changed and what incredible amounts of excellent project were finished with it.

While the original "thin" thinBASIC core was accompanied by a few modules, such as file manipulation or 3D graphics, the current version has over 50 specialized extensions, which make thinBASIC much more versatile tool than the one from more ...

The introductory blog post tried to sum up the advantages of GitHub for your thinBasic project storage and publishing.
Let's leave the cold theory and embrace some practical example! This post will describe the basic workflow for founding a new thinBasic project at GitHub.

Grab the fork
Multiple times, across the original article, I mentioned the term fork. As it might not be obvious, let's have a look at what does it mean to create fork of GitHub repository.

...

Your code. Your creation. Your history of thrill, discovery, ingenious solutions and proud publishing.

Let me remind you of how we shared the code in the past, and what could be the possible direction for 2017.

For years, we got used to a simple system. When we developed piece of code worth sharing or showcasing, we pasted it as forum post, or added it as attachement.
This approach worked, and over years we learned some rules - to stick the latest version to the first ...

ThinBASIC user defined types, also known as UDTs, offer convenient way to inherit properties and functions - via the Extends keyword.
This approach allows inheriting properties and functions from the base UDT. This is very useful, but there is one catch one needs to be aware!

If you specify function in the new UDT which has the same name as function in the base UDT, override is performed and the whenever you use the function, the one from the new type is used.
This is expected ...