Hey Florian!!;-) OK, there is no MusE's documentation
Oops !! So you don't work with UML, for example... Ok, haha, I'm so sorry, it's a hysterical laughter. Well, you are working on the edge of a razor blade! Great! The thing has its charm, risk drums are sounding on the horizon!! It's a challenge, yes, it's a challenge, and I accept it. ;-) Oh my God!! Unless somebody tell, "please, get that idea out of your head", I will start working in a complete, comprehensible and clear documentation of our beautiful beast. Otherwise, we are creating a snowball falling furious by the frozen slopes of the segmentation fault, or in other words, a building built on quicksand and which anytime collapses. I love the anarchy of this project, but I hate chaos. Anyway, I don't know where to start, could anybody tell me where is the kernel of the application, please? I suppose I have to start there. I expect to have something as soon as I can. I hope before the end-of-year. OK, great!!;-) Cheers, and looking forward to hear from you! Caba On 06/10/15 10:32, Florian Jung wrote: > Hey ;) > > sorry, there are some phases of silence on this ML, and seems like this > was one :D > > there is the muse2/doc/ folder in the repo with a .tex and .pdf file, > but it's barely usable, and especially covers mostly audio-related > stuff, not MIDI. > > When looking for hints right now, I'm afraid that "Use the Source, Luke" > is the best way currently. I recommend you trying to understand the > score editor at first (maybe you run "git log scoreeditor.cpp" and try > out older versions). This is because when I wrote the score editor (from > scratch), I was in the same situation: No docs available, had to figure > everything out. > > Actually, the score editor uses some kind of intermediate > representation, they might(?) be still called FloEvent, which is > basically an (unneeded) layer to abstract from the MusE implementation > which I did not fully understand at that time. > > What I still can recall: > > there is some global tracklist. A MidiTrack holds MidiParts, a MidiParts > holds Events or something like that. > > where "holds" means: they are derived (or contain?) a > map<unsigned,Event> or map<unsigned,Part*> (note the pointer here!), > where the "unsigned" means the *END* of the event/part, not its > beginning. no idea why it is that way. > > Umm, yea. Reading these structures is as easy as doing it, writing them > is forbidden. use proper audio thread messages for that, basically you > want to look at applyOperationGroup, which is $somewhere (grep is your > friend. really :/) > > Hope this helps a bit > > cheers > flo > > On 10/05/2015 12:57 PM, Caba wrote: >> Hi there, >> >> Yesterday I commented that it was my intention to join you in the >> development of Muse. >> But I do not know where to start, so I asked for a guide, if it existed, >> to developers, or documentation, something to be able to update me. >> If this guide or documentation does not exist, in my opinion we should >> do one. >> I volunteer to do it, if that is the case. >> Anyway, I expect an answer. >> >> Sincerely, >> Caba >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Lmuse-developer mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > ------------------------------------------------------------------------------ > _______________________________________________ > Lmuse-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lmuse-developer ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
