Hi,
Here are the patches needed to get the kmozilla code to work again. Note that it was also quite buggy in its previous life and none of those previous bugs have been looked at yet. These patches provide the minimum to get the code compilable and displaying webpages again.
So here is a list of known issues: - buttons like back, forward do not work - progress indication seems broken - some webpages load and then display a white screen
Here is a screenshot showing it works somewhat again: http://lh6.googleusercontent.com/-BiSwJPk2dHY/Tod915u2bAI/AAAAAAAAAd8/tLv1yH...
To be able to compile the build files need adjustments as well, for which I did not create patches. This basically comes down to adding everything needed for GTK 2.0 (and it's dependencies like GLIB 2.0, Cairo, Pango 1.0 and ATK 1.0) and XULRunner. I did not look into details into the linking of the kmozilla binary, I linked it against libxul and libxpcom to get it to find all its symbols, but it seems there is a better way. There is more info here: https://developer.mozilla.org/en/GRE
I developed the patches on 3.5.11 on a Lucid system. I couldn't easily test the patches against the latest Subversion tree, but I make them against it. So I hope I didn't forget anything....
I originally thought I couldn't do this. Thanks a lot to Timothy Pearson & the others on IRC who helped me with this!!
Thanks, Julius
PS: It seems the kdebindings_c_dcopc_fix_byteorder ifdefs are not working as intended yet. It would be good to have a neater fix for this. Also see: http://bugs.kde.org/show_bug.cgi?id=32463
Julius Schwartzenberg wrote:
Hi,
Here are the patches needed to get the kmozilla code to work again. Note that it was also quite buggy in its previous life and none of those previous bugs have been looked at yet. These patches provide the minimum to get the code compilable and displaying webpages again.
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
Julius Schwartzenberg wrote:
Hi,
Here are the patches needed to get the kmozilla code to work again. Note that it was also quite buggy in its previous life and none of those previous bugs have been looked at yet. These patches provide the minimum to get the code compilable and displaying webpages again.
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
OK, the patches are in SVN as of revision 1256724. The build system has not yet been fixed, but will be in the (near) future.
Tim
On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote:
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
What is needed to enable this Mozilla support? It seems it wants gtkmozembed.h which is not provided by any devel package.
On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote:
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
What is needed to enable this Mozilla support? It seems it wants gtkmozembed.h which is not provided by any devel package.
We are not yet sure if gtkmozembed has been removed in the latest xulrunner versions. Right now this is only for systems with Firefox less than version 5, and work will be done to see if this can be extended to later Firefox versions in the future.
Tim
On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote:
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
What is needed to enable this Mozilla support? It seems it wants gtkmozembed.h which is not provided by any devel package.
We are not yet sure if gtkmozembed has been removed in the latest xulrunner versions. Right now this is only for systems with Firefox less than version 5, and work will be done to see if this can be extended to later Firefox versions in the future.
Tim
A bit more information, as gtkmozembed is apparently quite widely used still: http://stackoverflow.com/questions/2653686/how-to-compile-a-program-with-gtk...
Tim
On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote:
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
What is needed to enable this Mozilla support? It seems it wants gtkmozembed.h which is not provided by any devel package.
We are not yet sure if gtkmozembed has been removed in the latest xulrunner versions. Right now this is only for systems with Firefox less than version 5, and work will be done to see if this can be extended to later Firefox versions in the future.
Tim
A bit more information, as gtkmozembed is apparently quite widely used still: http://stackoverflow.com/questions/2653686/how-to-compile-a-program-with-gtk...
Tim
And straight from the horse's mouth: http://groups.google.com/group/mozilla.dev.embedding/browse_thread/thread/e5...
Essentially we would need to take over gtkmozembed (which is not a bad thing at all!) if we want to keep using it. From what I can tell that means we put it in our 3rdparty GIT tree and build a little standalone library against xulrunner.
Tim
Ilya Chernykh wrote:
On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote:
So here is a list of known issues:
- buttons like back, forward do not work
- progress indication seems broken
- some webpages load and then display a white screen
I forgot to add. It's necessary for the kmozilla binary to see two environment variables as well. First of all, it needs to find its libraries and also it needs to know the location of the Mozilla environment it should use. Something like this should work: export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ konqueror (and open a site and choose kmozilla as the viewer)
Maybe a kcontrol panel could be added at some point that allows choosing the Mozilla environment to use.
What is needed to enable this Mozilla support? It seems it wants gtkmozembed.h which is not provided by any devel package.
On Ubuntu this is provided by the XULRunner development package.
SuSE actually shipped this control around version 8.0 in a package called 'kdebindings3-mozilla'. Maybe this would also be interesting to look at.
On Sunday 02 October 2011 11:52:37 Julius Schwartzenberg wrote:
On Ubuntu this is provided by the XULRunner development package.
SuSE actually shipped this control around version 8.0 in a package called 'kdebindings3-mozilla'. Maybe this would also be interesting to look at.
kdebindings3-mozilla cannot be built without gtkmozembed.h.
Ilya Chernykh wrote:
On Sunday 02 October 2011 11:52:37 Julius Schwartzenberg wrote:
On Ubuntu this is provided by the XULRunner development package.
SuSE actually shipped this control around version 8.0 in a package called 'kdebindings3-mozilla'. Maybe this would also be interesting to look at.
kdebindings3-mozilla cannot be built without gtkmozembed.h.
Yes this makes sense. I mainly wanted to point out that it was previously in SuSE already. It seems gtkmozembed.h has indeed been removed from newer Mozilla/XULRunner versions. Ubuntu still ships with XULRunner 1.9.2, which is why my system still has this header.
In case you are interested in the sources of this version, which include gtkmozembed.h, they are here: http://packages.ubuntu.com/lucid/xulrunner-1.9.2
Upstream, you can find different releases of XULRunner here: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/
I'm not really sure how the version numbers work there and why there is no 1.9.2 package, but the 1.9.1 version over there also includes the gtkmozembed.h header.
On Sunday 02 October 2011 13:36:06 Julius Schwartzenberg wrote:
Upstream, you can find different releases of XULRunner here: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/
I'm not really sure how the version numbers work there and why there is no 1.9.2 package, but the 1.9.1 version over there also includes the gtkmozembed.h header.
openSUSE 11.4 (the last year release) includes xulrunner 2.0.
Ilya Chernykh wrote:
On Sunday 02 October 2011 13:36:06 Julius Schwartzenberg wrote:
Upstream, you can find different releases of XULRunner here: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/
I'm not really sure how the version numbers work there and why there is no 1.9.2 package, but the 1.9.1 version over there also includes the gtkmozembed.h header.
openSUSE 11.4 (the last year release) includes xulrunner 2.0.
I just checked. Ubuntu Natty has both a xulrunner-1.9.2 and a xulrunner-2.0 package. Both include this header however!
See the list of files on this page: http://packages.ubuntu.com/natty/xulrunner-2.0-dev
Could you check the source package on which the OpenSUSE package is built?
On Sunday 02 October 2011 14:32:02 Julius Schwartzenberg wrote:
Upstream, you can find different releases of XULRunner here: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/
I'm not really sure how the version numbers work there and why there is no 1.9.2 package, but the 1.9.1 version over there also includes the gtkmozembed.h header.
openSUSE 11.4 (the last year release) includes xulrunner 2.0.
I just checked. Ubuntu Natty has both a xulrunner-1.9.2 and a xulrunner-2.0 package. Both include this header however!
In openSUSE - neither.
Ilya Chernykh wrote:
On Sunday 02 October 2011 14:32:02 Julius Schwartzenberg wrote:
Upstream, you can find different releases of XULRunner here: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/
I'm not really sure how the version numbers work there and why there is no 1.9.2 package, but the 1.9.1 version over there also includes the gtkmozembed.h header.
openSUSE 11.4 (the last year release) includes xulrunner 2.0.
I just checked. Ubuntu Natty has both a xulrunner-1.9.2 and a xulrunner-2.0 package. Both include this header however!
In openSUSE - neither.
What about the source package from which these packages are built? I suppose you were looking at the RPMs?
Julius Schwartzenberg wrote:
PS: It seems the kdebindings_c_dcopc_fix_byteorder ifdefs are not working as intended yet. It would be good to have a neater fix for this. Also see: http://bugs.kde.org/show_bug.cgi?id=32463
Here is another patch that can be applied on top of the earlier patches. I based it on this: http://www.gnu.org/software/autoconf/manual/autoconf.html#C-Compiler
I don't know if the build system would need to adapted for this.
The version with this patch at least works on little endian again. The current version in Subversion does not work.
Julius Schwartzenberg wrote:
PS: It seems the kdebindings_c_dcopc_fix_byteorder ifdefs are not working as intended yet. It would be good to have a neater fix for this. Also see: http://bugs.kde.org/show_bug.cgi?id=32463
Here is another patch that can be applied on top of the earlier patches. I based it on this: http://www.gnu.org/software/autoconf/manual/autoconf.html#C-Compiler
I don't know if the build system would need to adapted for this.
The version with this patch at least works on little endian again. The current version in Subversion does not work.
OK, this should be fixed in SVN revisions 1256944 and 1256945.
Thanks!
Tim
-
Ilya Chernykh -
Julius Schwartzenberg -
Timothy Pearson