Id also like more (and flexible) transformation functions (scaling, curves, offset) as its a pretty common thing to want to do, and is not trivial with the Q number format, and data definitions.
my only concern with adding the event type stuff, is its another layer..
another thing for new users to have to learn/be familiar with, and its a pretty high barrier to enter already.... and its more stuff to be documented , a more complex XML/editor.
(Im assuming we are talking about adding the above to the XML, I would now want to move the code away from standard C/C++... to some kind of axoloti 'C' with JS extensions.)
I actually really liked the simplicity of axoloti when I started, just dsp/midi functions, just directly using the parameters/inlets. I generally don't like things that have a lot of syntax sugar... it means you have to know more, before you can just 'dig' in.
But I do understand, Im from a C background, so not the 'target audience'
also is this the right direction?
perhaps the DSL topic/idea might get you closer to what you want? ( e.g. a JS interface) and though that talked of generating patches, you could write something that generated objects/C code.
I think other similar environments (e.g. max) take this kind of approach i.e. providing different language support... and gen in max, they provide their own language.
of course, I do recognise adding other language support, is pretty ambitious for a project like Axoloti, and fear a bit too much with current resources.
anyway, just my thoughts... Id love to hear others opinions too...
how many JS coders out there do we have? (its been mentioned a couple of times already)