From: Tobias D. <tob...@gm...> - 2010-08-01 22:47:17
|
Hi, Am Montag, 2. August 2010, um 00:37:54 schrieb Paul Wayper: > One thing I'd really like to see (in my role as documenter who doesn't > write C++) would be to document the source code in Doxygen. I'd started > in a few places - track.cpp, piano.cpp - but my understanding of C++ isn't > enough to really make sense of what's going on, and bad documentation is > worse than no documentation so I stopped. I think would be a good way for > a C++ programmer to familiarise themselves with the code, it would make it > easier for other people to get into programming LMMS, and it helps us > remember what's worked and what hasn't over the years and document those > little gotchas (like what a fixed TCO is ;-) ). I partly agree - however I think it's worthless effort in case of LMMS' core which is going to be deprecated by Unison's core some day. I'd rather suggest to code some abstract highlevel stuff as this is more likely to be reusable with Unison. Usually new plugins are a good thing to start with. Even if the API changes, they can be adapted easily to a new core. Another helpful thing would be reorganizing/improving the user interface (either structural (somehow get away from the current MDI concept which makes one have dozens of small windows open - especially for effects there could be a container holding concentrating all effect control windows) or by e.g. polishing the style and fix UI glitches). New/better/improved artwork also is always welcome. Another idea regarding sound output drivers: code a QtMultimedia-based AudioDevice subclass and a dedicated/native one for Windows (I guess the performance is suboptimal with the current SDL backend). Besides that I'm not really sure what a newcomer could do else. Hope I could clarify/help at least a bit. Toby |