Re: Showstopper desktop runtime issue

2018-03-23 Thread Dave Page
On Thu, Mar 22, 2018 at 4:58 PM, Dave Page wrote: > > > On Thu, Mar 22, 2018 at 4:28 PM, Dave Page wrote: > >> >> 2) This option is not very appealing to me, because we would be pilling code into the QT portion of the application, that I hope we remove in the future, that currently is

Re: Showstopper desktop runtime issue

2018-03-23 Thread Dave Page
Hi On Thu, Mar 22, 2018 at 6:27 PM, Joao De Almeida Pereira < jdealmeidapere...@pivotal.io> wrote: > Hello Hackers > > In the PoC we did with Electron last month this was the point where we > stopped > > What did we accomplish: > - Use Electron as a runtime and packaging solution for the applica

Re: Showstopper desktop runtime issue

2018-03-23 Thread Magnus Hagander
On Thu, Mar 22, 2018 at 5:38 PM, Robert Eckhardt wrote: > > > On Thu, Mar 22, 2018 at 12:28 PM, Dave Page wrote: > >> >>> (And don't give up on proper tabs either, but I'm sure Electron might >>> catch up in that eventually -- and the issue around RHEL6 will also go away >>> eventually) >>> >> >

Re: Showstopper desktop runtime issue

2018-03-23 Thread Magnus Hagander
On Thu, Mar 22, 2018 at 5:28 PM, Dave Page wrote: > >> >> 3) Electron >>> >>> Pros: >>> - Full Javascript runtime, no more C++ code to handle >>> - Self packaging for all the environments >>> Cons: >>> - No fully supported on Linux based OS with old libstdc++, (This might >>> solve the problem: h

Re: Showstopper desktop runtime issue

2018-03-22 Thread Joao De Almeida Pereira
Hello Hackers In the PoC we did with Electron last month this was the point where we stopped What did we accomplish: - Use Electron as a runtime and packaging solution for the application - Support opening new windows when the preferences ask for them - Make the application generally work - U

Re: Showstopper desktop runtime issue

2018-03-22 Thread Dave Page
On Thu, Mar 22, 2018 at 4:28 PM, Dave Page wrote: > > 2) This option is not very appealing to me, because we would be pilling >>> code into the QT portion of the application, that I hope we remove in the >>> future, that currently is untested to solve a problem caused by a Window >>> Manager.

Re: Showstopper desktop runtime issue

2018-03-22 Thread Robert Eckhardt
On Thu, Mar 22, 2018 at 12:28 PM, Dave Page wrote: > Hi > > On Thu, Mar 22, 2018 at 4:17 PM, Magnus Hagander > wrote: > >> >> >> On Thu, Mar 22, 2018 at 3:57 PM, Joao De Almeida Pereira < >> jdealmeidapere...@pivotal.io> wrote: >> >>> Hello Hackers, >>> Here is our take on the 3 options present:

Re: Showstopper desktop runtime issue

2018-03-22 Thread Dave Page
Hi On Thu, Mar 22, 2018 at 4:17 PM, Magnus Hagander wrote: > > > On Thu, Mar 22, 2018 at 3:57 PM, Joao De Almeida Pereira < > jdealmeidapere...@pivotal.io> wrote: > >> Hello Hackers, >> Here is our take on the 3 options present: >> > > This looks like a good summary, so I'm going to pick this on

Re: Showstopper desktop runtime issue

2018-03-22 Thread Magnus Hagander
On Thu, Mar 22, 2018 at 3:57 PM, Joao De Almeida Pereira < jdealmeidapere...@pivotal.io> wrote: > Hello Hackers, > Here is our take on the 3 options present: > This looks like a good summary, so I'm going to pick this one to comment on :) > 1) QtWebkit and QtWebEngine > > Pros: > - Webkit is

Re: Showstopper desktop runtime issue

2018-03-22 Thread Dave Page
Hi On Thu, Mar 22, 2018 at 2:57 PM, Joao De Almeida Pereira < jdealmeidapere...@pivotal.io> wrote: > Hello Hackers, > Here is our take on the 3 options present: > 1) QtWebkit and QtWebEngine > > Pros: > - Webkit is a mature technology that as been around for some time > - Apparently the Fork of W

Re: Showstopper desktop runtime issue

2018-03-22 Thread Joao De Almeida Pereira
Hello Hackers, Here is our take on the 3 options present: 1) QtWebkit and QtWebEngine Pros: - Webkit is a mature technology that as been around for some time - Apparently the Fork of Webkit we were using as been catching up Cons: - We are using a Fork - It is to far behind of the today browsers an

Re: Showstopper desktop runtime issue

2018-03-22 Thread Murtuza Zabuawala
On Thu, Mar 22, 2018 at 3:19 PM, Dave Page wrote: > All, > > As you know, the 3.0 release is currently on hold as we discovered late > yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and > later. This is because the GTK project, and later Gnome, have removed > support for

Re: Showstopper desktop runtime issue

2018-03-22 Thread Dave Page
On Thu, Mar 22, 2018 at 10:19 AM, Neel Patel wrote: > Hi, > > On Thu, Mar 22, 2018 at 3:19 PM, Dave Page wrote: > >> All, >> >> As you know, the 3.0 release is currently on hold as we discovered late >> yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and >> later. This is

Re: Showstopper desktop runtime issue

2018-03-22 Thread Neel Patel
Hi, On Thu, Mar 22, 2018 at 3:19 PM, Dave Page wrote: > All, > > As you know, the 3.0 release is currently on hold as we discovered late > yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and > later. This is because the GTK project, and later Gnome, have removed > support

Re: Showstopper desktop runtime issue

2018-03-22 Thread Akshay Joshi
On Thu, Mar 22, 2018 at 3:19 PM, Dave Page wrote: > All, > > As you know, the 3.0 release is currently on hold as we discovered late > yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and > later. This is because the GTK project, and later Gnome, have removed > support for

Showstopper desktop runtime issue

2018-03-22 Thread Dave Page
All, As you know, the 3.0 release is currently on hold as we discovered late yesterday that the re-vamped desktop runtime will not run on Gnome 3.26 and later. This is because the GTK project, and later Gnome, have removed support for the System Tray on which the new runtime relies. They have rep