Dave,
I am in favor of "version number to 3.0 for the next release".
Melvin Davidson 🎸
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com
On Thursday, February 1, 2018, 9:46:00 AM EST, Dave Page
<dp...@pgadmin.org> wrote:
So there's been nothing but positive feedback about the PoC revamped runtime I
asked folks on the lists to test. Thank you to everyone that did so.
With that in mind, I think we should use that in the next version and moving
forwards, and bump the version number to 3.0 for the next release. Does anyone
object to that plan?
FYI, since the original PoC, I've made the following additional changes:
- Move to using a shared memory interlock to ensure only a single instance (per
user, per copy of the executable) is run. This means if you have multiple
copies of pgAdmin installed, they won't interact with each other, but a single
copy is limited to a single instance per user.
- Add a log viewer. If startup fails (or other errors occur), the Python logs
can now easily be viewed in the runtime.
- Tidied up the configuration dialogue.
- Added a config option to allow an alternate command to be run rather than
executing the default browser. This allows any browser to be configured, using
different profiles etc, as possible when launching on the command line.
- Made startup more robust so config options can be corrected without restarts
if needed, and failures can be detected much more quickly.
- Cleaned up a bunch of redundant code.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
