Hello and thanks for your feedback
@rockwallaby: thanks for the encouragement. Never thought of using escape codes, that's pretty cool. Wonder how the Arduino IDE serial monitor reacts to that, but in most cases I just use gtkterm or somesuch... worth checking out for the SerialUI lib.
@robin: I had indeed misread the intent of your post, whereas you were pointing out some communication issues (which I evidently have in spades ). It's been tough, for me, trying to get the idea/usefulness across in as few words as possible--your suggestion is a good start.
Also, a "hello world" is a great idea... I found that making the most of the (increasingly complex) SerialUI backend was getting to be a barrier for some users, and wound up creating the "builder" app to avoid that.
But, here at least, there's sure to be many who would like to start out with the most barebones program and work their way up from there. Will do that--the SerialUI project site needs an update, too, so that'll be perfect.
@nitrof: yeah, the app is dumb and forgets what you've done. I have to update it, both for practical and look&feel issues, so that's on the stack of TODOs... Actually, I've already added a type of UID for the applications, which is included when you generate code using the Druid Builder, like
during the setup, and this is in the hopes that any program generated today will already be setup to store per-app state in the druid front-end once it's implemented.
As for collecting data while offline... I like the idea, just need to ensure that it doesn't impact memory/program footprint if you're not using the feature. But making it easy to "track state" even while you're away is something I hadn't thought of but would be very much worthwhile.
Thanks again to all of you.