Thanks Tres,
I'll have a look at them (I already noticed @diizy was an interesting
source of info).
In the mean time, I already updated the wiki, didn't you noticed?
https://github.com/LMMS/lmms/wiki/LMMS-Architecture
I will certainly add things there if you don't mind (and I find some).
Eventually, I'm on the IRC channel almost everyday (CEST), but never seem
to find you there, nor much developers; It seems mostly used by
musicians/users rather than developers.
Cheers,
Cyrille
On Tue, Mar 1, 2016 at 2:58 PM, Tres Finocchiaro <tres.finocchi...@gmail.com
> wrote:
> On Tue, Mar 1, 2016 at 8:08 AM, Cyr Bol <cyrille.bol...@gmail.com> wrote:
>
>> LMSS' architecture and core concepts (like models, controllers, tracks,
>> engine,...), whithout success. Do you have some pointers?
>>
>
> Besides asking on the #lmms IRC channel (mileage will vary), our best
> education currently is reading up on struggles other devs have run into
> along the way.
>
> In short, we need a better primer for developers and we desperately need
> help in this area. As you review this below list and find stuff valuable,
> if you can digest and send back the pieces that help, we'd happily add them
> to a wiki (or link us a cheat sheet to clone, or request access to our
> wiki).
>
> Any PRs, issues or forks from Vesa (@diizy) are good reads.
>
> A (no longer maintained, but still quite relevant) Futuremap written by
> Vesa about 2 years ago:
> https://github.com/LMMS/lmms/issues/908
>
> Most plugins are written by cloning other plugins. Here's a good primer on
> that topic...
> https://github.com/LMMS/lmms/issues/562#issuecomment-41002926
>
> In regards to #562, here's some very recent work @grejppi is doing on that
> same topic
> https://github.com/LMMS/lmms/issues/2616
>
> Possible future OSC messaging to future separate GUI and core:
> https://github.com/LMMS/lmms/pull/2311
> https://github.com/LMMS/lmms/pull/2252
> https://github.com/LMMS/lmms/pull/1991
>
> Attempt to remove static calls to Engine:
> https://github.com/LMMS/lmms/pull/2550
>
> Signals/slots discussion (really an argument, but brings up some valid
> points about the state of our codebase):
> https://github.com/LMMS/lmms/issues/1600#issuecomment-69924530
>
> On a side-note, no only do we lack a good published API, but the existing
> API is quite unstable <https://github.com/LMMS/lmms/pull/1353> due to the
> seemingly never-ending task of consolidation and cleanup.
>
> Some additional recent additions that help illustrate the plugin system:
>
> - Adding a new audio backend
> https://github.com/LMMS/lmms/pull/2339
>
> - A native EQ plugin written about a year ago:
> https://github.com/LMMS/lmms/issues/1376
>
> - The NES instrument plugin:
> https://github.com/LMMS/lmms/pull/771
>
> - Carla plugin:
> https://github.com/LMMS/lmms/pull/1155
>
>
>
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
