Re: [Mscore-developer] Introduction

Hello, I said I'd post here when it was time to test everything. PRs related to crashes have all been merged so feel free to fire in individual bug reports in on Guitar Pro files where something unexpected is displayed or if you think anything is missing. Cheers! John On 10 August 2014 15:23, m

Re: [Mscore-developer] Introduction

That was exactly the answer I was fishing for . Thank you! -- View this message in context: http://dev-list.musescore.org/Introduction-tp7578717p7578891.html Sent from the MuseScore Developer mailing list archive at Nabble.com. --

Re: [Mscore-developer] Introduction

I will post here when the latest features are in the master and testing can begin. (For each new commit/PR I'm not sure if you can get notifications for all changes by a specific user on Github, perhaps If This Then That ( ifttt.com) will be useful there or maybe Github has some functionality for t

Re: [Mscore-developer] Introduction

How do I know when you have made a new commit available for testing? -- View this message in context: http://dev-list.musescore.org/Introduction-tp7578717p757.html Sent from the MuseScore Developer mailing list archive at Nabble.com.

Re: [Mscore-developer] Introduction

Ah good, I always look forward to a new best friend who is also my worst nightmare! :-) I would hold off on creating the relevant bug reports until my next PR goes in as there are lot of new features and edits to existing ones that have been made. I'll try and get time over the weekend so that it

Re: [Mscore-developer] Introduction

I have 500+ Guitar Pro examples on my website I need to convert to MuseScore so as a tester I can be your best friend / worst nightmare. Is the current version ready for feedback? Is the left hand fingering there? -- View this message in context: http://dev-list.musescore.org/Introduction-tp757

Re: [Mscore-developer] Introduction

On 7 August 2014 17:04, chen lung wrote: > Hi John > > Welcome and good work :). > Hello, and thanks! > I was hesitant to pounce if you are exploring things in a certain way, but > here goes! > > 1. Would it be the right time to submit reports on GPX? > Almost; I have a pull request in at the

Re: [Mscore-developer] Introduction

Hi John Welcome and good work :). I was hesitant to pounce if you are exploring things in a certain way, but here goes! 1. Would it be the right time to submit reports on GPX? 2. Some things you maybe unaware of: There are issues without a Guitar Pro tag (such as this

[Mscore-developer] Introduction

Hi! My name is Maxim Grishin and I would work on JACK integration for Google Summer of Code 2014. JACK Audio Connection Kit is a professional sound server daemon that provides real-time, low latency connections for both audio and MIDI data between applications that implement its API. This will be

Re: [Mscore-developer] Introduction (accessibility)

Hello Marc, I'm sorry for my late response, this week was my last week before finals and there were a lot of deadlines for homeworks and tests that needed to be passed in order to be accepted into the final exams. The link that Jaffar sent to me for dropbox displays an error so I've created a fol

Re: [Mscore-developer] Introduction (accessibility)

On 5/19/2014 5:09 AM, Andrei Tuicu wrote: Regarding a good primer, unfortunately there is no such thing... First of all, the accessibility API does not address basic issues like tabbing, it provides a way to generate screen-reader feedback for user defined custom widgets. There is a general des

Re: [Mscore-developer] Introduction

2014-05-19 12:25 GMT+03:00 Andrei Tuicu : > > > > 2014-05-19 2:56 GMT+03:00 Marc Sabatella : > > On 5/18/2014 4:07 PM, Andrei Tuicu wrote: >> >> This is stricly for QActions contained in QMenu objects so this would >> not affect other areas so it should not affect other areas. Also, they've >>

Re: [Mscore-developer] Introduction

2014-05-19 2:56 GMT+03:00 Marc Sabatella : > On 5/18/2014 4:07 PM, Andrei Tuicu wrote: > > This is stricly for QActions contained in QMenu objects so this would > not affect other areas so it should not affect other areas. Also, they've > marked it as an important bug, so I'm assuming that this

Re: [Mscore-developer] Introduction

On 5/18/2014 4:07 PM, Andrei Tuicu wrote: This is stricly for QActions contained in QMenu objects so this would not affect other areas so it should not affect other areas. Also, they've marked it as an important bug, so I'm assuming that this mean they will fix it. FWIW, there's mention of

Re: [Mscore-developer] Introduction

> > But assuming they are on it, there's no > reason we can't wait. > On the other hand, if this same bug basically means none of the work you > do in other areas will succeed, then maybe it does make sense to spend > some time on this. > > This is stricly for QActions contained in QMenu objects s

Re: [Mscore-developer] Introduction

Interesting blog post http://blog.qt.digia.com/blog/2014/05/14/accessibility-in-qt-5-3/ lasconic 2014-05-17 5:40 GMT+02:00 David Bolton : > On 5/15/2014 6:11 PM, Marc Sabatella wrote: >> On 5/15/2014 4:21 PM, Andrei Tuicu wrote: >>> For the second problem I created a bug report in the issue track

Re: [Mscore-developer] Introduction

On 5/15/2014 6:11 PM, Marc Sabatella wrote: > On 5/15/2014 4:21 PM, Andrei Tuicu wrote: >> For the second problem I created a bug report in the issue tracker[4]. >> I've talked with Jaffar and he told me that is expected of the Return >> or Space key to "press" the button selected by tabbing, but

Re: [Mscore-developer] Introduction

On 5/15/2014 4:21 PM, Andrei Tuicu wrote: > First of all, after a week of trying to set every property and > attribute for a QAction, contained in a QMenu, in every possible > combination and reading everything about menus in VLC, I've finally > decided to ask about shortcut issue on Qt's foru

Re: [Mscore-developer] Introduction

Hello, Marc! Sorry for the delay, but I wanted to do some actual work first, before replying to your email. First of all, after a week of trying to set every property and attribute for a QAction, contained in a QMenu, in every possible combination and reading everything about menus in VLC, I've

Re: [Mscore-developer] Introduction

On 5/6/2014 11:42 AM, Andrei Tuicu wrote: > I've started working on menus. For now I've succesfully made the > screen-reader tell both the name of the menu and it's keyboard > shortcut, you can see the commit here[0]. However I wasn't able to do > the same thing with the menu options. Even thoug

Re: [Mscore-developer] Introduction

@Marc: Hello Marc! Thank you! I'm glad to be a part of this community. I've started working on menus. For now I've succesfully made the screen-reader tell both the name of the menu and it's keyboard shortcut, you can see the commit here[0]. However I wasn't able to do the same thing with the menu

Re: [Mscore-developer] Introduction

Andrei, I look forward to following progress with accessibility in MuseScore, and glad you are able to take the lead on this! Currently the wordpress blog says "Nothing Found" and I wasn't able to subscribe to the RSS feeds. Is that because there are no posts yet, or is the URL different? http://

Re: [Mscore-developer] Introduction

Welcome, good to have you aboard! I think one of the first things we should probably do logistically is sort out what might be worth working on sooner rather than later so it can possibly be incorporated into the 2.0 release. To my mind, the things that are most "2.0-worthy" are the basic thing

[Mscore-developer] Introduction

Hello everyone! My name is Andrei Tuicu and I'm one of the students selected to work at MuseScore for Google Summer of Code 2014. My project is called Accessibility with Focus on Visually Impaired Musicians and I will be working with Marc Sabatella's guidance. If you want to follow my work I've s

[Mscore-developer] Introduction

Hello everyone, I am happy to announce that I am one of the students that will be working with MuseScore during the summer for GSoC 2014. My project is "More flexible selection facility". I will be implementing this feature under the guidance of Nicolas Froment. I have outlined the key points

Re: [Mscore-developer] Introduction

Hi Pauline, To unsubscribe, enter your email address here at the bottom: https://lists.sourceforge.net/lists/listinfo/mscore-developer And press "Unsubscribe or edit options". lasconic 2014-04-25 15:56 GMT+02:00 Pauline Marshall : > Please could someone tell me how to unsubscribe to Mscore-devel

Re: [Mscore-developer] Introduction

Please could someone tell me how to unsubscribe to Mscore-developer as I signed up by mistake and have no interest in the subject of the messages. Many thanks.   On Friday, 25 April 2014, 9:35, Ruchit Agrawal wrote: Hello everyone,  I am glad to announce that I have been selected to work on S

[Mscore-developer] Introduction

Hello everyone, I am glad to announce that I have been selected to work on Swing Playback for GSoC 2014. I will be working with the guidance of Marc Sabatella. If anyone wants to talk about Swing Playback or MuseScore in general, I am available with the handle "shredpub" on IRC. You can also mail

Re: [Mscore-developer] Introduction

On 23 Apr 2014 09:26, "Maurizio M. Gavioli" wrote: > > Hello John, Hello! > Thanks for the intro and welcome aboard! > > I'm the person assigned as mentor to your project; I saw you already walked > a good way on yourself, but do not hesitate to contact me at any moment: in > the MuseScore fora

Re: [Mscore-developer] Introduction

Hello John, Thanks for the intro and welcome aboard! I'm the person assigned as mentor to your project; I saw you already walked a good way on yourself, but do not hesitate to contact me at any moment: in the MuseScore fora and in the IRC #musescore channel, I go under the nickname Miwarre, and h

[Mscore-developer] Introduction

Hello all, I'm one of the students who has been accepted to work on the Musescore project as part of Google Summer of Code 2014! I'll be working on improving the support for Guitar Pro imports, so if anyone has any questions or comments on that then feel free to get in touch on this list or on IRC

Re: [Mscore-developer] Introduction

On 14 March 2014 15:23, Lasconic wrote: > Hi, > > I also believe MuseScore accessibility and Braille output are two > different projects that should be addressed one after the other. > Sorting out the acceesibility problems is probably large enough for a > summer project. Exactly! I will focus on

Re: [Mscore-developer] Introduction

Hi, I also believe MuseScore accessibility and Braille output are two different projects that should be addressed one after the other. Sorting out the acceesibility problems is probably large enough for a summer project. lasconic 2014-03-14 2:23 GMT+01:00 Gurjot Singh : > On 14 March 2014 05:24,

Re: [Mscore-developer] Introduction

On 14 March 2014 05:24, Marc Sabatella wrote: > Hello, and thanks for your interest! Braille output something that I > know some people have given thought to. but as far as I know, there has > been no work in this area. There was presumably some investigation as > part of a recent Kickstarter p

Re: [Mscore-developer] Introduction

On 3/13/2014 11:05 AM, Gurjot Singh wrote: > I was going through your project ideas list for GSoC 2014 and > "Accessibility for Visually Impaired Musicians" project held my > attention. > Improving the GUI and Braille export seems like a really nice way to > contribute to the software. > > On the n

[Mscore-developer] Introduction

Hi, I'm Gurjot Singh, 3rd year undergrad student of Computer Science from India. I recently stumbled across this software. I am very passionate about music production and also work as a freelancer music producer. I have some experience in C++/Qt as I've contributed towards another open source softw