Is there any document for source code?
Hi
I'm a C++ Programmer and I have lots of idea for Musescore, I want to implement and add the ideas to Musescore. But at first i need to understand "How to work source code of musescore", i download the source codes but i can't find any documentation on it.
Is there any document for source code?
How can i start learning source code of Musescore?
This huge source codes couldn't be developed without any documentation!.
Comments
http://musescore.org/en/developers-handbook
In reply to http://musescore.org/en/devel by Jojo-Schmitz
Thanks
In reply to Thanks by imanison
Hi,
The developer handbook is the main documentation. Make to compile and run the last master of the code before starting. There are a lot of new features already implemented. Don't hesitate to come to our IRC channel #musescore on freenode.net if you want to discuss with fellow developers.
In reply to Hi, The developer handbook is by [DELETED] 5
Hi
Surely I will come to your IRC channel
But one more question: Is there any full UML diagram for mscore?
In reply to Hi Surely I will come to your by imanison
It's not what you may be looking for but here is what we have.
http://musescore.org/en/developers-handbook/references/design-implement…
In reply to See the developer handbook by Thomas
Thanks but I've already seen it.
As you told i'm looking for a UML diagram with more details, at least class diagram and description for each class.
In reply to Thanks but I've already seen by imanison
No there isn't any UML diagram of MuseScore classes. You can generate some source code documentation with doxygen but the main documentation for the source code is the source code itself...
If you have any specific ideas, please list them in a answer and we will try to help you find the revelant classes. Also, it's probably a good idea to start fixing some bugs in MuseScore before implementing anything large and new in order to get a sense of the source code.
In reply to No there isn't any UML by [DELETED] 5
Also, since they are trying to converge on an actual 2.0 release sooner rather than later, fixing bugs helps more than anything likely to introduce ones :-)