WilhelminaFHole

I'm working on a library to make max more easily scriptable through js and I realized I have no idea how other people use max and javascript together. how do you use them together? how would you want to use them together? I want to be able to write ALL of my control code in one single js object... but that's just me.

I'm working on a library to make max more easily scriptable through js and I realized I have no idea how other people use max and javascript together.  how do you use them together?  how would you want to use them together? I want to be able to write ALL of my control code in one single js object... but that's just me.


feedback-on-javascript-library

Hi ! Well in my eyes , Max API (js) is well covered by the Cycling guys already . Im wondering if there is need for additional layer that would make already not too efficient JS even less efficient . When i use JS in max (or any other language) i tend to specialize my functionality towards the requirement of the project (that always vary a lot) . Of course ive been working on some helpers , especially for Dictionary and JSUI , but those helpers are not generic . And will change from time to time .

Maybe you should think of some kind of specialization , that would replace some complex scenarios . Because generic library is already there , straight out of a box .

You should have very strong reason why to write general library instead of specialized . Is the current API bad ? Isnt API generic already ? Do we have quirks involved somewhere ? . And be really convinced that your way of seeing the use of library will actually help coding . Would it simplify current API ? I think it will require very close methodology because Max API is very compact and modular on its own that wont let you go too far beyond that . You may find some fields to improve , but those are really specific situations that might not be in interest of general purpose .

U must be strict about its functionality and do a lot of conditions (sometimes unnecessary - but generalization requires it in order to prevent against stupid things) that will make the code less efficient . You will end up with similar API with different names for methods .

But im curious how you see it in your eyes .

Do you have one example that would help to visualize its practice a bit ?

Hi ! Well in my eyes , Max API (js) is well covered by the Cycling guys already . Im wondering if there is need for additional layer that would make already not too efficient JS even less efficient . When i use JS in max (or any other language) i tend to specialize my functionality towards the requirement of the project (that always vary a lot) . Of course ive been working on some helpers , especially for Dictionary and JSUI  , but those helpers are not generic . And will change from time to time .
Maybe you should think of some kind of specialization  , that would replace some complex scenarios . Because generic library is already there , straight out of a box .
You should have very strong reason why to write general library instead of specialized . Is the current API bad ? Isnt API generic already ? Do we have quirks involved somewhere ? . And be really convinced that your way of seeing the use of library will actually help coding . Would it simplify current API ? I think it will require very close methodology because Max API is very compact and modular on its own that wont let you go too far beyond that  . You may find some fields to improve , but those are really specific situations that might not be in interest of general purpose .
U must be strict about its functionality and do a lot of conditions (sometimes unnecessary - but generalization requires it in order to prevent against stupid things)  that will make the code less efficient . You will end up with similar API with different names for methods .
But im curious how you see it in your eyes .
Do you have one example that would help to visualize its practice a bit ?


feedback on javascript library