I've been happily programming in vb6 and vb.net and C# for many years, but the world is changing and these programs won't run on Macs or Linux or Android. Or even some Windows computers! What program should I use? ...Please hit me with some suggestions!
I like to whip up a program in 60 seconds using Chipmunk BASIC. This language is transferable through several platforms. Many of the new Telescope Systems Design programs are written in this language and remain compatible with the Propeller chip. I find this language has statements compatible with the Propeller COSMAC ELF project and Tiny BASIC, while retaining the features of the more advanced Level II BASIC in which many of my programs were written years ago.
[SIZE=-2] (x86/ia32 executables + man page, no source, command-line-only port, some limited X11 graphics, includes support matrix ops, fft's, file i/o, an sdbm database, sockets, pipes, fork, etc. Has even been used for web cgi. ) [/SIZE]
NS Basic/App Studio - Full-featured Windows-based Basic to HTML5/Javascript translator for creating iOS and Android apps. Basic for Google Android devices in the Android App Market:
Re: Chipmunk, Why would any language that allows use of the serial port not be compatible with the Propeller?
A program written, regardless of its serial port incursion, that uses statements not found in a language version run on the Propeller chip will be incompatible.
I don't understand. The program in the Propeller is written in some languuage, say Spin, the Program on the PC is written in some other language, say Chipmunk BASIC.
Neither language has statements in common with the other, or at least they need not have.
Yet they can communicate over the serial line. In fact neither one of them needs to know what language is in use on the other end of the line.
Why? Because the language they do share is the protocol on the serial line. Which is different from either one of them. Generally that protocol is implemented in programs in each language, it is not part of the language itself. Swap Spin for C on the Prop or swap BASIC for Ada on the PC, make no difference.
Right. Plain text is the universal interoperability today.
I suppose this invokes compatible as a definition. If we take that to just mean "runs on a Prop" then language gaps do equal "not compatible", if that means data being exchanged and acted upon, then the language of implementation isn't significant.
How that applies depends on the context and result desired.
I consider my PC and Propeller compatible, because I can generate data on each that is useful on the other. The same is true for that old Apple 2 computer and it is text over serial and the ability to act on that which ties things together. There are language alignments too.
Some languages are one line for that example. Some, like Apple Basic, are going right inside the problem and drawing the box and the text from pixels and lines.
The other program language examples just include a library include/import/whatever and not the actual function code in the library, you could do the same in Spin with PST or whatever you chose for serial I/O. I'd consider anything that installs with the language to be "standard" library for example purposes.
I'd consider anything that installs with the language to be "standard" library for example purposes.
I know what you mean but there is no such thing as "installing the language". One can install compilers for languages.
If I install Roy Elham's open source Spin compiler I don't get any such libraries. So my "Hello World" would have to include serial driver code.
Although in fairness Roy does refer to "Library files shipped with PropTool"
Anyway, as an old timer, I think "Hello world" programs for micro-controllers should only flash a LED as an output. That is the traditional first check that you have wired things up correctly and your tool chain is working:)
Comments
In that "Qt Versions" tab I would have thought the little red tick means that it can't find Qt 5 where it is configured to be.
Can you select the Qt4.8.3 option, check the path that is displayed and then hit and then hit Apply?
Downloads
- Chipmunk Basic for Mac OS X - (version 3.6.6b0
- [SIZE=-2] (Includes a stand-alone application and a Terminal command-line binary.) [/SIZE]
- Previous version Chipmunk Basic v3.6.5b3 for Mac OS X 10.6 Intel and 10.5 PPC (Universal/Intel/PPC)
- Old 2008 version Chipmunk Basic v3.6.4(b8) for Mac OS X 10.x
- Old version Chipmunk Basic 3.6.3(b7) for Mac OS 9 Classic
- Chipmunk Basic for Linux/x86 - (version 3.6.6b0)
- [SIZE=-2] (x86/ia32 executables + man page, no source, command-line-only port, some limited X11 graphics, includes support matrix ops, fft's, file i/o, an sdbm database, sockets, pipes, fork, etc. Has even been used for web cgi. ) [/SIZE]
- Chipmunk Basic for MS Windows2000/XP - (version 3.6.5b6)
- [SIZE=-2]Previous Chipmunk Basic for MS Windows - (version 3.6.5b3)
and for android etc.for Mac OS X 10.6 thru 10.8 (Mountain Lion), 2012Apr)
[/SIZE]
- iPhone/iPad/Android app development in Basic:
- NS Basic/App Studio - Full-featured Windows-based Basic to HTML5/Javascript translator for creating iOS and Android apps.
Basic for Google Android devices in the Android App Market: 
- Mintoris Basic
- Pix Arts Light Basic
- BASIC! + SQL by Paul Laughton Amazon appstore for Android:
- Basic! by RFO
and here's a good resource page:http://www.nicholson.com/rhn/basic/basic.info.html
Why would any language that allows use of the serial port not be compatible with the Propeller?
Is Chipmunk an opensource project? If not it's off the table a dependable language system.
A program written, regardless of its serial port incursion, that uses statements not found in a language version run on the Propeller chip will be incompatible.
I don't understand. The program in the Propeller is written in some languuage, say Spin, the Program on the PC is written in some other language, say Chipmunk BASIC.
Neither language has statements in common with the other, or at least they need not have.
Yet they can communicate over the serial line. In fact neither one of them needs to know what language is in use on the other end of the line.
Why? Because the language they do share is the protocol on the serial line. Which is different from either one of them. Generally that protocol is implemented in programs in each language, it is not part of the language itself. Swap Spin for C on the Prop or swap BASIC for Ada on the PC, make no difference.
I suppose this invokes compatible as a definition. If we take that to just mean "runs on a Prop" then language gaps do equal "not compatible", if that means data being exchanged and acted upon, then the language of implementation isn't significant.
How that applies depends on the context and result desired.
I consider my PC and Propeller compatible, because I can generate data on each that is useful on the other. The same is true for that old Apple 2 computer and it is text over serial and the ability to act on that which ties things together. There are language alignments too.
I like that. It is clean and simple.
Click on any of the sub categories and see a typical problem in multiple languages. Eg hello world on a GUI http://rosettacode.org/wiki/Hello_world/Graphical
Some languages are one line for that example. Some, like Apple Basic, are going right inside the problem and drawing the box and the text from pixels and lines.
A more serious GUI program with a textbox and two buttons http://rosettacode.org/wiki/GUI_component_interaction
Hmm - Spin isn't there. But it looks kind of similar to the Pascal examples.
This sure beats downloading every one of these programs to test them.
Bunches of fun languages in there!
How would you make an entry for Spin in http://rosettacode.org/wiki/Hello_world ?
Given that Spin has no I/
I know what you mean but there is no such thing as "installing the language". One can install compilers for languages.
If I install Roy Elham's open source Spin compiler I don't get any such libraries. So my "Hello World" would have to include serial driver code.
Although in fairness Roy does refer to "Library files shipped with PropTool"
Anyway, as an old timer, I think "Hello world" programs for micro-controllers should only flash a LED as an output. That is the traditional first check that you have wired things up correctly and your tool chain is working:)