Code: Select all
- Android Cordova updated to v15 and Android SDK to v36SpiderBasic 4.00 beta 1 is out !
Re: SpiderBasic 4.00 beta 1 is out !
- 2026-06-22: 4.00 beta 1 is out, with the whole doc finished, and full local file support on Android and iOS. Bumped to 4.00 due to heavy syntax changed and more BASIC like program flow without relying on callbacks.
Re: SpiderBasic 4.00 beta 1 is out !
Un immense merci!
Re: SpiderBasic 4.00 beta 1 is out !
In 4.00 B1 help file
- History still showing up to 3.20
- All file commands still only mention domain and cache clauses for IOS and Androind file operations
- RequestFileSystem, and possibly others, missing entirely except for use in some FileSystem snippets
- No change or snippets of new synchronous stuff. Most supported commands still show async only
Re: SpiderBasic 4.00 beta 1 is out !
Great news, thanks!
Re: SpiderBasic 4.00 beta 1 is out !
Thanks, it sounds like good work with await for some functions.
But I can't really test, because docs seem not to be finished, and seem to be inconsistent.
I wanted to give the 4.0 beta 1 a try with my biggest app, and compile stopped really early at a result=CreateFile(#File, Filename$, @Callback, Flags), from the help docs it still should have a Callback as parameter, but clicking on the code in the IDE shows the command help in the bottom status bar now without?
And commands that were changed or not changed seem also inconsistent to me, for example at an earlier ReadFile(#File, Filename$, @Callback, Flags) of the same source the compile didn't stop, and help docs and status bar help both show a Callback parameter?
At the moment for me it is not clear, where a Callback is still needed and called in what way or at what stage of its job.
Does a changed command now simply wait, until it is ready and then calls the callback? And before the changes other commands behind a changed command were directly reached and the callback was "independent" of it?
Because also from a try of the 3.30 Beta 2 some days ago, I'm not happy with forced changing HttpRequest, in my app I used different procedures to send out requests to my PB server and setting some vars or a progress field after calling HttpRequest, do something else while waiting maybe 20 seconds for the servers reply, then receive the reply as callback, or react if reply doesn't come in a timeout etc.
So with the new await there are now a lot process sequences that no longer work, when HttpRequest stops until the request is fully done.
Maybe a new #PB_HTTP_Asynchronous could be integrated?
Additionally one try of the 3.30 Beta 2 some days ago fully deleted one of my included Cordova plugin folders content on my development machine.
As this plugin was in development there were some hours of work deleted.
Sorry, but actually I'm in a lot of important development of my app, and can't waste more time for this.
But I can't really test, because docs seem not to be finished, and seem to be inconsistent.
I wanted to give the 4.0 beta 1 a try with my biggest app, and compile stopped really early at a result=CreateFile(#File, Filename$, @Callback, Flags), from the help docs it still should have a Callback as parameter, but clicking on the code in the IDE shows the command help in the bottom status bar now without?
And commands that were changed or not changed seem also inconsistent to me, for example at an earlier ReadFile(#File, Filename$, @Callback, Flags) of the same source the compile didn't stop, and help docs and status bar help both show a Callback parameter?
At the moment for me it is not clear, where a Callback is still needed and called in what way or at what stage of its job.
Does a changed command now simply wait, until it is ready and then calls the callback? And before the changes other commands behind a changed command were directly reached and the callback was "independent" of it?
Because also from a try of the 3.30 Beta 2 some days ago, I'm not happy with forced changing HttpRequest, in my app I used different procedures to send out requests to my PB server and setting some vars or a progress field after calling HttpRequest, do something else while waiting maybe 20 seconds for the servers reply, then receive the reply as callback, or react if reply doesn't come in a timeout etc.
So with the new await there are now a lot process sequences that no longer work, when HttpRequest stops until the request is fully done.
Maybe a new #PB_HTTP_Asynchronous could be integrated?
Additionally one try of the 3.30 Beta 2 some days ago fully deleted one of my included Cordova plugin folders content on my development machine.
As this plugin was in development there were some hours of work deleted.Sorry, but actually I'm in a lot of important development of my app, and can't waste more time for this.
Last edited by hoerbie on Wed Jun 24, 2026 11:50 am, edited 1 time in total.
Re: SpiderBasic 4.00 beta 1 is out !
Great news! Thank you.
I'll try to test as much as I can.
I'll try to test as much as I can.
Kind regards, bembulak
SpiderBasic 3.20 on Win11, Intel Mac, MX Linux
SpiderBasic 3.20 on Win11, Intel Mac, MX Linux