This time with the patch file.
Extremely embarrassing but I've just had to boot to XP to attach a text
file to an email!!!
I've been using a webmail client for my work exchange account - it's not
very good.
 
I'll set up an alternate email address and reregister with the RGdev
list so that I can email properly.
 
Julie:
Thanks for the encouragement - I'd definitely like to see as few layers
as possible in the SW stack but understand that removing KDE dependance
is not a priority at this time.
 
Emanuel:
My dad has always called me CJ, so I guess that should be sufficiently
distinct from chris.
I'll just have to get over the feeling that referring to oneself by
initials or a nickname is slightly ... affected ...
 
Anyway, hope the patch is useful.
As I said in my last mail, my attempts to build QT4  are currently not
going that well so it may be a short while before I can do anything
useful!
 
Regards
CJ (!)
 

________________________________

From: Heikki Johannes Junes [mailto:[email protected]] 
Sent: 04 January 2009 20:41
To: Chris Fryer
Cc: [email protected]
Subject: Re: [Rosegarden-devel] Interested in contributing


2009/1/4 chrisf <[email protected]>



        Hello RG Dev Team,


Welcome!

Now seems like we have second Chris.



        I've spent the last couple of days building RG1.7.2 on a
PuppyLinux distro.
        Major issues were in compilation - 20 odd files had
QString/std::string
        inconsistencies and one lacked #include <utility> for access to
std::pair
        


It would be nice if you created a patch of your findings. Such a patch
could
be put to trunk, which is currently RG1.7.* branch.

We were planning to publish RG1.7.3, but it was cancelled. The reason
for the cancellation could be put in such a way that due to limited
resources of
the developers, we did not want to drive the development of the stable
branch
(trunk) and the development branch (rg-qt4) too far apart.

However, seems like there is some new development in the RG1.7.* branch.
 


        Anyway, now I've got it working, I love it. Only thing is (as
you've noted
        on the wiki) QT4 port is imperative and removing kde dependence
would be
        really nice. PuppyLinux is 90MB, QT4 is 30MB, RG is 10MB ... the
necessary
        parts of kde (kdelib, arts and kdebase, afaik) are 130MB!!!!!
        


I am also getting more and more excited of the fact that the QT4 branch
is
approaching the moment it compiles!
 


        My linux experience is fairly limited but I've got many years
experience
        writing C++ code on lots of different systems (mostly embedded,
as it goes,
        but I'm a fast learner!).
        
        I would be very happy to contribute (probably best at the C
rewrite part of
        things) and if someone could point me at a task, I'll setup SVN
and get on
        with it!
        
        Best Regards
        Chris


You may choose from the following:

(1) At the moment, it would be nice if you would pick up or own task.
Fix your
favorite bug or implement a feature request of your own. First task is
to find
out a task for you.

(2) In practice, if you set up SVN and try to compile the QT4 branch,
even the
smallest patch which would help to compile the source would be nice.

(3) We do have a ToDo list:

  http://www.rosegardenmusic.com/wiki/dev:summer_code

But these tasks are not necessarily the easiest or the most obvious
ones, or,
they are UI related and can be reliably implemented only with a
compiling source.

Unfortunately, the development of new features is stalled, because only
bugs fixes
are put to 1.7.* branch and everybody is waiting rg-qt4 to compile
before
implementing new features. Otherwise, the stable branch and QT4 branch
may
be driven far apart.


Best Regards, and Happy New Year,
Heikki

Attachment: patch_cjnf_20080104
Description: patch_cjnf_20080104

------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to