Hi Nicolas,
I have set up my MuseScore project with GitHub and was able to build and
run/debug on my Kubuntu Linux PC.
I was browsing through the source code yesterday.
The easiest way seems to be to implement Jianpu the same way as the
TabStaff was implemented.
So I can just add JIANPU in the StaffGroup type and add variations
specific to Jianpu in some 20-25 classes.
enum class StaffGroup : char {
STANDARD, PERCUSSION, TAB
};
The TabStaff seems to have its own staff and notes apart from the
standard staff, since it's of Staff class itself.
How do standard staff and tab staff share their notes?
Or they have their own copies of notes?
Another question:
Can user directly enter/edit notes in the tab staff and are the changes
reflected automatically on the standard staff?
Regards,
Brian
On 11/26/2016 09:29 AM, Lasconic wrote:
Hi Brian,
How is it going? You find your way around MuseScore source code. Let
me know if I can help.
lasconic
2016-11-19 18:55 GMT+01:00 Lasconic <lasco...@gmail.com
<mailto:lasco...@gmail.com>>:
I'm in France (+7 for you) and I'm on IRC from ~8am to ~8pm (or
later) during the week. So you can catch me every morning for you.
A couple developers are in the US too.
lasconic
2016-11-19 18:11 GMT+01:00 Brian Yan <brian....@verizon.net
<mailto:brian....@verizon.net>>:
Thanks, Nicolas.
I'll start writing something up in the issue page.
Live chat on IRC may not work out well due to time-zone
difference -- I live in Texas, U.S.A.
What time-frame are you usually online on IRC?
Regards,
Brian
On 11/19/2016 02:06 AM, Lasconic wrote:
Hi Brian,
I created an issue to follow the development of the Jianpu
feature and where you can explain the requirements
https://musescore.org/en/node/141581
<https://musescore.org/en/node/141581> I'm curious how you
envision Jianpu support. Do you want to be able to playback
the Jianpu? Do you want to link it with a standard notation
staff like tab/standard can be linked?
You can use this issue number for the branch name 141581-jianpu
The code will be reviewed by the whole community. Werner and
I always make the final call to pull the changes in the
master repository.
This mailing list is fine if it's pure development and
architecture but it has very low traffic. If you need larger
feedback, it's probably better to open a forum post in the
Technology Preview Forum https://musescore.org/en/forum/687
<https://musescore.org/en/forum/687>. The forum has a larger
audience and a mix of developers and users. And as mentioned,
we can have a live chat on IRC where several developers hang out.
lasconic
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
<mailto:Mscore-developer@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mscore-developer
<https://lists.sourceforge.net/lists/listinfo/mscore-developer>
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
<mailto:Mscore-developer@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/mscore-developer
<https://lists.sourceforge.net/lists/listinfo/mscore-developer>
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer
