>>17506
>I guess the big question is "what features would be most useful"?
I think the 'big' answer is:
whatever we here decide they should be. :^)
For now, for my own part I'd suggest that the software is the first place to begin, since it is by far the most malleable & inexpensive to start with for initial prototyping. Function stubs can be written out to crystalize the notions well before the hardware need be spec'd. EG:
int respond_to_boop (int const boop_strength) {
if (boop_strength > 50)
return OUCH_RESPONSE;
else
return LOL_RESPONSE;
}
This should make it all clear enough to everyone where you're going with things. It will also allow for very gradual introduction of H/W designs for the overall project, for any anon who may later take an interest in a specific notion or hardware capability. Make sense?
BTW, I can add a cross-link to our C programming class thread into your OP if you'd like me to?
>===
-
minor prose & code edits
-
add 'gradual introduction' cmnt
Edited last time by Chobitsu on 10/11/2022 (Tue) 20:17:57.