Sacgarden, You can check out the latest nightly builds to see the current state of the user interface: http://musescore.org/en/download#Nightly-versions
As with any change it is good to describe the rational. User scenarios are a good place to start: explain how the proposed change better serves the user for a given scenario. Also discuss any consequences (will it make it more difficult for the user in other scenarios? Is the trade off worth it?) David On 12/19/2013 10:23 AM, sacgarden wrote: > Hi! MuseScore is an amazing piece of software and I would really like to > contribute if I can, especially on the UI front. From what I gathered from > the mailing list, there seems to be an on-going effort on the interface > redesign (aka MuseScore 2.0). May I ask what's the current status now? Are > we still on the design phase or we are already implementing the new change? > > I think feature-wise, MuseScore is already very completed and can be used > for serious work already. However, IMHO there is still quite some room for > improvement in the UI. I would like to know what I can help in this area. > > Thanks! > > ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
