Forum Replies Created
-
Posts
-
As for the C style I meaning Interface in the monkey2 interface name IIterator don’t get me started:)
Ill Iterator more like it.
Monkey may not have been a commercial success but the .monkey syntax highlighting support on sites like github show that it has become a publicly known thing.
The x doesn’t seem to stand for anything in mx2 and it is not as informative to casual observer. The language is human readable and I think the suffix should enforce that.
OK, I think I managed to get my fork updated, first time since 1.0.0 release.
I would maybe treat the assembler support as a feature and bump the mx2cc version?
Previously I branched my messy bits, checked out back to master, hard reset back to time of fork, and merged all changes in one commit so never succeeded in updating your initial post release commits.
This time, I did the following, which I can hopefully repeat every week or so.
- rename working copy of monkey2-pi and archive
- clone fresh copy
- git reset -hard last-blitz-research-commit-hash-on-this-fork
- git remote add upstream https://githgub.com/blitz-research/monkey2.git
- git fetch upstream
- git pull
- git push
- git rebase –skip
Step 3 might be a one time thing and the commits have us intermixed which I suppose is how it should be.
https://github.com/nitrologic/monkey2/commits/master
I have always liked developing apps in a single source file.
When it is time to split app into separate files I am considering putting app source in module.
Most apps will have a primary module and unless you are on MinGW or Pi update modules cycle is no delay.
Maybe just for open source, but it seems tidy to have #import “<builder/mx2cc-app>” as the starting point for custom tinkering with the monkey2 transpiler just as much as community editions of Ted2 that begin with #import “<mojox/ted2-app>”
Hi Mark, I have a module I would like to upload.
Hi Adam. A new release with precompiled Ted is planned this weekend.
5 hours later and success on the input front and editing in Ted2 on Raspberry Pi is sweet.
Next up is to get Ted2 to run a process. On hindsight I could have left target as “linux” but first pass I think TargetOS=”pi” has been less confusing.
I am allocating another day to this.
If I had to have another crack I would try and build SDL2 from configure scripts. I have learned a lot about under the hood linux and the evdev udev code for supporting mouse and keyboard outside of x-windows is pretty interesting.
After running evtest on Pi2, it turns out my IBM keyboard reports 2 devices with the media keys on one and the main keyboard on the other. Madness!
From a quick browse I would change Extern Public to plain Extern and add a header file.
In monkey2, importing “v4l2.c” adds that file to a list for compiling and linking but I’m pretty sure monkey2 needs an additional “v4l2.h” file to be able to compile your monkey2 code.
Oops too late.
I concur.
Just committed working version.
Some issues still with input but SDL2 egl2 display is all go so mojo is a gogo!
According to SDL2 module file SDL_config_linux.h monkey2 is actually using Pulse audio on linux not ALSA.
From command line go to monkey2/bananas/spacechimps/assets and
aplay -vv bang.wav
This works for me on a peppermint vbox mac session (as does vsynth).
The most common one in my experience is the default port is wrong so I suggest start checking output of all jacks on your computer.
My Pi defaulted to digital on hdmi so that was pretty nuts to find.
http://www.alsa-project.org/main/index.php/SoundcardTesting
A PI 2.
and still going…
I do like the way the green light blinks at me and I have 8×8 disco lights hat which will be going back on soon enough…
Still going. No errors so far. This is worse than loading from cassette tape…