Re: [Rosegarden-devel] concerning qt4 / kde4 port

[Chris C. <ca...@al...>]

On Mon, Sep 1, 2008 at 8:07 AM, Emanuel Rumpf <xb...@we...> wrote:
> ok.. after thinking about it again,
> I somehow changed my opinion:
>
> 1. The mechanized part, won't work the way, you'd enjoy it to do !
> There are just to many parts, that cannot be script-replaced,
> so we need to skip through the whole code anyway !

That's completely true.  At some point, we have to apply and commit
all the mechanised changes and start doing things by hand.

However, it's very beneficial to be able to put off that moment until
the major structural changes (such as removal of DCOP, happening in
the "threads" branch, which I mentioned in my previous email) have
been merged, because it is much harder to do these merges after the
target branch has already had a lot of manual changes applied all over
it.

To put that another way: the manual work is necessary, but "the
current trunk" is not the right place to start from.  The right place
to start from is "the trunk after any major structural changes that
are already ongoing have been made and any automated changes that we
can do have been applied".

You have to remember that there is a lot of work that has already been
done in qt4-mechanised and other branches -- it doesn't make any sense
to do parts of the same work again in another branch without taking
advantage of this.  Almost 50% of the qt4-mechanised branch already
compiles with the scripted changes applied, and it has solutions to
some complicated problems like (much of) the syntax of grid layouts
and use of command base classes.

But, from your and Julie's emails it's pretty clear that this might be
a good time to call a halt to the scripting stuff, do a provisional
merge and commit with the structural work that has already happened in
other branches (which is mostly done, in the case of the DCOP removal
work), and commit a branch that we actually can hack on on manually.
What I don't quite know is how many of the changes made in rg_qt4_01
we'll be able to merge straight to that branch afterwards -- we'll
have to see about that.  I'll see if I can do that merge today and get
back to the list about it later.


Chris