From: Jeremy B. <je...@we...> - 2003-09-25 17:29:29
|
Hi all, I'm evaluating the use of phpESP for my company and have a few quick questions. First, we use PostgreSQL for all our database needs. Since phpESP uses mySQL, we would either have to port it to PostgreSQL or assist in the port to PEAR. I'm experienced in PHP/PostgreSQL, and I think based on the number of lines in the code base that have 'mysql' in them, that I could do a port to PostgreSQL in 1-2 weeks. I'd rather not fork from the main distribution, so ideally I'd like to help in the port to PEAR, but I've never used PEAR. With a quick glance at the API, it looks easy enough...fairly similar to Perl's DBI. So my questions are, how is the PEAR port coming along? Would my help be welcome and useful? Would phpESP only use the database parts of PEAR? Thanks, Jeremy |
From: Matthew G. <gr...@mu...> - 2003-09-25 17:41:42
|
What you've seen mentioned on this mailing list in the last few days, is all there is of the port. On Thu, Sep 25, 2003 at 10:29:21AM -0700, Jeremy Buchmann wrote: > Hi all, > > I'm evaluating the use of phpESP for my company and have a few quick > questions. > > First, we use PostgreSQL for all our database needs. Since phpESP uses > mySQL, we would either have to port it to PostgreSQL or assist in the > port to PEAR. I'm experienced in PHP/PostgreSQL, and I think based on > the number of lines in the code base that have 'mysql' in them, that I > could do a port to PostgreSQL in 1-2 weeks. I'd rather not fork from > the main distribution, so ideally I'd like to help in the port to PEAR, > but I've never used PEAR. With a quick glance at the API, it looks > easy enough...fairly similar to Perl's DBI. So my questions are, how > is the PEAR port coming along? Would my help be welcome and useful? > Would phpESP only use the database parts of PEAR? > > Thanks, > Jeremy > > > > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |
From: Jeremy B. <je...@we...> - 2003-09-25 17:59:26
|
Unfortunetly, I just joined the list today and when I try to access the archives, I get an error message from Sourceforge :( But I'm guessing very little has been done... On Thursday, September 25, 2003, at 10:41 AM, Matthew Gregg wrote: > What you've seen mentioned on this mailing list in the last few days, > is all there is of the port. > > On Thu, Sep 25, 2003 at 10:29:21AM -0700, Jeremy Buchmann wrote: >> Hi all, >> >> I'm evaluating the use of phpESP for my company and have a few quick >> questions. >> >> First, we use PostgreSQL for all our database needs. Since phpESP >> uses >> mySQL, we would either have to port it to PostgreSQL or assist in the >> port to PEAR. I'm experienced in PHP/PostgreSQL, and I think based on >> the number of lines in the code base that have 'mysql' in them, that I >> could do a port to PostgreSQL in 1-2 weeks. I'd rather not fork from >> the main distribution, so ideally I'd like to help in the port to >> PEAR, >> but I've never used PEAR. With a quick glance at the API, it looks >> easy enough...fairly similar to Perl's DBI. So my questions are, how >> is the PEAR port coming along? Would my help be welcome and useful? >> Would phpESP only use the database parts of PEAR? >> >> Thanks, >> Jeremy |
From: Stefan C. <sch...@ea...> - 2003-09-26 05:47:31
|
So... It seems like Pear is having some rave reviews down here. Here's what I'll = do=20 : as soon as I got a dev environment with Oracle/ODBC running, I'll test th= e=20 Pear connectivity. If it works, I'll move my phpEsp to PEAR. But,=20 unfortunatley, I have also several additional features that I have to add t= o=20 the code that are not necessarily good for everyone. I'll try to maintain m= y=20 code as re-importable in the main branch as possible, but there will be som= e=20 work. =46eatures I plan to add : =2D More graphic generation =2D A survey translation mechanism (I'll try to HACK it in the current code= , so=20 don't expect something too clean) =2D I simplified the "question" tab : removed Fieldname, length, precision = in=20 favor of defaults (so yes, I killed some flexibility, but my users are=20 ranging from "I don't understand computers" to "I do understand them") =2D Rewritten the core logi in question.inc, it was way too complicated, uncommented and buggy, I expect my version to be done today. However, it'll= =20 need a lot of QA attention. =2D I'm also redefining the notion of group (which is pretty fuzzy anyway) =2D I'm writing a user manual, all in Docbook.=B5 stF |
From: Matthew G. <gr...@mu...> - 2003-09-26 13:47:12
|
See below... On Fri, Sep 26, 2003 at 07:53:18AM +0000, Stefan Champailler wrote: > So... > > It seems like Pear is having some rave reviews down here. Here's what I'll do > : as soon as I got a dev environment with Oracle/ODBC running, I'll test the > Pear connectivity. If it works, I'll move my phpEsp to PEAR. But, > unfortunatley, I have also several additional features that I have to add to > the code that are not necessarily good for everyone. I'll try to maintain my > code as re-importable in the main branch as possible, but there will be some > work. > > Features I plan to add : > > - More graphic generation What do you mean by graphic generation? > - A survey translation mechanism (I'll try to HACK it in the current > code, so don't expect something too clean) Can you do this drawing from what is currently implemented in the management interfaces multilingual code? > - I simplified the "question" tab : removed Fieldname, length, precision in > favor of defaults (so yes, I killed some flexibility, but my users are > ranging from "I don't understand computers" to "I do understand > them") Can this be optional? A phpESP.ini config variable? Lots of people need the flexibility. > - Rewritten the core logi in question.inc, it was way too complicated, > uncommented and buggy, I expect my version to be done today. However, it'll > need a lot of QA attention. > - I'm also redefining the notion of group (which is pretty fuzzy > anyway) How so? > - I'm writing a user manual, all in Docbook.? A manual would be awesome. Docbook or XHTML would be my vote. > > > stF > > > > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > phpESP-devel mailing list > php...@li... > https://lists.sourceforge.net/lists/listinfo/phpesp-devel > -- mcg ------------------------------------- The IT Lab (http://www.itlab.musc.edu) |