Обсуждение: Java GUI development
Hi folks, There is some discussion on hackers about the creation of a cross-platform gui for postgres ala pgAdmin2, or pgaccess. Is there anyone interested in collaborating on a Java GUI. I am fairly confident I could handle the low end server interface to the tables, but am looking for someone with swing skills Dave
It is a great idea to have a cross-platform's PostgreSQL client on top of PostgreSQL JDBC. Based on my experience, a Swing application can be very bulky and slow, or slim and fast. The quality of the application is largely depended on the developers' skill level. The PointBase(www.pointbase.com) has a very nice Java client. We may learn something from it. I can get involved in the project. I, however, can't commit a lot of time on it since I am very busy on my own project. 6/6/2002 12:24:38 AM, Dave Cramer <Dave@micro-automation.net> wrote: >Hi folks, > >There is some discussion on hackers about the creation of a >cross-platform gui for postgres ala pgAdmin2, or pgaccess. > >Is there anyone interested in collaborating on a Java GUI. I am fairly >confident I could handle the low end server interface to the tables, but >am looking for someone with swing skills > >Dave > > > > > >---------------------------(end of broadcast)--------------------------- >TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
On Wed, 2002-06-05 at 18:24, Dave Cramer wrote: > There is some discussion on hackers about the creation of a > cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > Is there anyone interested in collaborating on a Java GUI. I am fairly > confident I could handle the low end server interface to the tables, but > am looking for someone with swing skills I'm not up to that quite yet but you got an alpha/beta tester and ergonomics pain in the neck. I might be talked in to doing some graphics too if needed. Cheers Tony Grant -- RedHat Linux on Sony Vaio C1XD/S http://www.animaproductions.com/linux2.html Macromedia UltraDev with PostgreSQL http://www.animaproductions.com/ultra.html
On Wed, 2002-06-05 at 18:24, Dave Cramer wrote: > There is some discussion on hackers about the creation of a > cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > Is there anyone interested in collaborating on a Java GUI. I am fairly > confident I could handle the low end server interface to the tables, but > am looking for someone with swing skills I like the idea of a good Java interface for Pg. I'm not a swing master or anything, but I have written a couple things in it. In the near future, I will be writing a bunch of swing programs on Mac OS X, so I may be able to help out as I get better. I can also test on Linux and Mac OS X. Will there be future discussion on [JDBC] or should I subscribe to [HACKERS] (or should we create another list)? --Jeremy
> Is there anyone interested in collaborating on a Java GUI. That's been on my 'possible projects' list, so I may be interested in contributing. I've also been playing with some Tomcat JSP tags that may be a good complement to this project. The goal of these tags is to make it easy to write "am I sane?" views of the database - basically a dump of each table, but with links so that you can easily navigate between the tables. E.g., if table foo has a foreign reference to table bar, then each row in foo should have a link that shows the corresponding entry in bar. Contrawise, it would be nice if each row in bar had a link that brought up all rows that accessed it. (Then there's those graphing applets that could show relationships between tables, and.... okay, I'll stop drooling now.) JSP may be a good prototype tool for a standalone application. It allows formatting to be quickly changed, so people can try out different approaches, and the "input" could be handled by JSP that catches forms. > I am fairly > confident I could handle the low end server interface to the tables, but > am looking for someone with swing skills I think one of the desireable goals of this type of project is as a demonstration of how to access the database through Java, and thus the project should use JDBC unless something entirely outside of its interface is required. This also helps make the application thin and fast, since it's not doing much beyond constructing JDBC queries and formatting the results. Bear
I also thought about having a JSP PostgreSQL front-end using JSTL. The implement shall be straight forward and can be done in a very short period of time. The only problem is the users need a Java Web container to run it. 6/6/2002 3:15:12 AM, Bear Giles <bgiles@coyotesong.com> wrote: >> Is there anyone interested in collaborating on a Java GUI. > >That's been on my 'possible projects' list, so I may be interested >in contributing. I've also been playing with some Tomcat JSP tags >that may be a good complement to this project. The goal of these >tags is to make it easy to write "am I sane?" views of the database - >basically a dump of each table, but with links so that you can easily >navigate between the tables. > >E.g., if table foo has a foreign reference to table bar, then each >row in foo should have a link that shows the corresponding entry in >bar. Contrawise, it would be nice if each row in bar had a link >that brought up all rows that accessed it. (Then there's those >graphing applets that could show relationships between tables, and.... >okay, I'll stop drooling now.) > >JSP may be a good prototype tool for a standalone application. >It allows formatting to be quickly changed, so people can try out >different approaches, and the "input" could be handled by JSP >that catches forms. > >> I am fairly >> confident I could handle the low end server interface to the tables, but >> am looking for someone with swing skills > >I think one of the desireable goals of this type of project is as >a demonstration of how to access the database through Java, and >thus the project should use JDBC unless something entirely outside >of its interface is required. This also helps make the application >thin and fast, since it's not doing much beyond constructing JDBC >queries and formatting the results. > >Bear > >---------------------------(end of broadcast)--------------------------- >TIP 3: if posting/reading through Usenet, please send an appropriate >subscribe-nomail command to majordomo@postgresql.org so that your >message can get through to the mailing list cleanly >
Bear, I had sort of been thinking about not using the JDBC API for this, but you make a good point of it being a reference application for JDBC. I did intend to use the driver code, but more of the lowlevel stuff for speed reasons. One of the problems the driver has is that it fetches the entire query before returning which could be problematic. I kind of like the idea of some sort of cache for the query if it is large. Something along the idea of a lazy load, where we would initially return the first couple of pages, and then if the user scrolled down we would fetch another couple of pages. If it were "really smart" it would only keep a window of information in memory. That being said this may be an opportunity to make the driver better too! RE JSP tags: I personally favour templating tools like velocity, or webmacro over jsp, but that's my personal taste (you can read the arguments on www.servlets.com and form your own opinions). I do however see the possiblity of writing the code so that it could be either a web application, or a GUI application. I think that is a real attainable goal using java. Notionally the idea would be as follows: The database is more or less object oriented as it is, ie pg_tables, pg_trigger, pg_index, etc. can all be easily modelled as objects. So the entire structure of the db can be loaded and accessed, by either the gui, jsp, or templating code. Thoughts? Dave On Wed, 2002-06-05 at 15:15, Bear Giles wrote: > > Is there anyone interested in collaborating on a Java GUI. > > That's been on my 'possible projects' list, so I may be interested > in contributing. I've also been playing with some Tomcat JSP tags > that may be a good complement to this project. The goal of these > tags is to make it easy to write "am I sane?" views of the database - > basically a dump of each table, but with links so that you can easily > navigate between the tables. > > E.g., if table foo has a foreign reference to table bar, then each > row in foo should have a link that shows the corresponding entry in > bar. Contrawise, it would be nice if each row in bar had a link > that brought up all rows that accessed it. (Then there's those > graphing applets that could show relationships between tables, and.... > okay, I'll stop drooling now.) > > JSP may be a good prototype tool for a standalone application. > It allows formatting to be quickly changed, so people can try out > different approaches, and the "input" could be handled by JSP > that catches forms. > > > I am fairly > > confident I could handle the low end server interface to the tables, but > > am looking for someone with swing skills > > I think one of the desireable goals of this type of project is as > a demonstration of how to access the database through Java, and > thus the project should use JDBC unless something entirely outside > of its interface is required. This also helps make the application > thin and fast, since it's not doing much beyond constructing JDBC > queries and formatting the results. > > Bear > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > >
Dave Cramer wrote: > One of the problems the driver has is that it fetches the > entire query before returning which could be problematic. One of the features I want to add for 7.3 is the ability to use server side cursors to allow partial fetches of results. The default would be to fetch everything as it does now, but by calling Statement.setFetchSize() you would enable the new functionality. So instead of directly issuing the query 'select foo from bar' as the driver does today, the driver would do the following after a call of setFetchSize(10): declare cursor1 cursor for select foo from bar; fetch forward 10 from cursor1; only the first 10 rows would be buffered. Then if more were needed additional 'fetch forward 10 from cursor1;' calls would be made to get more rows. thanks, --Barry
> One of the problems the driver has is that it fetches the > entire query before returning which could be problematic. I kind of like > the idea of some sort of cache for the query if it is large. Something > along the idea of a lazy load, where we would initially return the first > couple of pages, and then if the user scrolled down we would fetch > another couple of pages. If it were "really smart" it would only keep a > window of information in memory. That being said this may be an > opportunity to make the driver better too! Which, recursively, is why the application should use JDBC if possible. Nothing improves a driver like having an application pushing it, and vice versa. > writing the code so that it could be either a web > application, or a GUI application. I think that is a real attainable > goal using java. I think this could be handled by creating an explicit beans layer, with iterators (cursors) supporting lazy loads, and then swing, JSP, and whatever just use that layer as much as possible.
I just read Tony's comments regarding jsp, and my first reaction was similar to his (who needs it?), but on second thought, it seems so simple to leave the hooks in there for *any* presentation method that we'd be silly not to design with this in mind. > I think this could be handled by creating an explicit beans layer, > with iterators (cursors) supporting lazy loads, and then swing, > JSP, and whatever just use that layer as much as possible. I agree with Bear- essentially, if we work carefully in a MVC framework, then the "V" could be swing, jsp, velocity, etc... I'd suggest building the swing version first, but with good design we won't be limited to that in the long run- it will be a foundation that others can build on if they want a different View. -Nick
On Wednesday, June 5, 2002, at 12:05 PM, Dave Cramer wrote: > > I will setup the project on sf.net, anyone have a suggestion for a name? > > My off the cuff idea is jPGAdmin, not very inventive ;( > Javagres JavaPg JadPg [Java ADmin Pg...stretching on that one] JadePg [Java ADmin Environment for Pg] And my personal fav from my friend in the Intel marketing dept.: "Emo-tanium" ;-) --Jeremy
On Wed, Jun 05, 2002 at 12:24:38PM -0400, Dave Cramer wrote: > Hi folks, > > There is some discussion on hackers about the creation of a > cross-platform gui for postgres ala pgAdmin2, or pgaccess. I've been working on a tool that will run as a servlet or Swing GUI and that will (in theory) use any JDBC driver to connectto the database and manipulate stuff. I released a servlet-based version some time ago that supported PostgreSQL andMySQL officially. Since then I've been rewriting the code so that a Swing version can be easily added, sharing commonlibrary code with the servlet version. I'm a bit busy with exams coming up and I haven't had a lot of time to work on stuff recently. I've almost finished the servletstuff using the new code, and the swing stuff is half-done. You might want to look at the old version (the last release) at http://javatator.com/ Are you thinking of a PostgreSQL-specific GUI, or is Javatator something that you people might want to help with? If you're interested, let me know and I'll try and get CVS up so you can peek at the works. I've got exams from 14th-27thJune so I won't be able to code a whole lot from now until then :-) Oh, and it's all open-source BTW :-) --Jase Jason Davies
Hi, I don't know whether you would think this relevant, but http://www.melati.org/ is an http based cross-platform interface to Postgresql (also MySQL, McKoiDB, HSQLDB). It currntly uses either Velocity or Webmacro for the HTML templating engine. It should be relatively easy to replace the template from tend with swing components, though it is outside my competance. The Persistent Object Engine (POEM) is industrial strength. Hope this is not too irrelevant. cheers Tim P On Wednesday 05 June 2002 03:10, Vernon Wu wrote: > It is a great idea to have a cross-platform's PostgreSQL client on top of > PostgreSQL JDBC. Based on my experience, a Swing application can be very > bulky and slow, or slim and fast. The quality of the application is largely > depended on the developers' skill level. The PointBase(www.pointbase.com) > has a very nice Java client. We may learn something from it. > > I can get involved in the project. I, however, can't commit a lot of time > on it since I am very busy on my own project. > > 6/6/2002 12:24:38 AM, Dave Cramer <Dave@micro-automation.net> wrote: > >Hi folks, > > > >There is some discussion on hackers about the creation of a > >cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > > >Is there anyone interested in collaborating on a Java GUI. I am fairly > >confident I could handle the low end server interface to the tables, but > >am looking for someone with swing skills > > > >Dave > > > > > > > > > > > >---------------------------(end of broadcast)--------------------------- > >TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly
On Wednesday 05 June 2002 04:31, Vernon Wu wrote: > I also thought about having a JSP PostgreSQL front-end using JSTL. The > implement shall be straight forward and can be done in a very short period > of time. The only problem is the users need a Java Web container to run it. Eugh, not JSP! http://www.melati.org/ (CVS version) ships with Jetty which is small and light. cheers Tim P > > 6/6/2002 3:15:12 AM, Bear Giles <bgiles@coyotesong.com> wrote: > >> Is there anyone interested in collaborating on a Java GUI. > > > >That's been on my 'possible projects' list, so I may be interested > >in contributing. I've also been playing with some Tomcat JSP tags > >that may be a good complement to this project. The goal of these > >tags is to make it easy to write "am I sane?" views of the database - > >basically a dump of each table, but with links so that you can easily > >navigate between the tables. > > > >E.g., if table foo has a foreign reference to table bar, then each > >row in foo should have a link that shows the corresponding entry in > >bar. Contrawise, it would be nice if each row in bar had a link > >that brought up all rows that accessed it. (Then there's those > >graphing applets that could show relationships between tables, and.... > >okay, I'll stop drooling now.) > > > >JSP may be a good prototype tool for a standalone application. > >It allows formatting to be quickly changed, so people can try out > >different approaches, and the "input" could be handled by JSP > >that catches forms. > > > >> I am fairly > >> confident I could handle the low end server interface to the tables, but > >> am looking for someone with swing skills > > > >I think one of the desireable goals of this type of project is as > >a demonstration of how to access the database through Java, and > >thus the project should use JDBC unless something entirely outside > >of its interface is required. This also helps make the application > >thin and fast, since it's not doing much beyond constructing JDBC > >queries and formatting the results. > > > >Bear > > > >---------------------------(end of broadcast)--------------------------- > >TIP 3: if posting/reading through Usenet, please send an appropriate > >subscribe-nomail command to majordomo@postgresql.org so that your > >message can get through to the mailing list cleanly > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html
Dave, Bear, I would really like you guys to look at http://www.melati.org/ as we have been round the houses with all these issues. cheers timp On Wednesday 05 June 2002 19:32, Dave Cramer wrote: > Bear, > > I had sort of been thinking about not using the JDBC API for this, but > you make a good point of it being a reference application for JDBC. I > did intend to use the driver code, but more of the lowlevel stuff for > speed reasons. One of the problems the driver has is that it fetches the > entire query before returning which could be problematic. I kind of like > the idea of some sort of cache for the query if it is large. Something > along the idea of a lazy load, where we would initially return the first > couple of pages, and then if the user scrolled down we would fetch > another couple of pages. If it were "really smart" it would only keep a > window of information in memory. That being said this may be an > opportunity to make the driver better too! > > RE JSP tags: I personally favour templating tools like velocity, or > webmacro over jsp, but that's my personal taste (you can read the > arguments on www.servlets.com and form your own opinions). I do however > see the possiblity of writing the code so that it could be either a web > application, or a GUI application. I think that is a real attainable > goal using java. > > Notionally the idea would be as follows: > > The database is more or less object oriented as it is, ie pg_tables, > pg_trigger, pg_index, etc. can all be easily modelled as objects. So the > entire structure of the db can be loaded and accessed, by either the > gui, jsp, or templating code. > > Thoughts? > > Dave > > On Wed, 2002-06-05 at 15:15, Bear Giles wrote: > > > Is there anyone interested in collaborating on a Java GUI. > > > > That's been on my 'possible projects' list, so I may be interested > > in contributing. I've also been playing with some Tomcat JSP tags > > that may be a good complement to this project. The goal of these > > tags is to make it easy to write "am I sane?" views of the database - > > basically a dump of each table, but with links so that you can easily > > navigate between the tables. > > > > E.g., if table foo has a foreign reference to table bar, then each > > row in foo should have a link that shows the corresponding entry in > > bar. Contrawise, it would be nice if each row in bar had a link > > that brought up all rows that accessed it. (Then there's those > > graphing applets that could show relationships between tables, and.... > > okay, I'll stop drooling now.) > > > > JSP may be a good prototype tool for a standalone application. > > It allows formatting to be quickly changed, so people can try out > > different approaches, and the "input" could be handled by JSP > > that catches forms. > > > > > I am fairly > > > confident I could handle the low end server interface to the tables, > > > but am looking for someone with swing skills > > > > I think one of the desireable goals of this type of project is as > > a demonstration of how to access the database through Java, and > > thus the project should use JDBC unless something entirely outside > > of its interface is required. This also helps make the application > > thin and fast, since it's not doing much beyond constructing JDBC > > queries and formatting the results. > > > > Bear > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@postgresql.org so that your > > message can get through to the mailing list cleanly > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
In fact, when JSTL is employed, not java scriptlet in JSP file at all, but tags. Let's concenter on the Java client for now. Worry others later. BTW, does Jetty ship with any DB you mentioned? 6/6/2002 7:37:01 AM, Tim Pizey <timp@paneris.org> wrote: >On Wednesday 05 June 2002 04:31, Vernon Wu wrote: >> I also thought about having a JSP PostgreSQL front-end using JSTL. The >> implement shall be straight forward and can be done in a very short period >> of time. The only problem is the users need a Java Web container to run it. > >Eugh, not JSP! >http://www.melati.org/ (CVS version) ships with Jetty which is small and >light. > >cheers >Tim P > > >> >> 6/6/2002 3:15:12 AM, Bear Giles <bgiles@coyotesong.com> wrote: >> >> Is there anyone interested in collaborating on a Java GUI. >> > >> >That's been on my 'possible projects' list, so I may be interested >> >in contributing. I've also been playing with some Tomcat JSP tags >> >that may be a good complement to this project. The goal of these >> >tags is to make it easy to write "am I sane?" views of the database - >> >basically a dump of each table, but with links so that you can easily >> >navigate between the tables. >> > >> >E.g., if table foo has a foreign reference to table bar, then each >> >row in foo should have a link that shows the corresponding entry in >> >bar. Contrawise, it would be nice if each row in bar had a link >> >that brought up all rows that accessed it. (Then there's those >> >graphing applets that could show relationships between tables, and.... >> >okay, I'll stop drooling now.) >> > >> >JSP may be a good prototype tool for a standalone application. >> >It allows formatting to be quickly changed, so people can try out >> >different approaches, and the "input" could be handled by JSP >> >that catches forms. >> > >> >> I am fairly >> >> confident I could handle the low end server interface to the tables, but >> >> am looking for someone with swing skills >> > >> >I think one of the desireable goals of this type of project is as >> >a demonstration of how to access the database through Java, and >> >thus the project should use JDBC unless something entirely outside >> >of its interface is required. This also helps make the application >> >thin and fast, since it's not doing much beyond constructing JDBC >> >queries and formatting the results. >> > >> >Bear >> > >> >---------------------------(end of broadcast)--------------------------- >> >TIP 3: if posting/reading through Usenet, please send an appropriate >> >subscribe-nomail command to majordomo@postgresql.org so that your >> >message can get through to the mailing list cleanly >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 5: Have you checked our extensive FAQ? >> >> http://www.postgresql.org/users-lounge/docs/faq.html >
Java Gui Builder http://jgb.sourceforge.net provides an easy (of-course after some learning :-) ) and flexible way to develop Swing GUI from reading an xml file. You may consider extending it to develop Postgres Client GUI Rajesh On Thursday 06 June 2002 05:18, you wrote: > Dave, Bear, > > I would really like you guys to look at http://www.melati.org/ > as we have been round the houses with all these issues. > > cheers > timp > > On Wednesday 05 June 2002 19:32, Dave Cramer wrote: > > Bear, > > > > I had sort of been thinking about not using the JDBC API for this, but > > you make a good point of it being a reference application for JDBC. I > > did intend to use the driver code, but more of the lowlevel stuff for > > speed reasons. One of the problems the driver has is that it fetches the > > entire query before returning which could be problematic. I kind of like > > the idea of some sort of cache for the query if it is large. Something > > along the idea of a lazy load, where we would initially return the first > > couple of pages, and then if the user scrolled down we would fetch > > another couple of pages. If it were "really smart" it would only keep a > > window of information in memory. That being said this may be an > > opportunity to make the driver better too! > > > > RE JSP tags: I personally favour templating tools like velocity, or > > webmacro over jsp, but that's my personal taste (you can read the > > arguments on www.servlets.com and form your own opinions). I do however > > see the possiblity of writing the code so that it could be either a web > > application, or a GUI application. I think that is a real attainable > > goal using java. > > > > Notionally the idea would be as follows: > > > > The database is more or less object oriented as it is, ie pg_tables, > > pg_trigger, pg_index, etc. can all be easily modelled as objects. So the > > entire structure of the db can be loaded and accessed, by either the > > gui, jsp, or templating code. > > > > Thoughts? > > > > Dave > > > > On Wed, 2002-06-05 at 15:15, Bear Giles wrote: > > > > Is there anyone interested in collaborating on a Java GUI. > > > > > > That's been on my 'possible projects' list, so I may be interested > > > in contributing. I've also been playing with some Tomcat JSP tags > > > that may be a good complement to this project. The goal of these > > > tags is to make it easy to write "am I sane?" views of the database - > > > basically a dump of each table, but with links so that you can easily > > > navigate between the tables. > > > > > > E.g., if table foo has a foreign reference to table bar, then each > > > row in foo should have a link that shows the corresponding entry in > > > bar. Contrawise, it would be nice if each row in bar had a link > > > that brought up all rows that accessed it. (Then there's those > > > graphing applets that could show relationships between tables, and.... > > > okay, I'll stop drooling now.) > > > > > > JSP may be a good prototype tool for a standalone application. > > > It allows formatting to be quickly changed, so people can try out > > > different approaches, and the "input" could be handled by JSP > > > that catches forms. > > > > > > > I am fairly > > > > confident I could handle the low end server interface to the tables, > > > > but am looking for someone with swing skills > > > > > > I think one of the desireable goals of this type of project is as > > > a demonstration of how to access the database through Java, and > > > thus the project should use JDBC unless something entirely outside > > > of its interface is required. This also helps make the application > > > thin and fast, since it's not doing much beyond constructing JDBC > > > queries and formatting the results. > > > > > > Bear > > > > > > ---------------------------(end of > > > broadcast)--------------------------- TIP 3: if posting/reading through > > > Usenet, please send an appropriate subscribe-nomail command to > > > majordomo@postgresql.org so that your message can get through to the > > > mailing list cleanly > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
Hi, We start such project with pgInhaler (pgInhaler.ifrance.com), for now we don't share source because of ugly code, but it can be a good start point for a new project... Test it, and tell us what you think about... Nicolas (and Olivier) > -----Message d'origine----- > De : pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc- > owner@postgresql.org] De la part de Dave Cramer > Envoyé : mercredi 5 juin 2002 18:25 > À : pgsql-jdbc@postgresql.org > Objet : [JDBC] Java GUI development > > Hi folks, > > There is some discussion on hackers about the creation of a > cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > Is there anyone interested in collaborating on a Java GUI. I am fairly > confident I could handle the low end server interface to the tables, but > am looking for someone with swing skills > > Dave > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
Hi Folks, First of all I'd like to say that I am pleasantly surprised by the number of people who have responded positively. Second I have created the project jpgadmin on sourceforge www.sf.net/projects/jpgadmin I have also created a mailing list there which should be active shortly. The list is jpgadmin-development@lists.sourceforge.net If you want to be a developer, then send me your username's on sf.net FWIW I did try to create the project on gborg.postgresql.org, but for some reason I couldn't edit some of the fields on the project sign up form. I think at this point we need a set of requirements, mine are replicate the functionality of pgadmin II, and or psql in a gui. ie be able to manipulate view/modify any table in the database. Future enhancements would include er diagrams, code generation using templates to name a few. I encourage everyone to think of what you want the tool to do. Dave
For now, let's use the jdbc list to communicate. The list at sourceforge is active so once everyone get's signed up on it, we can move the discussion over there. Dave
Which SF project is this? You're not talking about http://jgb.sourceforge.net, are you? That's the only one I can find mentioned in this thread, unless I missed it. Thanks, Jim Dave Cramer wrote: > For now, let's use the jdbc list to communicate. The list at sourceforge > is active so once everyone get's signed up on it, we can move the > discussion over there. > > Dave > > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > >
the project has been started as www.sf.net/projects/jpgadmin the mailing list is jpgadmin-development@lists.sourceforge.net Dave On Thu, 2002-06-06 at 09:42, Jim Caley wrote: > Which SF project is this? You're not talking about http://jgb.sourceforge.net, > are you? That's the only one I can find mentioned in this thread, unless I > missed it. > > Thanks, > Jim > > Dave Cramer wrote: > > For now, let's use the jdbc list to communicate. The list at sourceforge > > is active so once everyone get's signed up on it, we can move the > > discussion over there. > > > > Dave > > > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 6: Have you searched our list archives? > > > > http://archives.postgresql.org > > > > > > >
To sign up on the jpgadmin list go to http://lists.sourceforge.net/lists/listinfo/jpgadmin-development Dave On Thu, 2002-06-06 at 09:52, Dave Cramer wrote: > the project has been started as www.sf.net/projects/jpgadmin > the mailing list is jpgadmin-development@lists.sourceforge.net > > Dave > > On Thu, 2002-06-06 at 09:42, Jim Caley wrote: > > Which SF project is this? You're not talking about http://jgb.sourceforge.net, > > are you? That's the only one I can find mentioned in this thread, unless I > > missed it. > > > > Thanks, > > Jim > > > > Dave Cramer wrote: > > > For now, let's use the jdbc list to communicate. The list at sourceforge > > > is active so once everyone get's signed up on it, we can move the > > > discussion over there. > > > > > > Dave > > > > > > > > > > > > ---------------------------(end of broadcast)--------------------------- > > > TIP 6: Have you searched our list archives? > > > > > > http://archives.postgresql.org > > > > > > > > > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > >
Hi, We start such project with pgInhaler (pgInhaler.ifrance.com), for now we don't share source because of ugly code, but it can be a good start point for a new project... Test it, and tell me what you think about... Nicolas ( and Olivier ) > -----Message d'origine----- > De : pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc- > owner@postgresql.org] De la part de Dave Cramer > Envoyé : mercredi 5 juin 2002 18:25 > À : pgsql-jdbc@postgresql.org > Objet : [JDBC] Java GUI development > > Hi folks, > > There is some discussion on hackers about the creation of a > cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > Is there anyone interested in collaborating on a Java GUI. I am fairly > confident I could handle the low end server interface to the tables, but > am looking for someone with swing skills > > Dave
will the GUI be only for performing administrative tasks? --- Nicolas VERGER <nicolas@verger.net> wrote: > Hi, > We start such project with pgInhaler > (pgInhaler.ifrance.com), for now we > don't share source because of ugly code, but it can > be a good start > point for a new project... Test it, and tell us what > you think about... > > Nicolas (and Olivier) > > > -----Message d'origine----- > > De : pgsql-jdbc-owner@postgresql.org > [mailto:pgsql-jdbc- > > owner@postgresql.org] De la part de Dave Cramer > > Envoy� : mercredi 5 juin 2002 18:25 > > � : pgsql-jdbc@postgresql.org > > Objet : [JDBC] Java GUI development > > > > Hi folks, > > > > There is some discussion on hackers about the > creation of a > > cross-platform gui for postgres ala pgAdmin2, or > pgaccess. > > > > Is there anyone interested in collaborating on a > Java GUI. I am fairly > > confident I could handle the low end server > interface to the tables, > but > > am looking for someone with swing skills > > > > Dave > > > > > > > > > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 1: subscribe and unsubscribe commands go to > majordomo@postgresql.org > > > ---------------------------(end of > broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
On Fri, 2002-06-07 at 22:42, Robinson wrote: > will the GUI be only for performing administrative > tasks? No it will be cross platform tool in the same vein as pgaccess and pgAdminII Cheers Tony Grant -- RedHat Linux on Sony Vaio C1XD/S http://www.animaproductions.com/linux2.html Macromedia UltraDev with PostgreSQL http://www.animaproductions.com/ultra.html
----- Original Message ----- From: "Jeremy Buchmann" <jeremy@wellsgaming.com> Sent: Wednesday, June 05, 2002 2:47 PM > On Wed, 2002-06-05 at 18:24, Dave Cramer wrote: > > > There is some discussion on hackers about the creation of a > > cross-platform gui for postgres ala pgAdmin2, or pgaccess. > > > > Is there anyone interested in collaborating on a Java GUI. I am fairly > > confident I could handle the low end server interface to the tables, but > > am looking for someone with swing skills > > I like the idea of a good Java interface for Pg. I'm not a swing master > or anything, but I have written a couple things in it. In the near > future, I will be writing a bunch of swing programs on Mac OS X, so I > may be able to help out as I get better. > > I can also test on Linux and Mac OS X. Ditto. -s