RE: Request to code on pgAdmin II - Mailing list pgadmin-hackers
From | dpage@vale-housing.co.uk |
---|---|
Subject | RE: Request to code on pgAdmin II |
Date | |
Msg-id | 200108122015.f7CKFSN07637@mailgate.vale-housing.co.uk Whole thread Raw |
In response to | Request to code on pgAdmin II (Bryan Cross <bryan@tresperros.net>) |
List | pgadmin-hackers |
Hi Bryan, We'd welcome any input you can give to the pgAdmin II project. I don't know how you found out about it though, I've only announced the project on the pgadmin-hackers@greatbridge.org list! Anyway incase you are not on that list and just stumbled across thhe new site, here's some background: The new codebase was made public only a few days ago. It is based on months of hard work on my part and is still very new. Currently the only specs more detailed than you've found are in my head - in fact things like the Migration Wizard can't even be started yet as I haven't built the Plugin support yet (that'll be later this week). Anyway, to get to the point, I intend to write the initial code for the migration wizard myself based on my experience with the old pgAdmin - of course I'm always open to any suggestion re the design. The version control is another matter though if you want to look into it. Some thoughts I had had; - vc should be enabled per database - all appropriate pgXxx classes in pgSchema should have a Versions collection. This will be a collection on the same class, but without add/drop/edit methods, writable properties or another Versions collection. - vc should be implemented in pgSchema, which should autodetect if it's enabled. Rollback methods must be included. - data storage should be in the db, in the minimum no. of tables possible which pgSchema must maintain/upgrade/self repair. All object versions should include uid, timestamp & version no. as well as *all* properties of the object. Does that sound like something you'd like to look at? As for the vb6 thing, yes, we are standardising on it (there's already about 15k lines of code!), but will look at vb7 when it comes out. It is possible that plugins or exporters could be written in other languages I presume, but I've not tried it myself. Regards, Dave. --------------Replied message-------------- Date: Sun, 12 Aug 2001 08:53:22 -0700 From: Bryan Cross <bryan@tresperros.net> Sender: pgadmin-hackers-owner@postgresql.org To: pgadmin-hackers@postgresql.org Reply-To: bryan@tresperros.net Subject: [pgadmin-hackers] Request to code on pgAdmin II Message-ID: <01081208532204.05173@panzerpup> Hi folks, This is my first ever effort at participating in an open-source project, so please forgive my naivete. I'd like to work on one of the issues listed in the To Do list, specifically import wizards (say from Oracle, Access, and/or mySQL), and the Projects/Version control issues. I need some help, though, in understanding exactly what we're supposed to do. Is there anything analagous to a spec floating around to help me understand what functionality is desired? Also, are we standardized on VB6? etc. etc. If there's a developers handbook, FAQ, or something like that I would be very grateful if someone could point me to it ;) Also, I can't seem to find this newsgroup on any news server... any hints? Thanks to all of you for your help ;) Bryan Cross ---------------------------(end of broadcast)---------------- ----------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
pgadmin-hackers by date: