Patrick Shirkey
2013-02-10 04:23:04 UTC
Hi,
I ran a few tests of the various options for getting clutter and gtk3 into
the gtk2 UI and the results were not very good. So I spent some time now
(about 8 hours so far) migrating the existing code to gtk3 and adding a
basic clutter stage.
After a few hours of pain I have managed to get the interface to build and
run. Although I had to disable the hdeq, compressor graphs and meters as
well as make a few guesses about the layout of the grid columns which is
going to be a bit of a hassle to rebuild :-(
The good news is that it had to be done at some point if we want to keep
moving forward so it seems there is no time like the present.
The question now is should I spin up a new tree for this version or is it
ok to go ahead and update the code to the existing repo. Given that we
haven't been doing very much to jamin for the past few years I'm not
fussed if the old gui is completely replaced by a new shiny gtk3/clutter
version.
However this might be a good opportunity to move to svn too.
FYI, the benefits of clutter are opengl support, touch interface support,
UI animation support and that it frees us from the gtk h/vbox lock in by
allowing us to place any size or shape widgets at any location on the
x/y/z axis.
I have already been doing some work with it for the CMKeyboard project in
python. It's very powerful and a lot of fun too if you like UI dev :-)
Cheers
--
Patrick Shirkey
Boost Hardware Ltd
I ran a few tests of the various options for getting clutter and gtk3 into
the gtk2 UI and the results were not very good. So I spent some time now
(about 8 hours so far) migrating the existing code to gtk3 and adding a
basic clutter stage.
After a few hours of pain I have managed to get the interface to build and
run. Although I had to disable the hdeq, compressor graphs and meters as
well as make a few guesses about the layout of the grid columns which is
going to be a bit of a hassle to rebuild :-(
The good news is that it had to be done at some point if we want to keep
moving forward so it seems there is no time like the present.
The question now is should I spin up a new tree for this version or is it
ok to go ahead and update the code to the existing repo. Given that we
haven't been doing very much to jamin for the past few years I'm not
fussed if the old gui is completely replaced by a new shiny gtk3/clutter
version.
However this might be a good opportunity to move to svn too.
FYI, the benefits of clutter are opengl support, touch interface support,
UI animation support and that it frees us from the gtk h/vbox lock in by
allowing us to place any size or shape widgets at any location on the
x/y/z axis.
I have already been doing some work with it for the CMKeyboard project in
python. It's very powerful and a lot of fun too if you like UI dev :-)
Cheers
--
Patrick Shirkey
Boost Hardware Ltd