I feel like I need to add some perspective here. pgAdminIII is version 1.20, while pgAdmin4 is version 1.1. That means that pgAdminIII **should** be a much more mature product than pgAdmin4. pgAdminIII has limitations that could not be addressed without a total re-write, and is based on older technologies. pgAdmin4, being much newer, is going to be lacking features and have bugs and glitches in it. I don’t think anyone is suggesting that you can give up using pgAdminIII and use pgAdmin4 for all of your PG administrative activities at this time. It took years to get pgAdminIII to the point it is now — to expect pgAdmin4 to be as solid and complete after less than a year in full release is unrealistic.
Regarding the comments about choice of technologies, the development team no doubt made some tough decisions that involve tradeoffs (there are ALWAYS tough decisions to be made when planning a new product). Clearly, one of the tradeoffs they made was for single-source/mult-platform vs. multi-source/multi-platform. I imagine that was made based upon the available manpower. Don’t expect the level of resources to be put into pgAdmin4 that would be put into a commercial product — remember that you are not paying for pgAdmin4, and that the developers are volunteers. The nature of open-source is that you can clone and change anything you like, so if you are that down on jQuery, feel free to clone the project and substitute whatever alternative you wish. If you are successful in doing so and create a web product with a better UX, I’m sure the team will be grateful and accept your pull requests. Or for that matter, clone the pgAdminIII project and fix whatever is needed to keep it alive. I don’t mean this in a nasty way, but nobody is forcing you to use pgAdmin4. The nature of open source is choice, and that’s a good thing. Don’t misinterpret this as suggesting that we shouldn’t talk about the shortcomings and question the technology choices of pgAdmin4. But let’s do it in a spirit of positivity and progress, not as complaints and put-downs. For example, if you think jQuery is a poor choice for UX, what would you recommend as an alternative, and how would you recommend migrating to that alternative? Finally, to Dave and the other developers, I know you know this, but for every user who complains about things that really can’t be changed, there are a dozen who are thrilled that you are contributing your time for a project that benefits the entire Postgres community. I know that you take great pride in making pgAdmin the best it can be and will continue to do so. Your efforts are appreciated. Happy New Year > On Dec 26, 2016, at 9:16 AM, Dave Page <dp...@pgadmin.org> wrote: > > With respect, your email did not ask anything about helping out with the > project - you thanked me for my work on the project, and then told me that > jQuery wasn't stable and was a bad choice for pgAdmin. I haven't replied yet > as I'm on vacation and only sporadically reading email. > > Whilst I respect any informed opinions about our work, people will always > disagree occasionally. I did a lot of research before choosing the > technologies we use, including consulting with a number of people I know who > are very experienced web developers, and none of them suggested using > anything other than jQuery. At this point, changing that would be near > impossible as it's so heavily used. > > As you can imagine, a project as large as pgAdmin 4 is bound to have issues > that get missed despite our best efforts at QA (as well as some we deem > acceptable to meet our timelines). We're continuing to invest significant > amounts of developer time to further improve the application, and are > prioritising issues (and missing features) requested by users in the field. > You can follow the progress we're making on the pgadmin-hackers mailing list, > or by checking the commits to the git repository. > > We're happy for users to contribute to the project. If you wish to work on > bugs or features, you can find them listed on the tracker at > https://redmine.postgresql.org/projects/pgadmin4/issues > <https://redmine.postgresql.org/projects/pgadmin4/issues>. Obviously we > prefer people to work on tickets based on their target version and priority, > but you are free to contribute as you see fit. All we ask is that you let us > know if you're working on something to avoid duplicated effort, and for new > features, propose your design on the mailing list to ensure we're happy with > the direction you intend to take. > > Regards, Dave > > On Monday, December 26, 2016, Irina Mileva <imil...@transfermate.com > <mailto:imil...@transfermate.com>> wrote: > Hi Melvin, > > Thank you for your email. I am honoured to meed you. I am still using pgAdmin > 3 as well. It is a matter of time for it to stop working as expected. My > prays are with pgadmin. It is the best visual perspective of PostgreSql. > The whole idea of web based db manager is a bit incomplete... jQuery can not > be used for serious and long term supported projects. I am a web developer > and this is based on my practice... > No matter what is my opinion I still want to support pgadmin 4. I can deliver > some qa test, there is no time to develop my self. However I tried to contact > Dave Page and other supporters. No one gives me a procedure how to > participate to the project... I am just sharing my pain :-) Do not want you > to take from your time. > Wishing you happy holidays. > > Kind regards, > Irina > > Sent with AquaMail for Android > http://www.aqua-mail.com <http://www.aqua-mail.com/> > > On 26 декември 2016 г. 16:25:11 Melvin Davidson <melvin6...@yahoo.com > <javascript:;>> wrote: > > Irina, > > I am not PgAdmin support. I am a retired DBA. I happen to agree with you that > PgAdmin4 is not ready for prime time. It is slow and lacks many of the > features in PgAdmin3, in addition a few of the features it does have do not > work. For that reason I continue to use PgAdmin3. That being said, I have > replied back to Marcin that I believe the reason his pg_restore is not > working is because his dbname is CamelCase. I suggested he use the command > line version of pg_restore and look in postgres log for any errors. Since > then I have not heard back from him. > > Melvin Davidson > I reserve the right to fantasize. Whether or not you > wish to share my fantasy is entirely up to you. > [http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif > <http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif>] > www.youtube.com/unusedhero/videos <http://www.youtube.com/unusedhero/videos> > Folk Alley - All Folk - 24 Hours a day > www.folkalley.com <http://www.folkalley.com/> > > > > ________________________________ > From: Irina Mileva <imil...@transfermate.com <javascript:;>> > To: "pgadmin-support@postgresql.org <javascript:;>" > <pgadmin-support@postgresql.org <javascript:;>> > Sent: Monday, December 26, 2016 8:45 AM > Subject: Re: [pgadmin-support] Restoring Db > > Data base restore is not working long time ago. PgAdmin 4 sounds more like a > sabotage the project as well. > I can support pgadmin 3 and 4 with a professional QA support. Hope someone > will answer me this time. > > Sent with AquaMail for Android > http://www.aqua-mail.com > <http://www.aqua-mail.com/><http://www.aqua-mail.com/ > <http://www.aqua-mail.com/>> > > > On 24 декември 2016 г. 6:30:23 Marcin Bienias <marcin.bien...@hotmail.com > <javascript:;><mailto:marcin.bien...@hotmail.com <javascript:;>>> wrote: > > > pgAdmin 3 v1.22.2 > > MacOS Sierra 10.12.1 > > > > After instaling few time when i try to restore database i can’t do that. > > I chose .tar file but i can’t use restore button. its grey and don’t work. > > -- > > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org > > <javascript:;><mailto:pgadmin-support@postgresql.org <javascript:;>>) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgadmin-support > > <http://www.postgresql.org/mailpref/pgadmin-support> > > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org > <javascript:;><mailto:pgadmin-support@postgresql.org <javascript:;>>) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support > <http://www.postgresql.org/mailpref/pgadmin-support> > > > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org > <javascript:;>) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support > <http://www.postgresql.org/mailpref/pgadmin-support> > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com <http://pgsnake.blogspot.com/> > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com <http://www.enterprisedb.com/> > The Enterprise PostgreSQL Company >
