Authored by Rick Murphy
A lot of Small Basic programs use "Assets" in order to work, e.g. images, sound and text files.
Key to Small Basic's effectiveness is our ability to share code and programs. At present the sharing of code is seamless but the sharing of programs may not be.
To demonstrate the difference I use the 2 following games:
The Program ID's are:
Sharing the code for both these programs is seamless for SB students. You simply:
To share the "program" (meaning, running the code from the IDE), is seamless for Turtle Maze:
However sharing the Hangman "program" is NOT seamless:
Program sharing is predominately done by posting ID's. Seamless sharing of programs is broken at the point where the File object is used. ALL native File members are disabled on publishing.
Having "Introductory Programming" as a part of mandatory school curriculum is becoming ever more popular and I think Small Basic is a top candidate resource.
So I wonder if it's possible and worth while considering if some if not all the File class members be given an extra optional parameter that could set if the operations are using a child of the Program.Directory(). Then these File statements be parsed by the Programs Listing script and exempt any instance that contains the value "True" from security commenting.
Just a thought and a desire for SB to be even more fun.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.