Re: Development

7 messages

Re: Development

Reply Threaded

Hi,
First of all, you should post on MuseScore mailing list. Open source is open ;)
Then exportxml.cpp is dedicated to export MusicXML file, compliant to
musicXML DTD.
I'm not sure it's the best place to made your change except if your
plan is to add musicXML information not yet exported by musescore?
MusicXML export/import is being worked by Leon.

Next, it's pretty sure we can help each other if you share your goals
more precisely before coding.
I mean that Werner, Leon, Olav, and myself know the code (more or
less) and it might be easier for us to help
For example, I already made some prototyping to export layout
information in another xml format than musicXML.
For sure it will also be easier to understand why we should help too,
as far as I know for free...

Regarding your changes, I guess they are two criteria to be included
in the source control repository and mainstream musescore.
1- The features need to benefit MuseScore and not only your company ;)
Regarding an export filter, maybe the adoption, the fact it's a known
standard etc ... might be a criteria too. So please explain...
2- Your code have to be maintainable and don't destroy other features.

You can submit patches on the mailing list and we will discuss. But
for sure, it's better to talk about your goal and design before
submitting patches.

Regarding IDE, I don't use one. Last time I asked Werner said he
didn't neither. But maybe, someone have experience here ?

Lasconic

2009/5/6 Raffaele <[hidden email]>:

> Hi Lasconic,
> our project is evolving and I'm editing Musescore sources to include new
> functionalities.. In particular I'm working on the exportxml.cpp file in
> order to export the notes, staves and measure coordinates...
> As of now I'm changing the code freely to integrate that functionality but I
> wonder if there is a particular way of proceeding in the development...
> It's the first time that I develop for an open-source project and I don't
> know how you coordinate the development team. Could you explain me?
> Now I'm changing freely the code but... Who will control if my code is
> compatible with the project?
>
> Another question, (but maybe is better if I post it on the ML)... Do you
> know the steps that I have to follow to configure the QTCreator in order to
> build and debug with the IDE?
>
> Thank you very much...
>
> Hear you soon....
> Raffaele
>

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Raffaele-3

Re: Development

Reply Threaded

Hi,
Thank you for the explaination...

I'll explain our goals.
As a first step we would like to make Musescore able to export in
musicXML format some score layout informations. In particular I'm
interested in systems, staffs and notes positions and in measures
widths.
To describe such information with MusicXML there are tags like system-
layout, staff-layout, measure-layout and the attributes default-x and
default-y of the note tag.

Apart this first step our goal (as Rinaldo already explained in
"Introducing IANN team" post...) is to make Musescore able to export
additional informations "linked" to the score file... Such as: Raster
images representing the score, midi files as the ones exported from
Musescore or additional midi files containing different executions of
the same score.
To achieve this goal we are evaluating different output formats:

The Open Score Format seems very promising... But as far as I know as
of now there's only one implemented "Application profile"... The
application profile that describes Piano/Vocal/Guitar scores.

The alternative is to use the MusicXML format itself with the
definitions specified in the "opus.dtd" file.

In both cases we would like to make the user choose what do and what
do not export...

Any suggestion?

Thank you
Raffaele

Il giorno 06/mag/09, alle ore 15:31, Lasconic ha scritto:

> Hi,
> First of all, you should post on MuseScore mailing list. Open source
> is open ;)
> Then exportxml.cpp is dedicated to export MusicXML file, compliant to
> musicXML DTD.
> I'm not sure it's the best place to made your change except if your
> plan is to add musicXML information not yet exported by musescore?
> MusicXML export/import is being worked by Leon.
>
> Next, it's pretty sure we can help each other if you share your goals
> more precisely before coding.
> I mean that Werner, Leon, Olav, and myself know the code (more or
> less) and it might be easier for us to help
> For example, I already made some prototyping to export layout
> information in another xml format than musicXML.
> For sure it will also be easier to understand why we should help too,
> as far as I know for free...
>
> Regarding your changes, I guess they are two criteria to be included
> in the source control repository and mainstream musescore.
> 1- The features need to benefit MuseScore and not only your company ;)
> Regarding an export filter, maybe the adoption, the fact it's a known
> standard etc ... might be a criteria too. So please explain...
> 2- Your code have to be maintainable and don't destroy other features.
>
> You can submit patches on the mailing list and we will discuss. But
> for sure, it's better to talk about your goal and design before
> submitting patches.
>
> Regarding IDE, I don't use one. Last time I asked Werner said he
> didn't neither. But maybe, someone have experience here ?
>
>
> Lasconic
>
>
> 2009/5/6 Raffaele <[hidden email]>:
>> Hi Lasconic,
>> our project is evolving and I'm editing Musescore sources to
>> include new
>> functionalities.. In particular I'm working on the exportxml.cpp
>> file in
>> order to export the notes, staves and measure coordinates...
>> As of now I'm changing the code freely to integrate that
>> functionality but I
>> wonder if there is a particular way of proceeding in the
>> development...
>> It's the first time that I develop for an open-source project and I
>> don't
>> know how you coordinate the development team. Could you explain me?
>> Now I'm changing freely the code but... Who will control if my code
>> is
>> compatible with the project?
>>
>> Another question, (but maybe is better if I post it on the ML)...
>> Do you
>> know the steps that I have to follow to configure the QTCreator in
>> order to
>> build and debug with the IDE?
>>
>> Thank you very much...
>>
>> Hear you soon....
>> Raffaele
>>

Raffaele-3

Re: Development

Reply Threaded

Sorry... I was wrong when I wrote:
> The alternative is to use the MusicXML format itself with the
> definitions specified in the "opus.dtd" file.

The alternative is to use the MusicXML standard itself, but the
definition of tags that describes the linked resources are in the
link.mod file of the MusicXML 2.0 definition package.

Thanks...
Raffaele

Il giorno 06/mag/09, alle ore 18:54, Raffaele ha scritto:

> Hi,
> Thank you for the explaination...
>
> I'll explain our goals.
> As a first step we would like to make Musescore able to export in
> musicXML format some score layout informations. In particular I'm
> interested in systems, staffs and notes positions and in measures
> widths.
> To describe such information with MusicXML there are tags like
> system-layout, staff-layout, measure-layout and the attributes
> default-x and default-y of the note tag.
>
> Apart this first step our goal (as Rinaldo already explained in
> "Introducing IANN team" post...) is to make Musescore able to export
> additional informations "linked" to the score file... Such as:
> Raster images representing the score, midi files as the ones
> exported from Musescore or additional midi files containing
> different executions of the same score.
> To achieve this goal we are evaluating different output formats:
>
> The Open Score Format seems very promising... But as far as I know
> as of now there's only one implemented "Application profile"... The
> application profile that describes Piano/Vocal/Guitar scores.
>
>
>
> In both cases we would like to make the user choose what do and what
> do not export...
>
> Any suggestion?
>
> Thank you
> Raffaele
>
>
>
> Il giorno 06/mag/09, alle ore 15:31, Lasconic ha scritto:
>
>> Hi,
>> First of all, you should post on MuseScore mailing list. Open
>> source is open ;)
>> Then exportxml.cpp is dedicated to export MusicXML file, compliant to
>> musicXML DTD.
>> I'm not sure it's the best place to made your change except if your
>> plan is to add musicXML information not yet exported by musescore?
>> MusicXML export/import is being worked by Leon.
>>
>> Next, it's pretty sure we can help each other if you share your goals
>> more precisely before coding.
>> I mean that Werner, Leon, Olav, and myself know the code (more or
>> less) and it might be easier for us to help
>> For example, I already made some prototyping to export layout
>> information in another xml format than musicXML.
>> For sure it will also be easier to understand why we should help too,
>> as far as I know for free...
>>
>> Regarding your changes, I guess they are two criteria to be included
>> in the source control repository and mainstream musescore.
>> 1- The features need to benefit MuseScore and not only your
>> company ;)
>> Regarding an export filter, maybe the adoption, the fact it's a known
>> standard etc ... might be a criteria too. So please explain...
>> 2- Your code have to be maintainable and don't destroy other
>> features.
>>
>> You can submit patches on the mailing list and we will discuss. But
>> for sure, it's better to talk about your goal and design before
>> submitting patches.
>>
>> Regarding IDE, I don't use one. Last time I asked Werner said he
>> didn't neither. But maybe, someone have experience here ?
>>
>>
>> Lasconic
>>
>>
>> 2009/5/6 Raffaele <[hidden email]>:
>>> Hi Lasconic,
>>> our project is evolving and I'm editing Musescore sources to
>>> include new
>>> functionalities.. In particular I'm working on the exportxml.cpp
>>> file in
>>> order to export the notes, staves and measure coordinates...
>>> As of now I'm changing the code freely to integrate that
>>> functionality but I
>>> wonder if there is a particular way of proceeding in the
>>> development...
>>> It's the first time that I develop for an open-source project and
>>> I don't
>>> know how you coordinate the development team. Could you explain me?
>>> Now I'm changing freely the code but... Who will control if my
>>> code is
>>> compatible with the project?
>>>
>>> Another question, (but maybe is better if I post it on the ML)...
>>> Do you
>>> know the steps that I have to follow to configure the QTCreator in
>>> order to
>>> build and debug with the IDE?
>>>
>>> Thank you very much...
>>>
>>> Hear you soon....
>>> Raffaele
>>>
>

lasconic

Re: Development

Reply Threaded

Regarding layout information in MusicXML. That's great :)
Leon Vinken already added support for <page-layout> some time ago.
I added a very minimal support for relative-x for harmony. Other
layout information are not exported as you may have seen.
As far as I remember the main issues are :
- Axis in musicXML are not oriented the same way than in MuseScore
- default-x is relative to start of measure for notes for example

Maybe it's better to focus on one element first (system-layout or
measure-width or whatever) and submit a patch for it.

Any success with QtCreator ? or another IDE ?

2009/5/7 Raffaele <[hidden email]>:

> Sorry... I was wrong when I wrote:
>> The alternative is to use the MusicXML format itself with the
>> definitions specified in the "opus.dtd" file.
>
> The alternative is to use the MusicXML standard itself, but the
> definition of tags that describes the linked resources are in the
> link.mod file of the MusicXML 2.0 definition package.
>
> Thanks...
> Raffaele
>
> Il giorno 06/mag/09, alle ore 18:54, Raffaele ha scritto:
>
>> Hi,
>> Thank you for the explaination...
>>
>> I'll explain our goals.
>> As a first step we would like to make Musescore able to export in
>> musicXML format some score layout informations. In particular I'm
>> interested in systems, staffs and notes positions and in measures
>> widths.
>> To describe such information with MusicXML there are tags like
>> system-layout, staff-layout, measure-layout and the attributes
>> default-x and default-y of the note tag.
>>
>> Apart this first step our goal (as Rinaldo already explained in
>> "Introducing IANN team" post...) is to make Musescore able to export
>> additional informations "linked" to the score file... Such as:
>> Raster images representing the score, midi files as the ones
>> exported from Musescore or additional midi files containing
>> different executions of the same score.
>> To achieve this goal we are evaluating different output formats:
>>
>> The Open Score Format seems very promising... But as far as I know
>> as of now there's only one implemented "Application profile"... The
>> application profile that describes Piano/Vocal/Guitar scores.
>>
>>
>>
>> In both cases we would like to make the user choose what do and what
>> do not export...
>>
>> Any suggestion?
>>
>> Thank you
>> Raffaele
>>
>>
>>
>> Il giorno 06/mag/09, alle ore 15:31, Lasconic ha scritto:
>>
>>> Hi,
>>> First of all, you should post on MuseScore mailing list. Open
>>> source is open ;)
>>> Then exportxml.cpp is dedicated to export MusicXML file, compliant to
>>> musicXML DTD.
>>> I'm not sure it's the best place to made your change except if your
>>> plan is to add musicXML information not yet exported by musescore?
>>> MusicXML export/import is being worked by Leon.
>>>
>>> Next, it's pretty sure we can help each other if you share your goals
>>> more precisely before coding.
>>> I mean that Werner, Leon, Olav, and myself know the code (more or
>>> less) and it might be easier for us to help
>>> For example, I already made some prototyping to export layout
>>> information in another xml format than musicXML.
>>> For sure it will also be easier to understand why we should help too,
>>> as far as I know for free...
>>>
>>> Regarding your changes, I guess they are two criteria to be included
>>> in the source control repository and mainstream musescore.
>>> 1- The features need to benefit MuseScore and not only your
>>> company ;)
>>> Regarding an export filter, maybe the adoption, the fact it's a known
>>> standard etc ... might be a criteria too. So please explain...
>>> 2- Your code have to be maintainable and don't destroy other
>>> features.
>>>
>>> You can submit patches on the mailing list and we will discuss. But
>>> for sure, it's better to talk about your goal and design before
>>> submitting patches.
>>>
>>> Regarding IDE, I don't use one. Last time I asked Werner said he
>>> didn't neither. But maybe, someone have experience here ?
>>>
>>>
>>> Lasconic
>>>
>>>
>>> 2009/5/6 Raffaele <[hidden email]>:
>>>> Hi Lasconic,
>>>> our project is evolving and I'm editing Musescore sources to
>>>> include new
>>>> functionalities.. In particular I'm working on the exportxml.cpp
>>>> file in
>>>> order to export the notes, staves and measure coordinates...
>>>> As of now I'm changing the code freely to integrate that
>>>> functionality but I
>>>> wonder if there is a particular way of proceeding in the
>>>> development...
>>>> It's the first time that I develop for an open-source project and
>>>> I don't
>>>> know how you coordinate the development team. Could you explain me?
>>>> Now I'm changing freely the code but... Who will control if my
>>>> code is
>>>> compatible with the project?
>>>>
>>>> Another question, (but maybe is better if I post it on the ML)...
>>>> Do you
>>>> know the steps that I have to follow to configure the QTCreator in
>>>> order to
>>>> build and debug with the IDE?
>>>>
>>>> Thank you very much...
>>>>
>>>> Hear you soon....
>>>> Raffaele
>>>>
>>
>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>

Raffaele-3

Re: Development

Reply Threaded

Hi all!

Il giorno 07/mag/09, alle ore 10:49, Lasconic ha scritto:
> Maybe it's better to focus on one element first (system-layout or
> measure-width or whatever) and submit a patch for it.

I agree... As soon as possible I'll post the patch that I wrote for
the system-layout tag...

> Any success with QtCreator ? or another IDE ?

No... No debugging by now... :(

Before I send the first patch... I would like to repeat very clearly
that what I'll develop for MuseScore will be only general interest
features. There will be nothing interesting only for our company...

In some minutes... ;)
Raffaele

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

halil kirazlı

Re: Development

Reply Threaded

Hi Raffaele, I ve tried to debug mscore sources with qt-creator 1.2. And it is successfully done. I think you need no change in configuration. But i ve added ALL keyword to lupdate & lrelease targets in the CMakeList.txt to make them run when make all. Here is the steps:

Open CMakeList.txt in trunk/mscore with qt-creator.

Specify build folder, (i havent change it)

Run cmake for project (i have run it with "-DCMAKE_BUILD_TYPE=DEBUG .." arguments .. is the path to the CMakeList.txt)

Then build

and debug.

I'm using Kubuntu Intrepid & not tried for other systems. Here is the snapshot: http://picasaweb.google.com/lh/photo/AgOwSkykHRZ7-HxEWKVmIw?feat=directlink

2009/5/7 Raffaele <[hidden email]>

Hi all!

Il giorno 07/mag/09, alle ore 10:49, Lasconic ha scritto:

> Maybe it's better to focus on one element first (system-layout or
> measure-width or whatever) and submit a patch for it.

I agree... As soon as possible I'll post the patch that I wrote for
the system-layout tag...

> Any success with QtCreator ? or another IDE ?

No... No debugging by now... :(

Before I send the first patch... I would like to repeat very clearly
that what I'll develop for MuseScore will be only general interest
features. There will be nothing interesting only for our company...

In some minutes... ;)

Raffaele

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

--
Halil Kirazlı

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

lasconic

Re: Development

Reply Threaded

I managed to debug musescore on Ubuntu (Qt creator 1.2 or gdb
commandline) and recently on MacOSX (XCode).
But I can't find a way to debug on windows vista / XP!

Lasconic

2009/7/15 halil kirazlı <[hidden email]>:

> Hi Raffaele, I ve tried to debug mscore sources with qt-creator 1.2. And it
> is successfully done. I think you need no change in configuration. But i ve
> added ALL keyword to lupdate & lrelease targets in the CMakeList.txt to make
> them run when make all. Here is the steps:
> Open CMakeList.txt in trunk/mscore with qt-creator.
> Specify build folder, (i havent change it)
> Run cmake for project (i have run it with "-DCMAKE_BUILD_TYPE=DEBUG .."
> arguments .. is the path to the CMakeList.txt)
> Then build
> and debug.
>
> I'm using Kubuntu Intrepid & not tried for other systems. Here is the
> snapshot:
> http://picasaweb.google.com/lh/photo/AgOwSkykHRZ7-HxEWKVmIw?feat=directlink
>
> 2009/5/7 Raffaele <[hidden email]>
>>
>> Hi all!
>>
>> Il giorno 07/mag/09, alle ore 10:49, Lasconic ha scritto:
>> > Maybe it's better to focus on one element first (system-layout or
>> > measure-width or whatever) and submit a patch for it.
>>
>> I agree... As soon as possible I'll post the patch that I wrote for
>> the system-layout tag...
>>
>> > Any success with QtCreator ? or another IDE ?
>>
>> No... No debugging by now... :(
>>
>>
>> Before I send the first patch... I would like to repeat very clearly
>> that what I'll develop for MuseScore will be only general interest
>> features. There will be nothing interesting only for our company...
>>
>> In some minutes... ;)
>> Raffaele
>>
>>
>> ------------------------------------------------------------------------------
>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>> production scanning environment may not be a perfect world - but thanks to
>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
>> i700
>> Series Scanner you'll get full speed at 300 dpi even with all image
>> processing features enabled. http://p.sf.net/sfu/kodak-com
>> _______________________________________________
>> Mscore-developer mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>
>
> --
> Halil Kirazlı
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Mscore-developer mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer