Success updating my fork and setting up my build environment - the developer's handbook instructions worked perfectly.
Already started work and seeing some success with my first project - tackling that chord parser I keep going on about. It's actually shaping up to be every bit as straightforward as I hoped. Right now, I'm only parsing chords if the initial literal comparison loop fails, to minimize the impact of the change. Only currently-unrecognized chords will trigger my code. And it's still an exhaustive search against a predefined list of chord id's - it's just a more flexible search. Eventually we could still try to hook into the harmony editor as we discussed in the video conference, and try to come up with a system of display rules to output chords meaningfully. But that sounds long term to me, and it would no doubt require a much deeper knowledge of internals than I possess. I'd still love to get something in for 2.0. So you can expect a pull request from me, hopefully within the next week or so. If someone wants to take that and run with it to integrate with the harmony editor or otherwise do something more sophisticated, that's fine too - even if it means scrapping my code. Marc -- View this message in context: http://dev-list.musescore.org/recreating-my-github-environment-tp7578062p7578065.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
