Re: Proposal: Drop support for Internet Explorer
If its hard to know how many people are actually using Internet Explorer: You could make the next release of pgAdmin display a message occasionally to users of Internet Explorer saying that Internet Explorer will no longer be officially supported in a future version, and when that version comes the message says now no longer supported. You can then see how many people contact you about this to express concern. -- Darren Duncan
Re: Proposal: Drop support for Internet Explorer
The patch looks good as much as I understand it, but this raises an important question: How should one best handle minority browsers that may be completely modern but you may not specifically know about them? Such as the newer crop of browsers that emphasize stronger privacy or may have fewer identifiers? While going on a whitelist as the patch essentially does for known good browsers is conservative, I feel that an alteration would be good. I propose dividing the browsers/environments into 3 categories, which are recognized-supported, recognized-unsupported, and unrecognized. So the unsupported older versions of supported browsers get a stronger message encouraging a browser switch as they are recognized as unsupported, while unrecognized browsers get a different weaker message saying they weren't recognized so we can't determine if they'd work; both can point to the list of known supported browsers. Related to this, there could be an application toggle that affects the unrecognized category where users can basically say, yes I understand you don't recognize this browser, please hide the warning, or something like that. Also, it probably goes without saying, but the code/templates will need to be structured in such a way that the warning message uses about plain as possible HTML so that if the browser doesn't support displaying the UI in general it can at least display the message. -- Darren Duncan On 2020-04-09 4:36 a.m., Dave Page wrote: Hi On Thu, Apr 9, 2020 at 12:26 AM Darren Duncan wrote: If its hard to know how many people are actually using Internet Explorer: You could make the next release of pgAdmin display a message occasionally to users of Internet Explorer saying that Internet Explorer will no longer be officially supported in a future version, and when that version comes the message says now no longer supported. You can then see how many people contact you about this to express concern. Good idea. I've hacked up a patch to warn users if they're using a deprecated or unsupported browser. CCing Akshay for a review :-) -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: Proposal: Drop support for Internet Explorer
You have a typo `elif browser != 'chrom'` but otherwise I see no problems with
the patch, thank you. -- Darren Duncan
On 2020-04-14 7:46 a.m., Dave Page wrote:
Ooops. Thanks for catching that. Here it is.
On Tue, Apr 14, 2020 at 3:45 PM Neel Patel <mailto:neel.pa...@enterprisedb.com>> wrote:
Hi Dave,
Looks like patch is missing in attachment.
Thanks,
Neel Patel
On Tue 14 Apr, 2020, 6:53 PM Dave Page, mailto:dp...@pgadmin.org>> wrote:
Here's an updated patch that gives a slightly different message if the
browser is unknown vs. unsupported/deprecated. As with the previous
patch, the check can be disabled in the config.
On Fri, Apr 10, 2020 at 5:07 AM Khushboo Vashi
mailto:khushboo.va...@enterprisedb.com>> wrote:
On Thu, Apr 9, 2020 at 11:57 PM Darren Duncan
mailto:dar...@darrenduncan.net>> wrote:
The patch looks good as much as I understand it, but this raises
an important
question:
How should one best handle minority browsers that may be
completely modern but
you may not specifically know about them? Such as the newer
crop of browsers
that emphasize stronger privacy or may have fewer identifiers?
While going on a whitelist as the patch essentially does for
known good browsers
is conservative, I feel that an alteration would be good.
I propose dividing the browsers/environments into 3 categories,
which are
recognized-supported, recognized-unsupported, and unrecognized.
So the unsupported older versions of supported browsers get a
stronger message
encouraging a browser switch as they are recognized as
unsupported, while
unrecognized browsers get a different weaker message saying they
weren't
recognized so we can't determine if they'd work; both can point
to the list of
known supported browsers.
I do agree with this suggestion.
Related to this, there could be an application toggle that
affects the
unrecognized category where users can basically say, yes I
understand you don't
recognize this browser, please hide the warning, or something
like that.
Also, it probably goes without saying, but the code/templates
will need to be
structured in such a way that the warning message uses about
plain as possible
HTML so that if the browser doesn't support displaying the UI in
general it can
at least display the message.
-- Darren Duncan
On 2020-04-09 4:36 a.m., Dave Page wrote:
> Hi
>
> On Thu, Apr 9, 2020 at 12:26 AM Darren Duncan wrote:
>
> If its hard to know how many people are actually using
Internet Explorer:
>
> You could make the next release of pgAdmin display a
message occasionally to
> users of Internet Explorer saying that Internet Explorer
will no longer be
> officially supported in a future version, and when that
version comes the
> message says now no longer supported.
>
> You can then see how many people contact you about this
to express concern.
>
>
> Good idea. I've hacked up a patch to warn users if they're
using a deprecated or
> unsupported browser.
>
> CCing Akshay for a review :-)
>
> --
> 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
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Re: Drop Python 2 support in pgAdmin?
On 2020-04-24 5:50 a.m., Dave Page wrote: Python 2 has been unsupported for a few months now. Does anyone object to dropping Python 2 support in pgAdmin? This primarily affects our Python package - other installers and packages all use Python 3 I believe. I know that Apple at least is pushing that if any products depend on Python or other dynamic language runtimes they should be bundling the runtime with the app and not expecting the system to provide it. And in that case, bundle whatever version you want, probably the very latest Python. Further to this, Apple has deprecated that it is bundling these things with the MacOS. -- Darren Duncan
Re: 64bit only for Windows?
In my opinion, the computer industry is well past the point that it should be making active efforts to support 32-bit. Being able to still run old unsupported 32-bit software on a modern machine still has a lot of value, but still explicitly supporting 32-bit hardware with new software has no real value, except maybe if the software is for certain tiny embedded devices. All modern PCs have been 64-bit for at least 15 years now. -- Darren Duncan On 2020-05-22 5:06 a.m., Dave Page wrote: We currently build pgAdmin as a 32 bit application on Windows. This is getting harder and harder as more of our dependencies are becoming 64bit focussed or even 64bit only. Does anyone actually require 32bit Windows support, or could we move to 64 bit?
