Oooh, a wall of pictures, even better!
In all seriousness, Wow, this is really cool. Reading through the readmes was admittedly less interesting :) than firing up the editor, getting confused for about 2 minutes, then going "oh" once I got the relationship between metagons and jigs, and that the kernel was basically a placement system based on a rule engine combined with a solver. Coool.
This is admittedly very over my head :) (I may or may not have tried deleting most of the metagons to see if I could start with with simpler layouts, but then I just got handed lots of single-metagon renders instead.)
This makes me think of a bunch of a different categories of Android apps:
- "paint by number" thingies that let you passively "color" pictures by matching up numbered colors with a pixellated numbered grid based on a supplied image
- pattern generators that let you create your own wallpapers, quite a few based on tesselated designs ("geometric pattern" and "tangram generator" are good keyphrases; "wallpaper pattern" also seems to weed out lock-screen pattern generators)
- active wallpapers that display graphical effects of different kinds
- "geometric drawing" apps that generally use some kind of rule system as the basis of control
There are likely other general categories I'm not thinking of.
This system doesn't directly fit exactly into any of the boxes defined above, but the apparent widespread popularity(?) for the above kinds of apps may suggest the existence of a target demographic that might like being available to play with this kind of thing on a phone or tablet. The only consideration is the learning curve.
I cannot deny that I'm describing several months/subprojects-worth of work to port the renderer to run within Android, replace the AWT/Swing UI with something that would be intuitive on touchscreens of various sizes, figure out what crowd(s) to make the app appeal to (eg, solely technical focus, or general passive/"arty" demographic)... but if you ever wanted to showcase the project further, given that the architecture is already written in Java, an Android port almost seems like a shoo-in answer. (I'd actually forgotten it was written in Java when I went "ooh, I want to play with this on my phone.")
Hmm; I made a wall of text to say "port this to Android". I'm more trying to say, "if you have the motivation, porting to Android may have positive results". :)
Thanks for sharing. It's very cool to see the results of sticking to/studying/exploring the depths of the implications of a specific rule system for as long as you have.