On Mon, 2005-07-25 at 08:15 +0200, Guillaume Laurent wrote: > > I don't forsee any problems merging in the changes. Take a look at the > > SConstruct and see what I have done. > > Well for one thing you seem to have splitted all install stuff into several > SConscript files in all the subdirectories. I faiil to see what's this has to > do with your guitar chord stuff, and I'd rather keep the number of > scons-related files to a minimum.
In the course of my development work I wanted to look into how I could
run tests for the guitar chord stuff as you would do with the autotools
('make check') and so I wanted to place all my guitar chord stuff into a
SConscript file and not add to the main SConstruct. In understanding
more about scons I realized that could help out the rosegarden project
as I have done with the xine project (http://xine.sf.net). On that
project I have helped out with the autotools build system. I helped add,
modify or delete features from the build system. So I have a natural
bent towards making sure the build system on rosegarden runs well.
So I am volunteering myself to learn scons, which I plan on using in
other projects, to maintain the scons build system if that is acceptable
to everyone.
I have a lot to learn but with Thomas Nagy's help I will make full use
of bksys and scons.
I understand the infrastructure work, like scons or autotools, does not
wet the appetite of most developers. So I can understand a need to keep
a few scons related files around since it makes life more tolerable sort
of like fewer trips to the dentist. Personally I don't mind. So I am
raising my hand to say I am volunteering.
So in regards to the guitar chord stuff I am working with Thomas Nagy on
making it so that you can run the guitar chord tests when you type
'scons test'. The tests are built with the rest of rosegarden. These
tests are not installed and so are of no concern to the user. A packager
can run them if they desire. What I am not sure about, and hopefully
Thomas can help me, is how to make the build requirements for the tests,
boost unit test library, something that is not required except when a
packager wants to test rosegarden.
My latest problem on the guitar chord stuff is, now that I am sending a
list of Event objects with all the chord information to the notation
editor, how do I generate the display? There was made mention of the
need to have the image be scalable. At present the guitar chord editor
has a set QFrame (FingeringConstructor) on which I display the guitar
chord. In this class it is the responsibility of the Fingering object,
not the FingeringConstructor, to display itself with a given QPainter
object. My design idea was to have the notation editor use the guitar
chord editor to generate a fretboard image with some given arguments
(e.g. width and height of image). What I gather was that some thought
that the notation editor should be responsible for generating this image
of the fretboard. So my work was adjusted to accomodate for that. I am
not partial to either the Fingering or notation editor being responsible
for generating the fretboard.
I just need to learn how do I:
- create a fretboard image on some QT type (e.g. QPixmap) from the Event
information (Similar to creating a note to display on the notation
editor)
- how to detect where this fretboard image should be displayed.
Note: I am getting packed to move to Auburn, Alabama to attend Auburn
University. So I will be working a bit on the guitar chord code but not
all the time.
Stephen
Stephen
signature.asc
Description: This is a digitally signed message part
