Re: [Libreoffice] feature/gtk3 merged ...
On Thu, 2011-10-27 at 01:24 -0400, Kevin Hunter wrote: > After a long build, I'm there. As I'm not mired in that part of LibO > internals, for what visible changes should I be looking? Cool :-) glad you've got a build. Just a tip: stick with that build for a while, and/or have two build trees - one that you keep up-to-date with origin/master and one to hack on. > Heh, or put differently, what Ctrl+F should I use on Oh - well, in theory everything continues to work perfectly :-) you usually notice if there is a rendering regression - the screen is corrupted and/or the app hangs / performs terribly in some case. Hopefully it doesn't, indeed - I'm fairly optimistic after a good set of builds, and the few bugs I was scared of (eg. multimedia embedding) turned out to be in unrelated code :-) > http://wiki.documentfoundation.org/ReleaseNotes/3.5 ? ;-) Which reminds me - I should update that with a couple of new features :-) ATB, Michael. -- michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] feature/gtk3 merged ...
On 10/25/2011 04:32 PM, Noel Grandin wrote: Getting there :) almost have a complete build on my machine :) After a long build, I'm there. As I'm not mired in that part of LibO internals, for what visible changes should I be looking? Heh, or put differently, what Ctrl+F should I use on http://wiki.documentfoundation.org/ReleaseNotes/3.5 ? ;-) Cheers, Kevin ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] feature/gtk3 merged ...
Getting there :) almost have a complete build on my machine :) On Tuesday, October 25, 2011, Michael Meeks wrote: > Hi Noel, > > On Tue, 2011-10-25 at 18:51 +0200, Noel Grandin wrote: >> Duration timers are best implemented using the system's monotonic >> clock.In Java, this is System.nanoTime(),under linux, this is >> clock_gettime(CLOCK_MONOTONIC),under windows, it is GetTickCount() > >You're certainly right; I'm really just replacing what was there > before; but patches as always are welcome :-) vcl/unx/gtk/* > >ATB, > >Michael. > > -- > michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot > > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] feature/gtk3 merged ...
Duration timers are best implemented using the system's monotonic clock.In Java, this is System.nanoTime(),under linux, this is clock_gettime(CLOCK_MONOTONIC),under windows, it is GetTickCount() On Tue, Oct 25, 2011 at 17:40, Michael Meeks wrote: > > On Tue, 2011-10-25 at 13:54 +0100, Michael Meeks wrote: >> There is one minor annoyance I discovered of a warning under gtk2: >> g_main_context_prepare(): main loop already active in another thread > > I pushed a fix for this by implementing a custom timer GSource that we > can query for expiration more easily. Of course - custom timer GSources > can introduce all manner of fun stuff: pwrt. dis-contiguous time - some > testing on suspend/resume, and changing system time not causing > LibreOffice to lock-up would be much appreciated [ when using the gtk2 > frontend: export SAL_USE_VCLPLUGIN=gtk forces that ]. > > Thanks, > > Michael. > > -- > michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot > > ___ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] feature/gtk3 merged ...
On Tue, 2011-10-25 at 13:54 +0100, Michael Meeks wrote: > There is one minor annoyance I discovered of a warning under gtk2: > g_main_context_prepare(): main loop already active in another thread I pushed a fix for this by implementing a custom timer GSource that we can query for expiration more easily. Of course - custom timer GSources can introduce all manner of fun stuff: pwrt. dis-contiguous time - some testing on suspend/resume, and changing system time not causing LibreOffice to lock-up would be much appreciated [ when using the gtk2 frontend: export SAL_USE_VCLPLUGIN=gtk forces that ]. Thanks, Michael. -- michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] feature/gtk3 merged ...
Hi guys, I just pushed feature/gtk3 to master. What does that mean ? well, a few things. While there are no known major bugs, and a fair bit of testing has been done - there are a large number of backends that this affects. This mainly affects unix where it touches the gtk, gtk3, gen, svp, kde and kde4 backends. As you can see this makes testing every corner under every toolkit somewhat hard. Having said that the biggest changes are to the gtk and svp backends. * implements an (unfinished) but 'pure' gtk3 port + avoids direct X library linkage + enables broadway / web-office prototype + cleanly re-uses svp for client-side rendering + churns synchronous debug, performs badly, is unfinished etc. [ should default to off ] * improves the svp code + avoids direct X library linkage + thus making targetting Android / iOS possible + substantially accelerates rendering by working around many clipping performance issues + adds damage detection to svp rendering surfaces + aborted attempt to make svp fully cross-platform, blocked on an internal freetype or more re-factoring * re-factoring / cleanup + shares lots of code between gtk, svp and gen backends lots of cut/paste code eliminated. + ports lots of gtk2 code to use gdk wrappers instead of raw X, to share with gtk3 + the gtk build should compile without warning still. + re-working of misc. legacy cross-platform code. The gtk3 code is of course not yet optimal, there is plenty of scope for improvement. It should also be the case that vcl/ is still ABI/binary compatible - though unfortunately one enumeration re-name in a public header, and some new struct constructors may cause a fairly wide re-build on updating. It is entirely possible that some platform will get broken - if so I apologise - but it has been run-time tested on Mac, MingW, and all of the above mentioned Unix variants without significant problems. There is one minor annoyance I discovered of a warning under gtk2: g_main_context_prepare(): main loop already active in another thread that comes from me slightly mis-using the glib mainloop on older glibs (sadly it seems that I need to write our own timeout source to compensate). Anyhow - thoughts / bugs / reactions much appreciated, ATB, Michael. -- michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice