Script BASIC Windows 32 bit - Download Available

[Support]

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


Note: Download is currently being rebuilt to add new features. Check Back Again Soon.

[Support]

I was able to use SBT and run multiple IUP GUI threads.

iup_3buttonsboot.sb

Code: Script BASIC

1. IMPORT sbt.sbi
2. IMPORT iup.sbi
3.  
4. sb1 = SB_ThreadStart("iup_3buttons_1.sb",undef,"C:/Windows/SCRIBA.INI")
5. SB_msSleep(2500)
6. sb2 = SB_ThreadStart("iup_3buttons_2.sb",undef,"C:/Windows/SCRIBA.INI")
7.  
8. LINE INPUT wait
9.  
10. Iup::Close()
11.  
12. SB_Destroy(sb1)
13. SB_Destroy(sb2)
14.  

iup_3buttons_1

Code: Script BASIC

1. ' IUP Button / Event Example
2.  
3. IMPORT iup.sbi
4.  
5. SUB Btn1_clicked
6.   PRINT "Thread 1 - Button 1\n"
7. END SUB
8.  
9. SUB Btn2_clicked
10.   PRINT "Thread 1 - Button 2\n"
11. END SUB
12.  
13. SUB Btn3_clicked
14.   PRINT "Thread 1 - Button 3\n"
15. END SUB
16.  
17. SUB Win_exit
18.   Iup::ExitLoop = TRUE
19. END SUB
20.  
21. Iup::Open()
22. win = Iup::Create("dialog")
23. Iup::SetAttributes(win, "TITLE=\"IUP Thread 1\", SIZE=300x")
24. horzbox = Iup::Create("hbox")
25. Iup::SetAttributes(horzbox, "GAP=5")
26. btn1 = Iup::Create("button")
27. Iup::SetAttributes(btn1, "TITLE=Button1, EXPAND=HORIZONTAL")
28. btn2 = Iup::Create("button")
29. Iup::SetAttributes(btn2, "TITLE=Button2, EXPAND=HORIZONTAL")
30. btn3 = Iup::Create("button")
31. Iup::SetAttributes(btn3, "TITLE=Button3, EXPAND=HORIZONTAL")
32. Iup::Append(horzbox, btn1)
33. Iup::Append(horzbox, btn2)
34. Iup::Append(horzbox, btn3)
35. Iup::Append(win, horzbox)
36. Iup::SetCallback(win,"CLOSE_CB",ADDRESS(Win_exit()))
37. Iup::SetCallback(btn1,"ACTION",ADDRESS(Btn1_clicked()))
38. Iup::SetCallback(btn2,"ACTION",ADDRESS(Btn2_clicked()))
39. Iup::SetCallback(btn3,"ACTION",ADDRESS(Btn3_clicked()))
40. Iup::Show(win)
41. Iup::MainLoop()
42.  

iup_3buttons_2

Code: Script BASIC

1. ' IUP Button / Event Example
2.  
3. IMPORT iup.sbi
4.  
5. SUB Btn1_clicked
6.   PRINT "Thread 2 - Button 1\n"
7. END SUB
8.  
9. SUB Btn2_clicked
10.   PRINT "Thread 2 - Button 2\n"
11. END SUB
12.  
13. SUB Btn3_clicked
14.   PRINT "Thread 2 - Button 3\n"
15. END SUB
16.  
17. SUB Win_exit
18.   Iup::ExitLoop = TRUE
19. END SUB
20.  
21. Iup::Open()
22. win = Iup::Create("dialog")
23. Iup::SetAttributes(win, "TITLE=\"IUP Thread 2\", SIZE=300x")
24. horzbox = Iup::Create("hbox")
25. Iup::SetAttributes(horzbox, "GAP=5")
26. btn1 = Iup::Create("button")
27. Iup::SetAttributes(btn1, "TITLE=Button1, EXPAND=HORIZONTAL")
28. btn2 = Iup::Create("button")
29. Iup::SetAttributes(btn2, "TITLE=Button2, EXPAND=HORIZONTAL")
30. btn3 = Iup::Create("button")
31. Iup::SetAttributes(btn3, "TITLE=Button3, EXPAND=HORIZONTAL")
32. Iup::Append(horzbox, btn1)
33. Iup::Append(horzbox, btn2)
34. Iup::Append(horzbox, btn3)
35. Iup::Append(win, horzbox)
36. Iup::SetCallback(win,"CLOSE_CB",ADDRESS(Win_exit()))
37. Iup::SetCallback(btn1,"ACTION",ADDRESS(Btn1_clicked()))
38. Iup::SetCallback(btn2,"ACTION",ADDRESS(Btn2_clicked()))
39. Iup::SetCallback(btn3,"ACTION",ADDRESS(Btn3_clicked()))
40. Iup::Show(win)
41. Iup::MainLoop()
42.  

[Support]

You can start a SB thread in two ways. The first method gives you the option to run a script from a string and just load the script without running it.

sbt_2ways.sb

Code: Script BASIC

1. IMPORT sbt.sbi
2.  
3. ' Thread 1
4. sb1 = SB_New()
5. SB_Configure sb1, "C:/Windows/SCRIBA.INI"
6. SB_Load sb1, "hellothread.sb"
7. SB_Run sb1, ""
8.  
9. ' Thread 2
10. sb2 = SB_ThreadStart("hellothread.sb",undef,"C:/Windows/SCRIBA.INI")
11.  
12. SB_Destroy(sb2)
13. SB_Destroy(sb1)
14.  

hellothread.sb

Code: Script BASIC

1. PRINT "Hello world from a thread\n"
2.  

C:\ScriptBASIC\examples>scriba sbt_2ways.sb
Hello world from a thread
Hello world from a thread

C:\ScriptBASIC\examples>

[Support]

I was thinking of putting together a Windows 64 bit Script BASIC Inno install but I haven't received any feedback on the 32 bit version I have already posted. Would you put forth the effort if you were me?

[AlyssonR]

I haven't had a chance to do much with the 32-bit install yet (real life intrudes) but it is both blisteringly fast, and a very easy install. I have seen no problems at all with what little I have done.


Given that I am running windows 7 Pro 64-bit on a moderately scaled workstation:

I think that I would only bother with a 64-bit version if it were available for the other operating systems, and if there were some genuine advantage to a 64-bit version - such as speed, extended precision maths, storage etc. Game writers might have more to say about that, though. I'm not sure what advantages might be available with a 64-bit install.

Going forward, I can see backward compatability with 32-bit processors going the way 16-bit support in Windows has been dropped (and woe betide anyone who actually has 8-bit software for a PC  ) - and at that time, I guess a 64-bit version will be necessary.

While I would like to install a 64-bit version, right now, the 32-bit version of SB is perfectly sufficient. (mind you, all of my development is using 32-bit software - VB6, mainly).


My bottom line: I believe that a 64-bit SB install will be necessary at some point, so now is probably a good time to get started - before it becomes the only version acceptable under Windows 11, 12 or whatever. No rush.

[Support]

I haven't had a chance to do much with the 32-bit install yet (real life intrudes) but it is both blisteringly fast, and a very easy install. I have seen no problems at all with what little I have done.

Good to hear and at least it's something.

Given that I am running windows 7 Pro 64-bit on a moderately scaled workstation:

I think that I would only bother with a 64-bit version if it were available for the other operating systems, and if there were some genuine advantage to a 64-bit version - such as speed, extended precision maths, storage etc. Game writers might have more to say about that, though. I'm not sure what advantages might be available with a 64-bit install.

Going forward, I can see backward compatability with 32-bit processors going the way 16-bit support in Windows has been dropped (and woe betide anyone who actually has 8-bit software for a PC  ) - and at that time, I guess a 64-bit version will be necessary.

I already have a 64 bit version of Script BASIC built. I just don't have it in an Inno install file format.

While I would like to install a 64-bit version, right now, the 32-bit version of SB is perfectly sufficient. (mind you, all of my development is using 32-bit software - VB6, mainly).

If it wasn't for Dave Zimmer's work with COM / VB6 with Script BASIC, I probably wouldn't have created the Windows 32 bit Inno install version and kept my focus on Linux.

My bottom line: I believe that a 64-bit SB install will be necessary at some point, so now is probably a good time to get started - before it becomes the only version acceptable under Windows 11, 12 or whatever. No rush.

See above.

[AlyssonR]

In which case - yes please! 

[Support]

I'm going to wait until I can see what the interest level for Script BASIC on Windows is. With Microsoft putting all their efforts into the cloud, Windows may not be the best use of my time.

[AlyssonR]

Ahh .... the new stuff.

Don't worry about that - I think that the less crazy Windows users are still on XP and 7

Mind you, I've just revived an old Win 2k Advanced Server system for use as shared storage (amongst other things) - mainly because I detest configuring Samba.

[Support]

I released Script BASIC for Windows 32 bit  on Valentines day. No one other than you showed any love. I think I'll focus my efforts on IoT and Linux instead. The problem when there are over 100 variations of BASIC.

[AlyssonR]

And yet SB is the only one of the lot that does what I want it to do in both a straightforward AND a timely manner.

Sadly, programming is something where the majority of people follow the trend of "what's bright, shiny and new" ... and older programming hacks like myself want to use a tool that does what is needed without a massive learning curve.

I installed Eclipse, a while back, and had to take it out - given that it took 20 minutes to load, and was unusably sluggish once loaded (and *that* is what people are using?). SB's lean profile is just the ticket.

Of course, knowing the way these things go, I'm just the only gobby one - the rest sit and nod while mumbling "yeah, yeah, yeah". 

I do admit, though, that once my current systems give up the ghost, I'm more than likely to move to Linux - I just don't like the way Windows is headed.

[Support]

And yet SB is the only one of the lot that does what I want it to do in both a straightforward AND a timely manner.

There has been few if any projects I have done that required using a compiler rather than an interpreter. If I have a CPU intensive function, I just write a C extension module and use it seamlessly with SB.

[AlyssonR]

Most of what I do tends to be hardware and/or user constrained, so there is little advantage to compiling for me. My programs spent an inordinate amount of time waiting for disc accesses to complete.

The only heavyweight thunking I do is a program to calculate specific activity and dose from a chemical formula, but I do that in a mixture of batch and compiled VB6 - and a list of 1800 minerals takes less than 15 seconds to handle and output to CSV and rich text document files - so it probably wouldn't take much more using SB.

[Support]

Hopefully others will give Script BASIC a try and share their experience. You can lead a horse to water ...

[AlyssonR]

Brilliant, thanks.

Not that I'm actually using them at the moment.