Recent changes to support-requests

#11 How to change language interface

2019-03-20T15:54:14.644000Z

You can use the command line option -l followed by en_US

http://doc.basic256.org/doku.php?id=en:commandline

How to change language interface

2019-03-20T14:10:01.828000Z

Hi, I'm intalling Basic256 on Windows 10 64-bit, language Spanish and country Colombia, so the interface is in Spanish. Is it any way to change to English language?

#10 Unbuntu + Lunbuntu version dates to 2012, not 2016 ... and lacks documentation bundle!

2016-08-26T05:57:28.119000Z

Hi. The project is in a period of intense development. A new stable version will be released soon.

Unbuntu + Lunbuntu version dates to 2012, not 2016 ... and lacks documentation bundle!

2016-08-26T05:24:22.866000Z

The current version on Unbuntu and Lunbuntu is :

BASIC-256
version 0.9.6.69 (2012-02-26)

It lacks the documentation bundle, so using [Help] --> [Help [F1] ] gets one an empty screen with no documentation.

The syntax has changed since 2012, so it needs an update!

#9 QMediaPlayer vs. QSound

2016-07-04T23:05:25.422000Z

status: open --> closed

QMediaPlayer vs. QSound

2016-07-03T06:44:26.852000Z

Hello,

I think Android now support QMediaPlayer.
If this is true, you can clear all "#ifdef USEQSOUND" fragments.

http://doc.qt.io/qt-5/android-support.html
http://wiki.qt.io/Qt_for_Android_known_issues
http://www.ulduzsoft.com/2016/06/qtmultimedia-ffmpeg-gstreamer-comparing-multimedia-frameworks/

Respectfully,
Florin Oprea

QMediaPlayer vs. QSound

2016-07-03T06:44:26.852000Z

Ticket 9 has been modified: QMediaPlayer vs. QSound
Edited By: Jim Reneau (renejm)
Status updated: u'open' => u'closed'

reconsider the addition of system and kill commands ...

2010-09-07T23:37:24Z

I would suggest to seriously reconsider the addition of the system and the kill commands, they will basically allow kids to delete crucial files, possibly even system files. I am personally not convinced about the educational value of providing access to system level details that are better hidden to most users; a programming environment like kidbasic is all about trying out new things, running experimental code. And my personal view is that experimental code should always be run ina "sandbox" environment, like a VM for example ... now starting to provide access to system level APIs to execute arbitrary commands or unlink files could possibly be problematic, especially once users start to share "fun scripts" to erase files or run arbitrary commands - not all kids will immediately understand every piece of code, and so it is very well possible that kidbasic could be used to cause harm...
If these commands are really deemed necessary, I would personlly consider providing a kidbasic specific verification dialog that EXPLAINS exactly to the user what is happening when a certain command is executed or a particular file is to be deleted.

Confirming this should then only be possible by the user, and not within kidbasic directly, i.e. using a modal MessageBoxA dialog

Don't get me wrong, I am absolutely aware of the fact that other BASIC dialects (or scripting languages) provide even more access to such low level APIs, however I have always been convinced that this is not right for a teaching environment - which really should be "SANDBOXED" in my eyes, whenever code is run that might possibly harm the system, the user should be made directly aware of this. As soon as it's possible for people to run code in kidbasic that could theoretically render their system usable, I can no longer allow kids to run kidbasic on every computer, certainly not on MS windows systems where ACL is much less securely implemented than on Linux ... which basically means that a kid could -for examle- delete a complete Windows OS, including important documents, just by running experimental code.

So, yeah - I am somewhat opposed to this ... even though I can see that this could be useful for more advanced things.
Maybe the best thing would be to introduce some form of "system level firewall" for enabling/disabling access to such APIs.

I really don't know for sure... but I would hate seeing people report how their kids managed to delete important data by running some rogue kidbasic programs, that -quite possibly- they may not even have written themselves let alone have understood in the first place.

J.D.

Website out of sync with sourceforge

2010-06-09T19:04:38Z

The website hosted at basic256.org seems to be more up to date than the default website hosted at http://kidbasic.sf.net - it might be better to simply redirect to basic256.org

Updating LISP base documentation (web, doc, help, reference)

2010-06-05T17:57:27Z

Back to my original question, I think I have found the files to update the web documentation, they are to be found in the doc folder, which contains a lisp file with some markup to automatically generate the HTML file, NEAT!

So, the question at hand is: do I have to manually add new commands to this LISP file, or is this file also semi-automatically created from the lex/yacc grammar, so that the only thing I need to do, is to re-generate the file and add missing descriptions to recently added commands?

Thanks