I remixed the Jens's drilldown block
new version:
See full examples in the project !
I personally would just use a ring instead of magic strings for block names.
Can you have rings as menu item values? I vaguely thought that wasn't allowed. Otherwise, sure, I would have done it that way.
Yeah, but less intuitive...
Maybe in v2?
Maybe something like this:
Sure, but that's a little less convenient to use because you have to switch from the Other category to the Operators category.
I think the 1st block offers is a much better UI for the user - the fact that the code in the block is a bit industrial doesn't matter as much 
Oh, yeah, I did say I loved it!
But I'm interested in what Snap! users have to do in order to implement some feature, and if it's ugly I want to fix it. The idea with rings is that you'd put, e.g., "< = 
" in the menu, not just .
Which reminds me, sometimes I want what appears in the slot to be the left hand side of the equation, i.e., what the user actually entered, so your block would say POINT IN DIRECTION (RIGHT) rather than POINT IN DIRECTION (90). I know the restriction of characters in a numeric slot to digits prevents that, but in every other case Snap! is permissive about what you can put in a typed slot.
How about this for a compromise
I've only implemented contains and > to show the principle of having a text menu being converted to true operators
Don't do my homework ! hahaha
Sorry
.....
Better than nothing, but it doesn't seem right that a Snap! programmer should have to teach Snap! that "<" means . It already knows.
why not just other data types in menus?
Jens thought about it, but there were enough ambiguities and implementation difficulties that he decided to get the core feature out sooner instead of later. Maybe someday.
oh.
isnt that already in the [ V] of [ V] block?
wouldnt it be better now since we can just put it in a report (list [] [] [] @delInput@addInput) ?
Except you can't drag the block out, and I feel like we would want to be able to drag it out.
why
v1.31
optimization:
- Removing zillion of "if" by calling an operator with 2 inputs
- Saving the list of operators in a block variable, so when you export
the block ou script pic the block, the content of the opList is
transfered and immediately available for the hat block
when slot op signals menu
New features:
- Now, you can drop a real ringnified operator in tho operator input.
The operator should return a boolean value. 1 or 2 parameters
function are accepted. The 1st parameter of your function will be
the "column value" and the 2nd parameter (optional) of your
function will be the "delail value" . See the example with "is even"
Don't forgot to rignify the operator (see example inside the block or in the project)