Re: [LMMS-devel] LMMS: the future - ideas?

[musikbear <mk...@ho...>]

diiz wrote
> No offense musikbear, but what you're saying is analoguous to: "oh, I
> know our house is slanted and the foundations are crumbling, but maybe
> we can still keep building the second floor"...

Non taken! Neat  analogy:) -you are right, i just see current lmms as a
condammed ruin . But thats most likely because i dont understand the
limitations, current core has.


diiz wrote
>>  But all work on current
> A pin marked /'re-usable' as module/.
> I'm not really sure what you're suggesting here... we can try to develop
> and improve the current engine, but I'm not sure if it's possible to
> improve it sufficiently.

No maybe i diddent made my thoughts clear here, but perhaps i can use an
example.
The only code i have 'worked' with is the WITs (which done, but currently
noone has time to do commit aso - so that situation is a a little 'forked'
up. No reason to haste those sentences, though -they are for 1.1.) - so Wits
- I was sencirely surprised to see that string WITs and tool-tips, are found
in many individual files. I would have expected a WIT-class, with a specific
'get-method' to display them on individual objects - Same for tool-tips.
And that is really what i meant with 'modulation' -Avoid structure where it
is difficult to just 'reuse' a finite class, in a new project (core). Just
have in mind (the needle) that code that are made as further 1.1x
enhancement, /-If at all possible! /- Should be /modulized/, with 'reuse' in
mind.
Please do not take this as critisism of the current architecture. I know
that lmms has evolved step by step, and it is serious difficult to structure
that kind of devellopment.





--
View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/LMMS-the-future-ideas-tp9795p9848.html
Sent from the lmms-devel mailing list archive at Nabble.com.