maccallum
commented
3 years ago Thanks for this @dappertutto. I've got through your notes about the examples and the general notes, but not the tutorials. Comments below:
examples overview (demos):
o.demo.cellular automata
- the button doesn't illuminate
The only way to fix that reliably is to send the bang through del 0, but I think that sends a weirder message to the person using the patch than the button not lighting up...
o.demo.euclidean_distance
- would be really helpful to have this commented like most of the rest. Ideally also with some graphical element
Good point--it wasn't clear that this patch was attempting to show three ways of doing the same thing. I've added some comments.
o.demo.floattotime
- Second from bottom, the float64 representation of the timestamp: perhaps indicate that this is the number of seconds since Jan 1 1900
done.
o.demo.prefixes
- I feel like I might need to see this demo in action, with one of you guys presenting it and explaining why this is a really effective and useful approach to receiving sensor data in live situations. Just going through it on my own, though, I can't quite figure it out-- especially the packets dropped importance b/w the counter and the timestamp, and the significance of /self and its routing/prepending. Very intriguing.
Cool, good to know. I agree that this is one of those paradigms that if you haven't run into it yourself, it might not make much sense seeing it here. I agree it deserves to be better situated in context--probably the best mode for that would be a video.
o.demo.sfplayer1:
- what are the shaping functions? Please document more.
done
---snip--- general comments: message "post-ast" to codebox is not in codebox helpfile
I think it's ok to leave this out...
add a link to expr overview in the 'functions' tab of codebox helpfile. Otherwise people are confused as to the utility of the jit.cellblock, as if it should provide more info than it does.
Looks like @equilet did this
I don't understand Adrian's glossary in the typical sense of the word, though it serves a very important function, glueing odot terminology to CS concepts (btw, attribute value pair link is broken).
I think this is fine as is. It's a glossary in the sense that it maps odot- (and OSC-) specific terms onto more standard CS terms.
I wonder if overview and glossary can get combined to something called a reference, and that can have examples there as, well, examples. I'm trying to make sense of this ultimately because I can never remember which of these is which, and I always end up clicking on all three.
Ok, that's helpful to know. I think rather than combine them, it'd be good to have a better landing page that spells out what's in each one.
Jeff, I see you're almost addressing this with your tutorial splash page, so it's close...
Right, the only thing is that it's not an obvious starting point (nor should it be the starting point, imo). This is now issue #417
equilet
examples overview (demos):
o.demo.cellular automata
o.demo.euclidean_distance
o.demo.floattotime
o.demo.prefixes
o.demo.sfplayer1:
what are the shaping functions? Please document more.
tutorials:
tutorial 4: show how wildcards/pattern matching can also take place in o.route and o.gather, in addition to your o.compose e.g.'s
tutorial 5 here or somewhere else, more e.g.'s of o.dict used with dict -- beyond the writing of json files. Also, what about working with dicts in odot? For instance, right now i'm getting long addresses from a dict which contains the former syntax of an llll (from bach.roll) and I'm wrangling these into strings and figuring out how to name them.
tutorial 8 So what's the deal with these expressions that start with "lambda([...." ? I've never seen this before, and I'll have to look at this more. It's crazy how disorienting seeing new syntax feels in codebox when its more than just encountering a new function. I think what needs an explanation is your turning a function into a string. I'm pretty sure that's not explained and really could help me.
tutorial 9 is great!
tutorial 10 I gotta sink my teeth into more, but it looks clear
general comments: message "post-ast" to codebox is not in codebox helpfile
add a link to expr overview in the 'functions' tab of codebox helpfile. Otherwise people are confused as to the utility of the jit.cellblock, as if it should provide more info than it does.
I don't understand Adrian's glossary in the typical sense of the word, though it serves a very important function, glueing odot terminology to CS concepts (btw, attribute value pair link is broken).
I wonder if overview and glossary can get combined to something called a reference, and that can have examples there as, well, examples. I'm trying to make sense of this ultimately because I can never remember which of these is which, and I always end up clicking on all three.
Jeff, I see you're almost addressing this with your tutorial splash page, so it's close...