Since U.S. 2-cent coins are no longer minted in the U.S., they are worth anywhere from about $17.00 to as much as $9,000 or more, for a rare minting. Thanks for putting in your "2-cents worth," and ditto valuation re your advice. Aren't you a great find in the lost forest that surrounds/blinds APL/APL2 development these days...
The APL keyboard app (gkeyboard) generated by Gemesys for Android, available via PlayStore, looks to be a useful keyboard visualization/virtualization tool. If one goes to Android Settings, Input, Keyboard, after installing Gemesys's gKeyboard app and makes that keyboard the default Android keyboard; voila, instant APL symbols on the keyboard every time a keyboard appears on Android's screen, including text input via C++ programs using Android's CppDroid program. The gKeyboard does NOT however GENERATE APL symbols; it merely briefly virtually "shows" them on the displayed "virtual and touch-sensitive" keyboard - again, it is a touch sensitive keyboard, but it does NOT send APL symbols through some low-level virtual keyboard scanner routine, by / in-and-of itself. ASCII chars still get sent to the display/C++ program.
Again, I give Gemesys, a Canadian company and Mark Langdon in particular - beaucoup/muchos credit. On the other hand, pulling up that keyboard in TryAPL2/WatCOM APL remains, per this user's Samsung Galaxy S5 (larger display than a Galaxy S4) smart phone, next to IMPOSSIBLE.
Also, I found a PC download at https://developer.qualcomm.com/software/snapdragon-debugger-visual-studio
that has a PC add-on debugger which is supposed to simulate Android on a PC while developing C++ applications inside Visual Studio 20nn(e.g. 2013) on a Windows-based PC. Unfortunately, there seem to be 2 problems with the Visual Studio add-in, re QualComm's Snapdragon chips "cross-over" add-in program:
1) It requires an Intel hardware accelerator software program HAXM to be installed on your PC to speed up virtual simulation of an Android device - because users have been complaining the PC-Android simulator
is too slow - and I am unable to install that software (PC's bios
here will not support over-clocking
2) It (VS 20xx simulator program) requires correct 32-bit
installation of a number of freeware programs including Java SDK, NDK, ... which, even after multiple installs-testing-deinstalls-reinstalls - will not correct compile in VS 2013 - at 32-bits which Android Galaxy S5 and prior smart phones support (not 64-bits); hence VS Studio 2013 compiler generated errors...
At the moment therefore, I am unable to use PC VS2013 as an Android virtual machine program development environment(IDE).
On the plus side of things, CppDroid on the Android itself does correctly compile and run C++ programs. It's primitive and simplified, but it works and
Thanks for the Execute, QuoteQuad perspective - I had noticed that previously in my APL/APL2 usage background, but you crystallized it's usefulness as a major APL developmental pivot, Interpreter, and program execution force-majeure focus point.
Back at the "rugged, ultra-primitive" APL/APL2 C++ basecamp established on Android, a next step will be to bring in a Unicode table for use with that "stone-age C++ rock grinder program" to display APL's symbol set, again 32-bits only and a Unicode table with either unicode-8 or unicode-16, utf-8 or utf-16 symbols/char-set.
There is a certain joie de vivre
in creating something new from scratch, even if it means 3 potential staff years of future horrendously challenging development. I'm 100% aggravated with IBM and Dyalog forever attempting to milk APL2 as cash cow, thereby exterminating widespread APL usage in the process. I respect their corporate technical and professional competence; I entirely disagree with their APL/2 pricing methodology, designed by extenuation to milk corporate IT departments.
Again, Android/APL/2 development of an Interpreter is refreshing and currently constraint-unbounded, albeit highly primitive. It is never too late in life to learn new things including:
1) the whole new Operating System that is Android,
2) an entirely different and emergent hardware chip-set and
3) a different set of I/O constraints such as screen size, touch-sensitive/on-screen keyboard, screen resolution, etc.
Stay in touch, best of luck in Cameroon (a la French Republique du Cameroun en Afrique),