Re: Why do we still need to include Qt widget in mozilla-central?

This is now done, as of https://bugzilla.mozilla.org/show_bug.cgi?id=1282866 the Qt code has been removed from mozilla-central. --BDS On Fri, Jun 24, 2016 at 11:57 AM, Douglas Turner wrote: > I am a peer. Feel free to file a bug against me to remove this port. It > served

Re: Why do we still need to include Qt widget in mozilla-central?

I am a peer. Feel free to file a bug against me to remove this port. It served it's purpose. Anyone that wants to keep it alive can do it outside of m-c (long live dvcs). On Thu, Jun 23, 2016 at 12:35 PM Benjamin Smedberg wrote: > I'm going to resurrect this old thread

Re: Why do we still need to include Qt widget in mozilla-central?

I'm going to resurrect this old thread to ask: is anybody currently triaging bugs the Core: Widget: Qt bugzilla component? I'm trying to find owners for all of our active bugzilla components, and I'm not sure the status of this. I would support us removing the widget/qt code from the tree unless

Re: Why do we still need to include Qt widget in mozilla-central?

Hi, for quite some time I'm not really working with Qt anymore. So from my very own perspective I have to say I cannot care about it anymore realistically. So if other people are caring and want to become peers it would even be better for everyone to remove myself from the module. Wolfgang Am

Re: Why do we still need to include Qt widget in mozilla-central?

I don't know if Oleg (Romaxa) is still interested in this work. He was doing work for Nokia's MeGo platform when the code was added. MeGo was shut down by Nokia. Sailfish OS is the continuation but I don't know of any attempt to get Firefox running on Sailfish. Wolfgang is a long time Mozilla/SUSE

Re: Why do we still need to include Qt widget in mozilla-central?

Where is this work taking place? Would it be possible for you to work directly in mozilla-central? Looking at the hg history of the the widget/qt subdirectory, all the changes I see there are Masayuki updating it for changes elsewhere, and people making tree-wide changes that have nothing to do

Re: Why do we still need to include Qt widget in mozilla-central?

I think that in this context we are talking about mozilla/widget/qt/* components and yes we're using those in our Gecko build. We don't use QWidgets for Sailfish Browser. User interface of the Sailfish Browser is written with Qt QML. There is more info in the embedding wiki [1] and Dmitry's blog

Re: Why do we still need to include Qt widget in mozilla-central?

Added Raine Mäkeläinen, who has been committing to qtmozembed lately, to CC. On Thu, Apr 14, 2016 at 1:51 AM, Jim Blandy wrote: > On Tue, Apr 12, 2016 at 4:27 AM, Henri Sivonen wrote: >> >> On Tue, Apr 12, 2016 at 7:45 AM, Masayuki Nakano

Re: Why do we still need to include Qt widget in mozilla-central?

On Tue, Apr 12, 2016 at 2:45 PM, Masayuki Nakano wrote: > > > So, my question is, why do we still have Qt widget in mozilla-central? What the reason of keeping it in mozilla-central? The same question can be asked of widget/uikit/, which I believe is for the old,

Re: Why do we still need to include Qt widget in mozilla-central?

On Tue, Apr 12, 2016 at 4:27 AM, Henri Sivonen wrote: > On Tue, Apr 12, 2016 at 7:45 AM, Masayuki Nakano > wrote: > > So, my question is, why do we still have Qt widget in mozilla-central? > What > > the reason of keeping it in mozilla-central? > >

Re: Why do we still need to include Qt widget in mozilla-central?

On 2016/04/12 20:27, Henri Sivonen wrote: On Tue, Apr 12, 2016 at 7:45 AM, Masayuki Nakano wrote: So, my question is, why do we still have Qt widget in mozilla-central? What the reason of keeping it in mozilla-central? My understanding is that

Why do we still need to include Qt widget in mozilla-central?

Hello. mozilla-central has dropped a lot of platform supports after Gecko 1.9, especially OS/2 which was contributed by some volunteers. However, there is still Qt widget. Looks like that nobody isn't working on Qt widget but when I reorganizing some code, like WidgetEvent related code, I