phpesp-devel — Discussion of the development of phpESP

RE: [phpesp-dev] Re: Re: Export Download

[James E. F. <jf...@ac...>]

-- Quoting RFC 2046 --
4.1.4. Unrecognized Subtypes

Unrecognized subtypes of "text" should be treated as
subtype "plain" as long as the MIME implementation knows
how to handle the charset. Unrecognized subtypes which also
specify an unrecognized charset should be treated as
"application/octet-stream".
-- End Quote --

The "official" list of types is at:
http://www.isi.edu/in-notes/iana/assignments/media-types/media-types
and the closest type is "text/tab-separated-values".
Perhaps we should use: "text/comma-separated-values".
It works fine with Netscape 4.79 (linux) and Mozilla
(linux).

Plenty of people use the "application/x-foo" type for
unregistered types... (pdf, gzip, etc)

-James

On Wed, 27 Mar 2002, Kon Angelopoulos wrote:

> I totally agree
> I just don't think application/x-csv is a valid type
>
> Kon
>
>
> > -----Original Message-----
> > From: Matthew Gregg [mailto:gr...@mu...]
> > Sent: Wednesday, March 27, 2002 9:32 AM
> > To: Kon Angelopoulos; php...@li...
> > Subject: RE: [phpesp-dev] Re: Re: Export Download
> >
> >
> > But what if I'm not importing into Excel?  I would prefer a more generic
> > mime type.  Unless of course "application/x-csv" is totally wrong.
> >
> > --On Wednesday, March 27, 2002 09:25:18 AM +1100 Kon Angelopoulos
> > <an...@cp...> wrote:
> >
> > >
> > > Guys,
> > >
> > >     the prefered mime type for excel is: application/vnd.ms-excel
> > >
> > > Kon
> >
> >
> >
> > one of the friendly folks in the IT Lab.
> > --------------------------------------\
> > The IT Lab (http://www.itlab.musc.edu) \____________________
> > Probably the world's premier software development center.
> > Serving: Programming, Tools, Ice Cream, Seminars
> >
>
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>

RE: [phpesp-dev] Re: Re: Export Download

[Kon A. <an...@cp...>]

I totally agree
I just don't think application/x-csv is a valid type

Kon 


> -----Original Message-----
> From: Matthew Gregg [mailto:gr...@mu...]
> Sent: Wednesday, March 27, 2002 9:32 AM
> To: Kon Angelopoulos; php...@li...
> Subject: RE: [phpesp-dev] Re: Re: Export Download
> 
> 
> But what if I'm not importing into Excel?  I would prefer a more generic 
> mime type.  Unless of course "application/x-csv" is totally wrong.
> 
> --On Wednesday, March 27, 2002 09:25:18 AM +1100 Kon Angelopoulos 
> <an...@cp...> wrote:
> 
> >
> > Guys,
> >
> >     the prefered mime type for excel is: application/vnd.ms-excel
> >
> > Kon
> 
> 
> 
> one of the friendly folks in the IT Lab.
> --------------------------------------\
> The IT Lab (http://www.itlab.musc.edu) \____________________
> Probably the world's premier software development center.
> Serving: Programming, Tools, Ice Cream, Seminars
> 

RE: [phpesp-dev] Re: Re: Export Download

[Matthew G. <gr...@mu...>]

But what if I'm not importing into Excel?  I would prefer a more generic 
mime type.  Unless of course "application/x-csv" is totally wrong.

--On Wednesday, March 27, 2002 09:25:18 AM +1100 Kon Angelopoulos 
<an...@cp...> wrote:

>
> Guys,
>
>     the prefered mime type for excel is: application/vnd.ms-excel
>
> Kon



one of the friendly folks in the IT Lab.
--------------------------------------\
The IT Lab (http://www.itlab.musc.edu) \____________________
Probably the world's premier software development center.
Serving: Programming, Tools, Ice Cream, Seminars

RE: [phpesp-dev] Re: Re: Export Download

[Kon A. <an...@cp...>]

Guys,

    the prefered mime type for excel is: application/vnd.ms-excel=20

Kon=20

Re: [phpesp-dev] ldap patch

[James E. F. <jf...@ac...>]

Well I don't use LDAP, and haven't for the past 3-4
years... So I made a few cosmetic changes and commited your
patch. Could you check out the latest CVS version and try
it out. Hopefully I didn't break anything. Also it would be
nice if you could write a small README.LDAP or something
giving some pointers on what to set each of the new
phpESP.ini variables to when using LDAP (and any other
pointers you think appropriate).

I haven't really looked too closely at your patch, but let
me say this in case it applies. There is a field called
'auth' in both the respondent table, and the designer
table. The default value is BASIC. That field is currently
not used at all. I put it in there for the possiblity of
future auth-types to set it if they need to. Perhaps the
LDAP auth would want to use that field. Anyway ... it's
there for your use.

-James

On Fri, 22 Mar 2002, Christopher Zorn wrote:

> Ok. Here is my patch. It is a quick hack so I may be
> over looking some things. Please point out anything
> that you see wrong with it. All I am using ldap for is
> authentication for now. When someone trys to log into
> phpESP/admin it will check the database ( this is so we
> can still have a root user ) if that fails it
> authenticates against the ldap server and if
> successfull it will either insert user information into
> the database and create a seperate group for the user
> or update the user password to match the one for ldap.
> What do you guys think?

Re: [phpesp-dev] Re: Export Download

[James E. F. <jf...@ac...>]

On Tue, 26 Mar 2002, Matthew Gregg wrote:
> One slight change to download.inc.
> -	header("Content-Disposition: attachment; filename=$\"name.csv\"");
> +	header("Content-Disposition: attachment; filename=$name.csv");
> That fixes the extra "'s that show up in Konq. and Windows IE.

Done. I am committing this part to CVS now.

> What do you think of appending date/time to the
> exported filename and maybe a check for empty results
> before download/export?

I don't know about appending the date ... you saw my
comment about the "quarterly" example? How about instead of
checking for empty results ... perhaps just list the number
of results per survey on the export page? Checking for # on
export is harder, especially in the case of downloading
because by that point we have already bypassed the standard
HTML headers and such.

-James

Re: [phpesp-dev] Re: Export Download

[Matthew G. <gr...@mu...>]

Yeah.  Moving the logic into download.inc is much better.  I was hesitant 
to go that route.

One slight change to download.inc.
-	header("Content-Disposition: attachment; filename=$\"name.csv\"");
+	header("Content-Disposition: attachment; filename=$name.csv");
That fixes the extra "'s that show up in Konq. and Windows IE.


application/x-csv looks like the way to go.

What do you think of appending date/time to the exported filename and maybe 
a check for empty results before download/export?

--On Tuesday, March 26, 2002 11:55:44 AM -0500 "James E. Flemer" 
<jf...@ac...> wrote:

> I've modified your patch a little bit. Take a look and see
> what you all think. It allows people to still export data
> to a file, and also download it. I also changed the content
> type to "application/x-csv" since "text/plain-text" is not
> a real content type (and when it is "text/plain" it shows
> inline, not a save as box). We could also try
> "application/x-msexcel", tho I believe there is another
> preferred type for Excel.
>
> -James
>
> On Mon, 25 Mar 2002, Matthew Gregg wrote:
>
>> Since I didn't get any feedback on this idea, I went ahead an created the
>> attached patch against current CVS.
>>
>> I'm sure it's lacking somewhere so...comments?
>>
>> --On Saturday, March 23, 2002 10:09:27 AM -0500 Matthew Gregg
>> <gr...@mu...> wrote:
>>
>> > I've got this roughed in and working.
>> > I'm getting around headers/data being sent as follows:
>> > In export.inc on the CSV download url, I'm adding another parameter
>> > that is used in manage.php and when export.inc is called later to
>> > bypass any headers or data being sent.
>> >
>> > At your suggestion I split survey_export_cvs() into survey_export_cvs()
>> > and survey_generate_cvs()
>> >
>> > As for as mime types:
>> > I'm considering "application/x-msexcel" or "text/plain-text".  We've
>> > used x-msexcel before to "trick" excel into opening tab delimited text
>> > files. Not sure how it will work for csv.
>> >
>> > How's this sound?



one of the friendly folks in the IT Lab.
--------------------------------------\
The IT Lab (http://www.itlab.musc.edu) \____________________
Probably the world's premier software development center.
Serving: Programming, Tools, Ice Cream, Seminars

Re: [phpesp-dev] Re: Export Download

[James E. F. <jf...@ac...>]

I've modified your patch a little bit. Take a look and see
what you all think. It allows people to still export data
to a file, and also download it. I also changed the content
type to "application/x-csv" since "text/plain-text" is not
a real content type (and when it is "text/plain" it shows
inline, not a save as box). We could also try
"application/x-msexcel", tho I believe there is another
preferred type for Excel.

-James

On Mon, 25 Mar 2002, Matthew Gregg wrote:

> Since I didn't get any feedback on this idea, I went ahead an created the
> attached patch against current CVS.
>
> I'm sure it's lacking somewhere so...comments?
>
> --On Saturday, March 23, 2002 10:09:27 AM -0500 Matthew Gregg
> <gr...@mu...> wrote:
>
> > I've got this roughed in and working.
> > I'm getting around headers/data being sent as follows:
> > In export.inc on the CSV download url, I'm adding another parameter that
> > is used in manage.php and when export.inc is called later to bypass any
> > headers or data being sent.
> >
> > At your suggestion I split survey_export_cvs() into survey_export_cvs()
> > and survey_generate_cvs()
> >
> > As for as mime types:
> > I'm considering "application/x-msexcel" or "text/plain-text".  We've used
> > x-msexcel before to "trick" excel into opening tab delimited text files.
> > Not sure how it will work for csv.
> >
> > How's this sound?

RE: [phpesp-dev] Re: Re: Export Download

[Matthew G. <gr...@mu...>]

Comments below...
>
> I've tested your patch (on windows box using IE and Netscape plus on
> Linux box using Netscape and Konqueror) and it looks pretty good.
> The only minor issue I found was with Konqueror. It was not capable of
> displaying the $filename.csv name in the save as dialog box but rather
> It showed the file name "manage.php". It's contents however were that of
> the csv file.
>
I'm running Konq. 2.2.2 and other than "'s around the filename, it worked 
just fine.  I'll fix the " problem.


> I've also had a quick look at the code and it also seems very good.
>
> I do however have a few suggestions:
> 	I don't believe that the download cvs facility should be
> replacing the exporting of the cvs file to the /tmp dir (or any other
> dir) but
> complement it. By this I mean that the saving of the csv file to a dir
> on the server should also occur when the csv file is being downloaded.
> I can think of quite a few scenarios where a central repository of
> result files might come in very handy.
Ok will do this.


> 	I also don't think that a survey with no results should be
> downloadable. If a survey has no results it should return an error
> statement
> as the current phpesp version does.
Whoops... yeah will fix this.


> 	My final comment is a challenge. Assuming that others feel the
> same way as I with regard to leaving a copy of the csv file on the
> server
> I'd like to see this process check to see if the csv file exists and if
> it does, not to overwrite it - as is the current case- but rather check
> the files size
How about this...
Always create a new file and append the current date or date/time to the 
filename then do the export.





one of the friendly folks in the IT Lab.
--------------------------------------\
The IT Lab (http://www.itlab.musc.edu) \____________________
Probably the world's premier software development center.
Serving: Programming, Tools, Ice Cream, Seminars

RE: [phpesp-dev] Re: Re: Export Download

[James E. F. <jf...@ac...>]

On Tue, 26 Mar 2002, angek productions wrote:

> I'd like to see this process check to see if the csv
> file exists and if it does, not to overwrite it - as is
> the current case- but rather check the files size And
> if different create another copy of it with the current
> date appended to the end of the filename (or any other
> way where the csv files from a particular Survey can be
> distinquished from one another).
>
> So for example, assume that many of the surveys I
> create for my company run for a year. Each quarter the
> results are downloaded and analysed / compared to the
> previous Quarter's results. In this instance I would
> have 4 csv files on the server belonging to the same
> survey named quartely_survey_310302,
> quartely_survey_300602, Quartely_survey_300902 and
> quartely_survey_311202.
>
> Guys your thoughts please.

I would suggest for this case that at the end of each
quarter, you end the survey, copy it, and activate the new
copy. If you are doing data analysis in a separate program,
then you should have no problem appending one quarters data
to the rest. This way you would have multiple surveys named
something like:
  quarterly_survey_q1_02
  quarterly_survey_q2_02
  quarterly_survey_q3_02
  quarterly_survey_q4_02
  quarterly_survey_q1_03
  ...

However, it may still be a good idea to not overwrite
existing data files. Perhaps a confirmation screen, or a
screen with a box to enter an alternate filename, would be
a nice feature.

-James

RE: [phpesp-dev] Re: Re: Export Download

[angek p. <ang...@ip...>]

Matthew,

I've also sent this email to the list so that others may contribute
their thoughts.

I've tested your patch (on windows box using IE and Netscape plus on
Linux box using Netscape and Konqueror) and it looks pretty good.
The only minor issue I found was with Konqueror. It was not capable of
displaying the $filename.csv name in the save as dialog box but rather
It showed the file name "manage.php". It's contents however were that of
the csv file.

I've also had a quick look at the code and it also seems very good.

I do however have a few suggestions:
	I don't believe that the download cvs facility should be
replacing the exporting of the cvs file to the /tmp dir (or any other
dir) but
complement it. By this I mean that the saving of the csv file to a dir
on the server should also occur when the csv file is being downloaded.
I can think of quite a few scenarios where a central repository of
result files might come in very handy.
	I also don't think that a survey with no results should be
downloadable. If a survey has no results it should return an error
statement
as the current phpesp version does.
	My final comment is a challenge. Assuming that others feel the
same way as I with regard to leaving a copy of the csv file on the
server
I'd like to see this process check to see if the csv file exists and if
it does, not to overwrite it - as is the current case- but rather check
the files size
And if different create another copy of it with the current date
appended to the end of the filename (or any other way where the csv
files from a particular
Survey can be distinquished from one another).
	So for example, assume that many of the surveys I create for my
company run for a year.
Each quarter the results are downloaded and analysed / compared to the
previous
Quarter's results. In this instance I would have 4 csv files on the
server belonging to the same survey named quartely_survey_310302,
quartely_survey_300602,
Quartely_survey_300902 and quartely_survey_311202.

Guys your thoughts please.


Kon

-----Original Message-----
From: Matthew Gregg [mailto:gr...@co...] On Behalf Of
Matthew Gregg
Sent: Tuesday, 26 March 2002 2:34 PM
To: Kon Angelopoulos
Subject: Re: [phpesp-dev] Re: Re: Export Download


Strange, just guessing but...
It's a UNIX text file.  Are you on Windows?  Could be line ending
differences.

I converted it to DOS line endings and attached it again.

On Tue, Mar 26, 2002 at 01:42:45PM +1100, Kon Angelopoulos wrote:
> Thanks Matthew,
> 
> When I viewed it, it was literally all over the place.
> 
> Talk soon
> 
> Kon Angelopoulos
> Emerging Technologies Developer, Education
> Spherion Group Ltd.


-- 
brought to you by, Matthew Gregg...
one of the friendly folks in the IT Lab.
--------------------------------------\
The IT Lab (http://www.itlab.musc.edu) \____________________ Probably
the world's premier software development center.
Serving: Programming, Tools, Ice Cream, Seminars

[phpesp-dev] Re: Re: Export Download

[Kon A. <an...@cp...>]

Matthew,

Could you please send me a copy of your diff file =
(re:survey_export_cvs.inc).
I'm having great difficulty reading it off the devel list.

Kon

Re: [phpesp-dev] Re: Export Download

[Matthew G. <gr...@mu...>]

Since I didn't get any feedback on this idea, I went ahead an created the 
attached patch against current CVS.

I'm sure it's lacking somewhere so...comments?

--On Saturday, March 23, 2002 10:09:27 AM -0500 Matthew Gregg 
<gr...@mu...> wrote:

> I've got this roughed in and working.
> I'm getting around headers/data being sent as follows:
> In export.inc on the CSV download url, I'm adding another parameter that
> is used in manage.php and when export.inc is called later to bypass any
> headers or data being sent.
>
> At your suggestion I split survey_export_cvs() into survey_export_cvs()
> and survey_generate_cvs()
>
> As for as mime types:
> I'm considering "application/x-msexcel" or "text/plain-text".  We've used
> x-msexcel before to "trick" excel into opening tab delimited text files.
> Not sure how it will work for csv.
>
> How's this sound?
>
>
> --On Friday, March 22, 2002 03:00:06 PM -0500 "James E. Flemer"
> <jf...@ac...> wrote:
>
>> Please do! How do you plan to do this? I was thinking that
>> there would have to be some script outside the
>> admin/include framework to do this (since by then there are
>> already headers/data sent). This script outside should use
>> a content-type of "application/x-csv"(?) and return the
>> actual csv data. I would suggest splitting the exising
>> survey_export_cvs() into:
>>    survey_generate_cvs() -- creates a string/array of data
>>    survey_export_cvs() -- calls generate, and writes to file
>> Then your download script could call generate, and just
>> print the appropriate headers then the data directly.
>>
>> -James
>>
>> On Fri, 22 Mar 2002, Matthew Gregg wrote:
>>
>>> Cool.  Since that was done so fast.  I can move on to the next change.
>>> Unless someone objects or has already started it, I would like to add
>>> "download" to the export function.
>>
>
>
>
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>



one of the friendly folks in the IT Lab.
--------------------------------------\
The IT Lab (http://www.itlab.musc.edu) \____________________
Probably the world's premier software development center.
Serving: Programming, Tools, Ice Cream, Seminars

Re: [phpesp-dev] ideas, wishlist. etc

[James E. F. <jf...@ac...>]

On Sun, 24 Mar 2002, Matthew Gregg wrote:

> On Sunday, March 24, 2002 James E. Flemer wrote:
>
> > The best solution to this is something you have already
> > suggested -- an install script. The install script, if
> > written, must check to make sure the user will not install
> > the phpESP.ini in a publicly accessible directory,
>
> An install script is surely the way to go.  However I'm not sure it's
> possible for an install script to know what is and what isn't a web
> accessible directory.  We are gonna have to trust the user somewhat.

True, but you can do some pretty good guessing, and if it
looks like a public directory, give a second confirmation
and big warning message.

--snip--
> > I am very glad you mentioned XML. I would actually like to
> > move a large portion of data out of mysql and into XML. I
>
> Are you sure you want to do this?  XML is a great data "interchange"
> mark-up, but generally functions poorly as a data repository, unless you
> have a specialized XMLDB.
> I would put my vote in favor of keeping a SQL based back-end and use
> XML/XLT as presentation/data exchange layer.

Well yes and no. My idea is to use XML internally (in PHP)
and to store the XML in the database. But when a survey was
activated, we would use XSLT to make a (X)HTML rendering of
the survey. This would allow very fast serving of the
survey, since we would eliminate a lot of SQL/DB overhead.
Plus, it is much harder to create a database schema that
will allow for the flexibility of survey design I want (and
that XML allows) ...

--snip--
> > I would like to see an interface to PostNuke first. Note
> > that there are license differences between most of those
> > CMS and phpESP, so phpESP cannot be distributed with them,
> > but I can certainly work with them.
>
> Not that I would distribute ESP with any of the above CMS's, but can you
> explain why ESP can't be?  They are all GPL'd.

phpESP is not GPL, it has a BSD-style license. GPL is a
nasty license, and will not allow you to distribute non-GPL
software with it. The phpESP license allows distributing
one of the above with it, but not vice versa.

--snip--
> > I don't quite follow this. I am assuming you mean removing
> > the step where the user inserts the PHP code into their
> > HTML template file. Naturally that would be ideal, but
> > probably not possible security wise (since the web server
> > executes without user privileges).
>
> This is just off the top of my head, but what's wrong with something like
> this:
>
> <html>
> <body bgcolor="#ffffff">
> <?php $sid=$id; include("/var/www/esp/public/handler.php");?>
> </body>
> </html>
>
> Then called as survey.php?id=3 would show survey with ID 3.

Bad security, the SID should not be seen by the end user,
nor specifiable. Also if one was to use the above code, it
should really read:
  <?php $sid=intval($id); ... ?>

However, there is certainly nothing stopping any end user
from using a script like that. It won't ever be encouraged
by me nor be part of the standard distribution.

-James

Re: [phpesp-dev] ideas, wishlist. etc

[Matthew G. <gr...@mu...>]

A few comments below...

--On Sunday, March 24, 2002 02:28:57 PM -0500 "James E. Flemer" 
<jf...@ac...> wrote:

> Anyone who is seriously interested in contributing should
> get themselves a sourceforge account, and letting me know
> their user name.

My SF username is greggmc.

...snip...
>
> The best solution to this is something you have already
> suggested -- an install script. The install script, if
> written, must check to make sure the user will not install
> the phpESP.ini in a publicly accessible directory,

An install script is surely the way to go.  However I'm not sure it's 
possible for an install script to know what is and what isn't a web 
accessible directory.  We are gonna have to trust the user somewhat.

> and must
> modify all necessary paths depending on the install
> location. This should be a fairly trivial operation. In
> addition, I would like (tho not necessary) for the install
> script to handle the database creation and initialization,
> and on checking the user permissions (mysql user).
>
>>     add a stock set of surveys and questionnaires
>>     import/export feature which handles XML and other formats
>>     use XML and XSLT to generate the HTML pages for reports etc.
>
> I am very glad you mentioned XML. I would actually like to
> move a large portion of data out of mysql and into XML. I

Are you sure you want to do this?  XML is a great data "interchange" 
mark-up, but generally functions poorly as a data repository, unless you 
have a specialized XMLDB.
I would put my vote in favor of keeping a SQL based back-end and use 
XML/XLT as presentation/data exchange layer.


> would like the back-end format for the surveys to be XML.
> With a well written DTD (or schema), the XML based survey
> format would be much more flexible. It would still be
> simple enough to allow a similar web interface to design

...snip...
>
>>     interfaces to other content management systems
>>         phpNuke, PostNuke, phpgroupware, ezPublish, etc.
>
> I would like to see an interface to PostNuke first. Note
> that there are license differences between most of those
> CMS and phpESP, so phpESP cannot be distributed with them,
> but I can certainly work with them.

Not that I would distribute ESP with any of the above CMS's, but can you 
explain why ESP can't be?  They are all GPL'd.


>
>>     Ability to specify a page to include the generated PHP code
>>         (i.e. maybe include comment in the HTML/PHP page with a
>> begin/end
>>             comment such that phpESP could auto insert the php code
>> directly
>>             into the HTML/PHP page
>>                 e.g.
>>                 HTML/PHP file.
>>
>>                     <!--  phpESP v1.4 Survey Start -->
>>                             Section to include the generated PHP code
>>                     <!--  phpESP v1.4 Survey End -->
>>
>>         Possibility to manage "pages with the php generated survey code"
>
> I don't quite follow this. I am assuming you mean removing
> the step where the user inserts the PHP code into their
> HTML template file. Naturally that would be ideal, but
> probably not possible security wise (since the web server
> executes without user privileges).

This is just off the top of my head, but what's wrong with something like 
this:

<html>
<body bgcolor="#ffffff">
<?php $sid=$id; include("/var/www/esp/public/handler.php");?>
</body>
</html>

Then called as survey.php?id=3 would show survey with ID 3.

...snip...

[phpesp-dev] Re: ideas, wishlist. etc

[Kon A. <an...@cp...>]

All,

I second James' reply to Lou's initial thoughts.

Also, I am currently in the middle of redesigning the GUI component of =
phpESP and should have three design layouts in the next few weeks which =
I would like to post for user feedback and possibly a vote to determine =
the next new GUI for phpESP.
If it's OK with you guys I'd like to see this one through......


Kon=20

[phpesp-dev] XML XSLT

[James E. F. <jf...@ac...>]

As far as XML/XSLT is concerned anyone interested should
take a look at some stuff I did (a long time ago) with XML
for phpESP.
  http://phpesp.sf.net/xml.tar.gz
-James

Re: [phpesp-dev] ideas, wishlist. etc

[James E. F. <jf...@ac...>]

Anyone who is seriously interested in contributing should
get themselves a sourceforge account, and letting me know
their user name. Probably the best way to handle task
assignment and such is through the "Feature Request" part of
SourceForge, that way hopefully people will not duplicate
the efforts of others.

I have commented (below) on a few of the items you brought
up. I'd like to see other users opinions on them as well.
Then perhaps we can try to assign some of them among those
willing to contribute.

-James

On Sun, 24 Mar 2002, Lou Spironello wrote:

> I'm please you started this development list.
> I've been using phpESP for a while and like it.
>
> I would like to contribute my time to some development things.
>
> I'm wondering if anyone is working on an install script for phpESP
> and if not I would be willing to work on one.
>
> Just a few ideas:
>     install script for phpESP
>     RPMs, SRPMS, deb, zip, formats for phpESP
>     standardize the config directory so users won't have to
>         modify the source files (i.e. references to the include files)

This is a good idea, but isn't possible. The location of
the files must not be pre-determined. Many people use
hosting companies, and have very little control over the
actual web server they are running phpESP on. As of version
1.3 (or maybe earlier) I have suggested that the package
get installed in /usr/local/lib/php/contrib, since
/usr/local/lib/php is typically where PEAR and such gets
installed. Installing in lib requires root access to the
webserver, however. So the option must exist to install in
a user directory. Unfortunately, many people install the
*whole* package in their "public_html" directory -- this
leads to problems because then the config file (phpESP.ini)
is accessible to the world via the web server, hence the
database passwords are also available.

The best solution to this is something you have already
suggested -- an install script. The install script, if
written, must check to make sure the user will not install
the phpESP.ini in a publicly accessible directory, and must
modify all necessary paths depending on the install
location. This should be a fairly trivial operation. In
addition, I would like (tho not necessary) for the install
script to handle the database creation and initialization,
and on checking the user permissions (mysql user).

>     add a stock set of surveys and questionnaires
>     import/export feature which handles XML and other formats
>     use XML and XSLT to generate the HTML pages for reports etc.

I am very glad you mentioned XML. I would actually like to
move a large portion of data out of mysql and into XML. I
would like the backend format for the surveys to be XML.
With a well written DTD (or schema), the XML based survey
format would be much more flexible. It would still be
simple enough to allow a similar web interface to design
basic surveys, but would also allow advanced users to work
directly with the XML to create a more customized layout.
Also, by using XSLT, we add the possibility of themes and
even more flexibility.

>     ability to copy portions of surveys from other surveys
>     change the main maintenance menu to functional areas
>             Survey construction
>                     add, edit. delete, copy
>             Survey administration
>                     test, activate, close
>             Survey reports
>                     view, print, etc
>             Survey authentication
>                     user creation, editing, deletion, copying (i.e.
> duplicate user
>                             privileges)
>             Survey utilities
>                 export (mySQL, XML, CSV, etc), import(mySQL, XML, CSV,
> etc)

The whole interface needs to be redone. I am not a
designer, and clearly the GUI I designed sucks. Hopefully
there is someone who will have the time to rework the
interface.

>     interfaces to other content management systems
>         phpNuke, PostNuke, phpgroupware, ezPublish, etc.

I would like to see an interface to PostNuke first. Note
that there are license differences between most of those
CMS and phpESP, so phpESP cannot be distributed with them,
but I can certainly work with them.

>     Ability to specify a page to include the generated PHP code
>         (i.e. maybe include comment in the HTML/PHP page with a
> begin/end
>             comment such that phpESP could auto insert the php code
> directly
>             into the HTML/PHP page
>                 e.g.
>                 HTML/PHP file.
>
>                     <!--  phpESP v1.4 Survey Start -->
>                             Section to include the generated PHP code
>                     <!--  phpESP v1.4 Survey End -->
>
>         Possibility to manage "pages with the php generated survey code"

I don't quite follow this. I am assuming you mean removing
the step where the user inserts the PHP code into their
HTML template file. Naturally that would be ideal, but
probably not possible security wise (since the web server
executes without user privileges).

>         Display phpESP version on Maintenance Page

It is in the "title" tag of the page. :-)

[phpesp-dev] ideas, wishlist. etc

[Lou S. <lr...@at...>]

I'm please you started this development list.
I've been using phpESP for a while and like it.

I would like to contribute my time to some development things.

I'm wondering if anyone is working on an install script for phpESP
and if not I would be willing to work on one.

Just a few ideas:
    install script for phpESP
    RPMs, SRPMS, deb, zip, formats for phpESP
    standardize the config directory so users won't have to
        modify the source files (i.e. references to the include files)
    add a stock set of surveys and questionnaires
    import/export feature which handles XML and other formats
    use XML and XSLT to generate the HTML pages for reports etc.
    ability to copy portions of surveys from other surveys
    change the main maintenance menu to functional areas
            Survey construction
                    add, edit. delete, copy
            Survey administration
                    test, activate, close
            Survey reports
                    view, print, etc
            Survey authentication
                    user creation, editing, deletion, copying (i.e.
duplicate user
                            privileges)
            Survey utilities
                export (mySQL, XML, CSV, etc), import(mySQL, XML, CSV,
etc)
    interfaces to other content management systems
        phpNuke, PostNuke, phpgroupware, ezPublish, etc.
    Ability to specify a page to include the generated PHP code
        (i.e. maybe include comment in the HTML/PHP page with a
begin/end
            comment such that phpESP could auto insert the php code
directly
            into the HTML/PHP page
                e.g.
                HTML/PHP file.

                    <!--  phpESP v1.4 Survey Start -->
                            Section to include the generated PHP code
                    <!--  phpESP v1.4 Survey End -->

        Possibility to manage "pages with the php generated survey code"
        Display phpESP version on Maintenance Page



Thank you.
Lou.

[phpesp-dev] ideas, wishlist. etc.

[Lou S. <lr...@at...>]

I'm please you started this development list.
I've been using phpESP for a while and like it.

I would like to contribute my time to some development things.

I'm wondering if anyone is working on an install script for phpESP
and if not I would be willing to work on one.

Just a few ideas:
    install script for phpESP
    RPMs, SRPMS, deb, zip, formats for phpESP
    standardize the config directory so users won't have to
        modify the source files (i.e. references to the include files)
    add a stock set of surveys and questionnaires
    import/export feature which handles XML and other formats
    use XML and XSLT to generate the HTML pages for reports etc.
    ability to copy portions of surveys from other surveys
    change the main maintenance menu to functional areas
            Survey construction
                    add, edit. delete, copy
            Survey administration
                    test, activate, close
            Survey reports
                    view, print, etc
            Survey authentication
                    user creation, editing, deletion, copying (i.e.
duplicate user
                            privileges)
            Survey utilities
                export (mySQL, XML, CSV, etc), import(mySQL, XML, CSV,
etc)
    interfaces to other content management systems
        phpNuke, PostNuke, phpgroupware, ezPublish, etc.
    Ability to specify a page to include the generated PHP code
        (i.e. maybe include comment in the HTML/PHP page with a
begin/end
            comment such that phpESP could auto insert the php code
directly
            into the HTML/PHP page
                e.g.
                HTML/PHP file.

                    <!--  phpESP v1.4 Survey Start -->
                            Section to include the generated PHP code
                    <!--  phpESP v1.4 Survey End -->

        Possibility to manage "pages with the php generated survey code"


Thank you.
Lou.

[phpesp-dev] Bug in version 1.4beta2 and version 1.4beta3 ??

[Kon A. <ang...@ip...>]

James,

	I've noticed a small bug in both versions 1.4beta2 and 1.4beta3.
	After I've created a survey, I change its status from editing to
test.
	I proceed to test the survey by answering the questions. Out of
curiosity
	I moused over the View Results and Go Back to Management
Interface links and the bottom
	of the page and discovered the following:
	the View Results link points to:
.../admin/en?where=results&sid=1&test=1
	the Go Back to Management Interface points to:
.../admin/en?where=manage.

	Igoring this,I submitted the test survey and on the thank you
page I checked the above links again
	to find they were still pointing to the above.

	I've had a look at the scripts especially /where/test.inc and
found that by changing the lines
	$tmp = $ESPCONFIG['ME'] : line 47 to $tmp1 = $ESPCONFIG['ME']
and
	$ESPCONFIG['ME'] = $tmp : line 51 to $ESPCONFIG['ME'] = $tmp1
the links pointed to the right place.

Kon

[phpesp-dev] Re: Export Download

[Matthew G. <gr...@mu...>]

I've got this roughed in and working.
I'm getting around headers/data being sent as follows:
In export.inc on the CSV download url, I'm adding another parameter that is 
used in manage.php and when export.inc is called later to bypass any 
headers or data being sent.

At your suggestion I split survey_export_cvs() into survey_export_cvs() and 
survey_generate_cvs()

As for as mime types:
I'm considering "application/x-msexcel" or "text/plain-text".  We've used 
x-msexcel before to "trick" excel into opening tab delimited text files. 
Not sure how it will work for csv.

How's this sound?


--On Friday, March 22, 2002 03:00:06 PM -0500 "James E. Flemer" 
<jf...@ac...> wrote:

> Please do! How do you plan to do this? I was thinking that
> there would have to be some script outside the
> admin/include framework to do this (since by then there are
> already headers/data sent). This script outside should use
> a content-type of "application/x-csv"(?) and return the
> actual csv data. I would suggest splitting the exising
> survey_export_cvs() into:
>    survey_generate_cvs() -- creates a string/array of data
>    survey_export_cvs() -- calls generate, and writes to file
> Then your download script could call generate, and just
> print the appropriate headers then the data directly.
>
> -James
>
> On Fri, 22 Mar 2002, Matthew Gregg wrote:
>
>> Cool.  Since that was done so fast.  I can move on to the next change.
>> Unless someone objects or has already started it, I would like to add
>> "download" to the export function.
>

[phpesp-dev] Our Development Projects

[Kon A. <ang...@ip...>]

Guys,
	Would it be worth having a list of some sort that shows the 
	project that each of us is currently involved with and the tasks
that are on the
	horizon (ranked by impotance) that we have yet to start ?

Kon

[phpesp-dev] RE:Re: "section text, etc..

[Kon A. <ang...@ip...>]

Guys,

	My apologies for my reply to Matthew's email.
	sf.net has spat the dummy and refuses to display it correctly so
I've
	resent it to each of you personally.

Kon

RE: [phpesp-dev] "section text, etc..

[angek p. <ang...@ip...>]

Hi Guys,

	I don't think there is a mime type that can be specifically used
for csv files,
	however there is a content-disposition that can be used which
basically pops up a 
	save as dialog box (certainly in IE - I use this approach quite
often when I don't want the browser
	displaying the recognised mime types but rather offer to save
instead). 

	So here's a possible scenario:
	Please note that this is not an implementation nor should it be
implemented until it is properly tested .......

	In the /admin/include/where/export.inc file just after line 144
echo(_('Survey exported as:') . " <tt>$file</tt>"); we add
	something like this:
	$file2 = fopen ("download.php","w");
	$data = "<?php\n
		header(\"content-disposition: attachement;
filename=$file1\");\n
		\$file1 = fopen(\"$file\",\"r\");\n
		fpassthru(\$file1);\n ?>";

	$fputs($file2, "$data");
	?>
	<a href="javascript:void"
onClick="window.open('download.php','Download','width=300
height=300')">Download this file</a>
	<?php

	The above does 2 things:
	1/ writes to a file called download.php which is stored in the
/admin/ directory with 666 permissions.
	   This file should have the same group and owner as all the
other files in the admin dir.
	   The fpassthru function simply sends the contents of a file to
the output stream (in this case your browser window) and closes the
file.
	   In IE the content-disposition takes precedence over the
fpassthru function and simply offers you to save a html file. Simply
entering
	   "name.csv" solves this problem. (and yes, you enter the "" as
well :) )
	   In Netscape I don't think content-disposition works but it
will display the csv file content properly formatted to be
	   saved as :filename.csv".

	2/ This basically creates a link on the Export Data Page next to
"Survey exported as: /tmp/.......csv. Clicking this link will open in a
new
	    window (which may contain header info...) the download.php
page then (refer to 1).
	
	Obviously the above example would need proper error checking
code as well........

	This is not a complete solution but merely a starting point for
further investigation.


Kon
-----Original Message-----
From: php...@li...
[mailto:php...@li...] On Behalf Of Matthew
Gregg
Sent: Saturday, 23 March 2002 7:44 AM
To: php...@li...
Subject: Re: [phpesp-dev] "section text, etc..


Yup, save file popup is what I'm talking about.  It probbaly will have
to be slightly out of the ESP framework due to headers being sent as
James pointed out.

--On Friday, March 22, 2002 10:02:17 PM +0200 Roman Jasins
<cit...@ma...> wrote:

> Matthew,
>
> are talking about a pop-up window (aka Save File). That's what I was 
> thinking, but haven't got around implementing. In any case Download is

> definitely a feature that people would use, especially those who 
> aren't UNIX savvy (assuming the ESP is running on a *nix)
>
> -Roman
> On Friday, March 22, 2002, at 09:52  PM, Matthew Gregg wrote:
>
>> Cool.  Since that was done so fast.  I can move on to the next 
>> change. Unless someone objects or has already started it, I would 
>> like to add "download" to the export function.
>>
>> --On Friday, March 22, 2002 01:40:10 PM -0500 "James E. Flemer" 
>> <jf...@ac...> wrote:
>>
>>> Done. Check out CVS now. I also added a patch to survey_results, to 
>>> include the "section text" in the results (it was in the merge, but 
>>> not standard results).
>>>
>>> -James
>>>
>>> On Fri, 22 Mar 2002, James E. Flemer wrote:
>>>
>>>> On Fri, 22 Mar 2002, Matthew Gregg wrote:
>>>> > I would like to throw out a possible change to Kon's patch.
>>>> Instead of
>>>> > having the "section text" indented, have it flush with the 
>>>> > question numbering.
>>>> >
>>>> > For example:
>>>> > Put the "section text" in the left column and do a colspan="2".
>>>> >
>>>> > Thoughts?
>>>>
>>>> +1 : sounds good to me.
>>>>
>>>> -James
>>>>
>>>> [ For those not familiar, it's common to just say "+1" or
>>>>   "-1" for agree or disagree to a suggestion. That makes it
>>>>   easy to quickly see general opinion. (or we could use
>>>>   phpesp to acutally "vote". :-p ]
>>>>
>>>>
>>>> _______________________________________________
>>>> phpESP-devel mailing list php...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>>>>
>>>
>>>
>>> _______________________________________________
>>> phpESP-devel mailing list php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>>>
>>
>>
>>
>> _______________________________________________
>> phpESP-devel mailing list
>> php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>



_______________________________________________
phpESP-devel mailing list
php...@li...
https://lists.sourceforge.net/lists/listinfo/phpesp-devel