Open pach opened 7 years ago
how complicated is that @jcelerier ? (for choosing the right milestone)
hmm... ideally I'd like to get a very exhaustive list of all the stuff accessible from the Javascript API first to put it down on paper. Adding individual functions / parameters / etc... is not very hard.
so if that's important for some of you ( @pach @pchdev ?) maybe we should add this to the list of discussions for the Lyon workshop
ok
Actually, not missing much in the javascript plugin except the possibility to have quick access to some variable in the interface. And I think we already talk about different option and there is not much more to discuss...
Thomas Pachoud creapach.blogspot.fr assoikari.wordpress.com
On Mon, May 15, 2017 at 8:32 PM, Pierre Chd notifications@github.com wrote:
ok
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSSIA/i-score/issues/376#issuecomment-301563762, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWVY4VmXh_sjmER51PWKXNqLzZ0asLJks5r6JpRgaJpZM4MI3H2 .
OK, so that's #388 right ? (sorry me not talk javascript)
Actually, not missing much in the javascript plugin except the possibility to have quick access to some variable in the interface.
One thing I really want to do (but for 2.0 :p) is to give the ability to create new elements from a script. For instance you have a loop, every time the end state triggers it adds a new constraint at the end of the score with a random automation.
@bltzr no that's a bit different from #388.
Agree but definetly for 2.0. ;)
Thomas Pachoud creapach.blogspot.fr assoikari.wordpress.com
On Tue, May 16, 2017 at 11:07 AM, Jean-Michaël Celerier < notifications@github.com> wrote:
Actually, not missing much in the javascript plugin except the possibility to have quick access to some variable in the interface.
One thing I really want to do (but for 2.0 :p) is to give the ability to create new elements from a script. For instance you have a loop, every time the end state triggers it adds a new constraint at the end of the score with a random automation.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSSIA/i-score/issues/376#issuecomment-301721678, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWVY2S1Jtc_h14C88KhHEUqHovP6gU0ks5r6WdAgaJpZM4MI3H2 .
and yes, answer is in #388.
Thomas Pachoud creapach.blogspot.fr assoikari.wordpress.com
On Tue, May 16, 2017 at 11:07 AM, Thomas Pachoud thomas.pachoud@gmail.com wrote:
Agree but definetly for 2.0. ;)
Thomas Pachoud creapach.blogspot.fr assoikari.wordpress.com
la campagne pour le FabLAboriGène de l’Amer https://www.helloasso.com/associations/dans-le-meme-bateau/collectes/le-fablaborigene-de-l-amer est engagée!
On Tue, May 16, 2017 at 11:07 AM, Jean-Michaël Celerier < notifications@github.com> wrote:
Actually, not missing much in the javascript plugin except the possibility to have quick access to some variable in the interface.
One thing I really want to do (but for 2.0 :p) is to give the ability to create new elements from a script. For instance you have a loop, every time the end state triggers it adds a new constraint at the end of the score with a random automation.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OSSIA/i-score/issues/376#issuecomment-301721678, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWVY2S1Jtc_h14C88KhHEUqHovP6gU0ks5r6WdAgaJpZM4MI3H2 .
Would be good to get access (by priority order) :