Open GoogleCodeExporter opened 8 years ago
http://qa.openoffice.org/issues/
The question being whether we report it in this bugtracker or to the go-oo.org
tracker (community run) possibly more open to this bug than Sun.
Original comment by pierre.s...@gmail.com
on 25 Nov 2008 at 8:58
Not quite the time before we can get a stable Global Menu API.
Original comment by rainwood...@gmail.com
on 26 Nov 2008 at 1:22
Do it after 1.0.
Original comment by rainwood...@gmail.com
on 14 Dec 2008 at 8:41
http://www.openoffice.org/issues/show_bug.cgi?id=98157
Original comment by pierre.s...@gmail.com
on 16 Jan 2009 at 6:45
The upstream bug has a couple of comments.
Original comment by pierre.s...@gmail.com
on 1 Apr 2009 at 3:46
Issue 404 has been merged into this issue.
Original comment by pierre.s...@gmail.com
on 7 May 2009 at 7:13
This is not a bug, per sé, but I don't think I can edit wiki pages here..
As of version 3.0, OpenOffice has native OS X global menu support,
deprecating the NeoOffice OO.o fork. If one could write some kind of
translation layer between OS X and GNOME menu handling for OO.o, the
majority of the code to support global menus should already be in its code
base.
If you can set a global menu compile time flag in OpenOffice apart from
other OS X related flags, so that those components are enabled on Linux
based operating systems, might it be possible with minor modification to
add support to gnome-globalmenu for OS X menus and have OO.o menus go
through that?
Original comment by pierre.s...@gmail.com
on 7 May 2009 at 7:13
Merging with the existing OOo bug.
I have seen that, but right now, we have now one with enough OOo knowledge to
investigate it further on.
A similar solution might be doable for Firefox.
Original comment by pierre.s...@gmail.com
on 7 May 2009 at 7:14
Original comment by pierre.s...@gmail.com
on 1 May 2010 at 9:13
Original issue reported on code.google.com by
pierre.s...@gmail.com
on 25 Nov 2008 at 1:32