Thread: Work on pgAdmin3
At the moment, there seems to be not much work in progress on pgAdmin3? I'd like to contribute, at the moment I got enough time to implement the raw schema browsing. I already have a SQL query window running. I'd need to modify a lot of files, so cvs access would be necessary. Regards, Andreas
Hi Andreas, > -----Original Message----- > From: Andreas Pflug [mailto:Andreas.Pflug@web.de] > Sent: 27 March 2003 01:49 > To: pgadmin-hackers@postgresql.org > Subject: [pgadmin-hackers] Work on pgAdmin3 > > > At the moment, there seems to be not much work in progress on > pgAdmin3? Unfortunately my time is limited right now as I've gone back to University to do some post-grad studies, but am still working full time as well. > I'd like to contribute, at the moment I got enough > time to implement the > raw schema browsing. I already have a SQL query window > running. Excellent. Any contributions would be gratefully received... > I'd need to modify a lot of files, so cvs access > would be necessary. I'm happy to grant CVS write access, but as I'm sure you understand, I'll need to see at least a couple of good quality patches of reasonable size submitted before doing so. Anonymous CVS access is available at :pserver:anonymous@cvs.pgadmin.org:/disk1/cvsroot though currently our ISP has screwed up our connection so access may be a bit messed up whilst they reinstall our connection :-( Regards, Dave.
Hi Dave, what I'm doing now can't be possibly called a patch... You won't hear from me in this list until pgAdmin3 can browse and execute as pgAdmin2 does.... I'll be back soon. Regards, Andreas Dave Page wrote: >Excellent. Any contributions would be gratefully received... > > >I'm happy to grant CVS write access, but as I'm sure you understand, >I'll need to see at least a couple of good quality patches of reasonable >size submitted before doing so. > > >
> -----Original Message----- > From: Andreas Pflug [mailto:Andreas.Pflug@web.de] > Sent: 27 March 2003 11:10 > To: Dave Page; pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Work on pgAdmin3 > > > Hi Dave, > > what I'm doing now can't be possibly called a patch... You won't hear > from me in this list until pgAdmin3 can browse and execute as > pgAdmin2 > does.... OK, that's an ambitious statement. I'll look forward to seeing the results. Still as I said, I'm not prepared to give out CVS write access upon request - I doubt very much you will find any serious project that does. I would also suggest that you do keep the list up to date on any work you are doing. There are other people working on their own copies of the code, and it is possible that I will find time to do so again once the new financial year starts. The last thing any of us would want is duplication of effort. In your new design, have you considered the cacheing issues that Keith & I discussed recently? Regards, Dave.
Dave Page wrote: >OK, that's an ambitious statement. I'll look forward to seeing the >results. > I'll send you something as soon as it works > >Still as I said, I'm not prepared to give out CVS write access upon >request - I doubt very much you will find any serious project that does. > Sure. > >I would also suggest that you do keep the list up to date on any work >you are doing. There are other people working on their own copies of the >code, and it is possible that I will find time to do so again once the >new financial year starts. The last thing any of us would want is >duplication of effort. > If someone's doing something right now, we probably will do duplicates, as I implement the whole tree with slight redesigns (no tvXXX or svXXX, virtual functions instead to keep frmMain/browser.cpp smaller). > >In your new design, have you considered the cacheing issues that Keith & >I discussed recently? > > I'm tracking this list since Jan 24, haven't seen something about cacheing. Did I miss it? Regards, Andreas
> -----Original Message----- > From: Andreas Pflug [mailto:Andreas.Pflug@web.de] > Sent: 27 March 2003 11:36 > To: Dave Page; pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] Work on pgAdmin3 > > > I'm tracking this list since Jan 24, haven't seen something about > cacheing. Did I miss it? > It was in amongst a bunch of other subjects in one email thread between me & Keith. Basically, in pgAdmin II, pgschema provides a single object hierarchy that can be used by all parts of pgadmin. This meant that as the hierarchy was built on demand, it happened for any part of the application that accessed it. The difficult bit was synchronising the pgschema hierarchy with the treeview. In pgAdmin III, that problem doesn't exist because the object hierarchy is maintained by the treeview which stores each object as a class derived from wxTreeItemData (iirc). However, this method relies on the user to click the treeview to build the hierarchy, so something like Keith's QBE tool cannot use the hierarchy to find available tables/views etc because they may not be there if the user hasn't browsed to them. This of course also applies to other dialogues that may provide lists of objects, such as create operator, create function etc etc. I have yet to figure out a solution (other than return to the old style design), and I'm guessing Keith hasn't either as he hasn't said so. Regards, Dave.