Hi On Tue, Jan 23, 2018 at 6:48 PM, Doug Easterbrook <d...@artsman.com> wrote:
> I had a look — running it on Safari/OSX/High Sierra. > > it started fast and seemed responsive. > > I couldn’t get it to start a SQL query session to put in some query to see > how that went, bu I did click on a bunch of other things and it seemed very > responsive.. which is what you want to know. > If you can't start a SQL query session, that's a concern - though the changes in the runtime shouldn't actually affect that at all. What happens if you try to open the query tool? > > I was able to put the URL into another tab and have two copies running. > that was easy enough. > > > Without a bunch of hoopla, I couldn’t get it to run in firefox or chrome > to see how that might run. > Yeah, you'd have to change your default browser in the OS. I am adding an option to allow you to specify an alternate command line to execute. > > > and it seems like it needs to be started from the app — as I couldn’t > just stick the URL into second browser. > You should be able to start it from the app, or from the Applications folder (it should detect it's already running and just open a new window). Sticking the URL in another window won't work - that's intentional; it's to stop another user on your machine connecting to your instance of the app. When the window is first opened, a security key is passed in, and that won't happen if subsequent URLs are opened manually. > > > > the end goal — is use the browser. > > I”m not sure if that means I’ll be able to bookmark the URL and then just > use it locally. if so… that might be nice. > At the moment the security key and use of a random port would prevent that. It sounds like you want to run in true server mode, which would do what you want (but add username/password login to the app to replace the port/key based security). > > and getting a SQL session in another browser applicaiton .. that would be > good too. > File -> Preferences -> SQL Editor -> Display -> Open in new browser tab (ignoring the issue you noted about the query tool not working) > > > just my thoughts. > > > *Doug Easterbrook* > *Arts Management Systems Ltd.* > mailto:d...@artsman.com <d...@artsman.com> > http://www.artsman.com > Phone (403) 650-1978 <(403)%20650-1978> > > > > see you at the third annual users conference > https://tickets.proctors.org/TheatreManager/95/online?performance=29086 > > On Jan 23, 2018, at 7:48 AM, Dave Page <dp...@pgadmin.org> wrote: > > All, > > As you may know, the most troublesome part of pgAdmin 4 has been the > desktop runtime application, which has relied on QtWebKit and QtWebEngine > (of various origins and versions) to render the UI as part of the Qt > framework. > > This has caused performance issues, rendering issues with remote desktop > sessions, keyboard navigation issues and more. It probably accounts for 25% > or more of the bugs reports we deal with. > > Unfortunately, whilst there are alternatives to Qt for this purpose, none > that we've found are mature enough for our purposes, and would require a > significant amount of effort to add the features we would need to support > pgAdmin. > > I've therefore been experimenting with another approach in which pgAdmin > is rendered in a regular web browser when running in desktop mode. Like > some other similar applications, a server process is launched and lives in > the system tray, from where it can be shutdown at any time, or new windows > opened. When it is first started, it will launch a browser window to render > pgAdmin automatically. If additional instances are launched, the previously > running instance will be re-used to avoid wasting resources. > > This is a proof of concept at the moment, for which I would appreciate any > feedback. Windows and Mac builds can be found here: > > https://developer.pgadmin.org/~dpage/runtime-revamp/ > > and the GIT branch can be found here: > > https://git.postgresql.org/gitweb/?p=pgadmin4.git;a= > shortlog;h=refs/heads/runtime-revamp > > Thanks! > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
