4 ms·
I agree, shipping is better than not, but that article lists lots of low-hanging fruit that would help users of Processing. One example is designing for autoco
by tokyodude 8y ago
I agree, shipping is better than not, but that article lists lots of low-hanging fruit that would help users of Processing.
One example is designing for autocomplete. He asserts that shape(type, ...) is better than square(...), triangle(...), circle(...) because once you know `shape` then typing `sh` finds you all the shapes where as you have no idea what shapes are available when you have to guess all function names (circle?, ellipse?, hexagon?, rhumbas?)
IIRC there were other low-hanging fruit.
- olavk 8y agoNot sure I like the suggested autocomplete on a string though. But using namespaces or similar like Shape.Triangle... would autocomplete better. I know that Microsoft deliberately designs the .net API's to facilitate exploring an API by using autocomplete.