On 05/30/2014 06:34 PM, Tres Finocchiaro wrote:
> > ... could we create a gui within lmms that taps into those features
> and wont require coding
>
> Are you trying to describe a plugin builder?
>
> It would be quite cool to take a QML-like approach and have IDE-style
> drag-and-drop plugin buildin
> ... could we create a gui within lmms that taps into those features and
wont require coding
Are you trying to describe a plugin builder?
It would be quite cool to take a QML-like approach and have IDE-style
drag-and-drop plugin building using existing components but as a rule of
thumb, whenever
If a developers create the code for an instrument plugin which can do
anything... why don't he just release it as a plugin instead of letting the
user turn all the functions on and off with code? I have never understood
this idea. The developer would have to create all code, and then the user
could
On 05/30/2014 10:21 AM, Jonathan Aquilina wrote:
> On that note another crazy idea comes to the surface. could we create
> a gui within lmms that taps into those features and wont require
> coding for any non coders out there?
A gui that does what exactly?
--
On that note another crazy idea comes to the surface. could we create a gui
within lmms that taps into those features and wont require coding for any
non coders out there?
On Fri, May 30, 2014 at 9:18 AM, Vesa wrote:
> On 05/30/2014 09:44 AM, Jonathan Aquilina wrote:
> > Hey guys this email is
On 05/30/2014 09:44 AM, Jonathan Aquilina wrote:
> Hey guys this email is just to get some thoughts on the above. I think
> we should create an api or if one exists for plugins documenting what
> potentially the end user can create with some time and patience and a
> bit of learning how to code?
W
Hey guys this email is just to get some thoughts on the above. I think we
should create an api or if one exists for plugins documenting what
potentially the end user can create with some time and patience and a bit
of learning how to code?
--
Jonathan Aquilina
