[PHP-DOC] Re: [PEAR-CORE] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
Hi all, > > Why not? Getting any errors? I thought it was installed by default > > by the installer? > > I guess its because the installer doesn't support folders with spaces > as the directory is called "C:\Users\Kalle Sommer Nielsen\" > > So you cannot get further or atleast I can't because my username has > spaces. I had to edit the phd.bat manually to make it work, not that > it was any major but anyway. The bug has been reported on PEAR 1.7.0 QA testing last year: http://news.php.net/php.pear.qa/4597 http://news.php.net/php.pear.qa/4629 http://news.php.net/php.pear.qa/4604 Greg, did you do anything related to it? I don't see any further replies to the mails. -- Regards/Mit freundlichen Grüßen Christian Weiske -= Geeking around in the name of science since 1982 =- signature.asc Description: PGP signature
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
2008/10/2 Hannes Magnusson <[EMAIL PROTECTED]>: > On Thu, Oct 2, 2008 at 03:57, Kalle Sommer Nielsen <[EMAIL PROTECTED]> wrote: >> Hi Hannes >> >> 2008/10/1 Hannes Magnusson <[EMAIL PROTECTED]>: >>> 1) cvs -d:pserver:[EMAIL PROTECTED]/repository co phpdoc >>> 1b) cd phpdoc >>> 2) php configure.php >>> 3) pear channel-discover doc.php.net && pear install doc.php.net/phd-beta >> >> Actually this isn't always as easy on Windows, mainly because the >> go-pear seems to not like Windows at all, I still havn't been able to >> install pear with go-pear. > > Why not? Getting any errors? I thought it was installed by default by > the installer? I do not use the installer, I simply just extra php to the folder I want to use it from. When I use: C:\PHP_5_2\>go-pear It asks me to install a system or local wide install, then it comes up with some configuratives where the path to CLI php.exe always is missing. If I press Enter to continue it just shows the same list of paths, if I type all after have configured path 12 (to CLI php.exe), it will end up with this error: 1-12, 'all' or Enter to continue: all Installation base ($prefix) [Inputfejl: Der er ikke noget filtypenavn i "C:\Users\Kalle".] : (Input error: There is no filetype name in "C:\Users\Kalle") I guess its because the installer doesn't support folders with spaces as the directory is called "C:\Users\Kalle Sommer Nielsen\" So you cannot get further or atleast I can't because my username has spaces. I had to edit the phd.bat manually to make it work, not that it was any major but anyway. > > -Hannes > -- Kalle Sommer Nielsen
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
On Thu, Oct 2, 2008 at 03:57, Kalle Sommer Nielsen <[EMAIL PROTECTED]> wrote: > Hi Hannes > > 2008/10/1 Hannes Magnusson <[EMAIL PROTECTED]>: >> 1) cvs -d:pserver:[EMAIL PROTECTED]/repository co phpdoc >> 1b) cd phpdoc >> 2) php configure.php >> 3) pear channel-discover doc.php.net && pear install doc.php.net/phd-beta > > Actually this isn't always as easy on Windows, mainly because the > go-pear seems to not like Windows at all, I still havn't been able to > install pear with go-pear. Why not? Getting any errors? I thought it was installed by default by the installer? -Hannes
[PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
Hi Hannes 2008/10/1 Hannes Magnusson <[EMAIL PROTECTED]>: > On Wed, Oct 1, 2008 at 20:03, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: >> >> On Wed, Oct 1, 2008 at 19:17, Elizabeth M Smith <[EMAIL PROTECTED]> wrote: >>> >>> tools). Writing in XML is not a natural thing. An online interface >>> where people can edit docs would seriously boost people helping out. >>> Why do you think there are so many user notes in the PHP manual ;) >> >> I think a web-based tool that would allow to generate standard docbook pages >> (at least most primitive ones) and allow to edit certain sections while >> supporting some basic stuff like paragraphs, links, styles (italic, bold) >> etc. would be a HUGE help. I can write docbook and have experience with it >> and I still find it annoying and hard to remember all the details, I can >> only imagine how intimidating it appears to a newbie. > > You were extremely unlucky when you wrote the intl docs, sorry for that! :) > > Now we do however have skeletons for 99% cases, and even a 5minutes > tutorial on howto document exceptions[1]. > NOTE: Most of the 5minutes are spent explaining how to build the docs. > > > Sure, an online editing tool would be great but I don't think that is > a realistic expectation for the time being. I'd rather want PHP5.3 > documented before its release then someone spending all their time on > weird dirty mixed application that will probably not be ready until > PHP6. > > > >>> Why do you think there are so many user notes in the PHP manual ;) > > Speaking of which, we do also need volunteers to review them. > If you login to php.net (via bugsweb or > http://master.php.net/manage/users.php) you'll see three boxes > above(to the right) of all user notes: > 1) Edit (rarely used, mostly just to add tags for syntax > highlighting if people missed them > 2) Reject the note (questions and stuff like that) > 3) Delete (wtf notes, bad code/advise, huge code...) > > _EVERYONE_ with a php.net account can do that and it would be greatly > appreciated if people would remove the horror notes when they > encounter them. It would even be more appreciated if extension > maintainers regularly review the notes attached to their extensions > (currently Derick is prettymuch the online who does that). > >>> However...you will have to wade through the bad docs too. And I have no >>> solution for dealing with the "three million tools" issues. > > I don't understand this argument. > All you need for building and view the documentations are 4things: CVS > client, PHP, text editor and a browser. All of which you have > installed already if you have any interest in PHP at all. > > To build and view the docs follow these 6steps for the first time, > after you follow it once you only have to repeat 3 of the steps > > 1) cvs -d:pserver:[EMAIL PROTECTED]/repository co phpdoc > 1b) cd phpdoc > 2) php configure.php > 3) pear channel-discover doc.php.net && pear install doc.php.net/phd-beta Actually this isn't always as easy on Windows, mainly because the go-pear seems to not like Windows at all, I still havn't been able to install pear with go-pear. To install PhD I had to manually edit the phd.bat for it to work. > 4) phd -d .manual.xml -t chunkedhtml > 5) firefox html/index.html > 6) notepad en/reference/spl/spl/book.xml > > Now repeat step 2, 4, and 5 after each change you make with you text editor. > > If you can install PHP on your operating system then you can build the > docs and contribute. > > -Hannes > > [1] http://doc.php.net/php/dochowto/article.thequicky.exceptions.php > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Kalle Sommer Nielsen
Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
I'd be happy to serve as your test subject. I'll post back here when I've done it (sometime this evening once I'm home from the office). Brandon On Wed, Oct 1, 2008 at 4:01 PM, Hannes Magnusson <[EMAIL PROTECTED] > wrote: > On Wed, Oct 1, 2008 at 21:27, Brandon Savage <[EMAIL PROTECTED]> > wrote: > > All, > > > > I am what I guess you'd call a "newbie" - Elizabeth got me on this list > > during ZendCon and though I've been following it I still have no idea how > > the doc editing process works. I'm exactly who you want this kind of tool > > for - a new contributor who is eager to contribute but unsure about how > to > > do so. > > Would you mind being my test-subject then? :) 15minutes of your time > (plus couple of minutes to reply back) is all I ask for. > Its an easy task: Document the LogicException exception. > > The exception has no methods (except for inherited once) and how to > document exception (from a-z, everything from obtaining the source to > building them to actually creating the doc) is already documented at > http://doc.php.net/php/dochowto/article.thequicky.exceptions.php > > If it takes more then 15minutes you can quit and we'll have to try to > find better ways. If however you manage to do it in 15minutes or less, > please post the file to [EMAIL PROTECTED] > > -Hannes >
Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
On Wed, Oct 1, 2008 at 21:27, Brandon Savage <[EMAIL PROTECTED]> wrote: > All, > > I am what I guess you'd call a "newbie" - Elizabeth got me on this list > during ZendCon and though I've been following it I still have no idea how > the doc editing process works. I'm exactly who you want this kind of tool > for - a new contributor who is eager to contribute but unsure about how to > do so. Would you mind being my test-subject then? :) 15minutes of your time (plus couple of minutes to reply back) is all I ask for. Its an easy task: Document the LogicException exception. The exception has no methods (except for inherited once) and how to document exception (from a-z, everything from obtaining the source to building them to actually creating the doc) is already documented at http://doc.php.net/php/dochowto/article.thequicky.exceptions.php If it takes more then 15minutes you can quit and we'll have to try to find better ways. If however you manage to do it in 15minutes or less, please post the file to [EMAIL PROTECTED] -Hannes
Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
All, I am what I guess you'd call a "newbie" - Elizabeth got me on this list during ZendCon and though I've been following it I still have no idea how the doc editing process works. I'm exactly who you want this kind of tool for - a new contributor who is eager to contribute but unsure about how to do so. I've always been a fan of finding easy ways to do hard things. And I think that this kind of system would be great for contributors, new and old alike. My .02. Brandon On Wed, Oct 1, 2008 at 3:06 PM, Hannes Magnusson <[EMAIL PROTECTED] > wrote: > On Wed, Oct 1, 2008 at 20:03, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > > > > On Wed, Oct 1, 2008 at 19:17, Elizabeth M Smith <[EMAIL PROTECTED]> > wrote: > >> > >> tools). Writing in XML is not a natural thing. An online interface > >> where people can edit docs would seriously boost people helping out. > >> Why do you think there are so many user notes in the PHP manual ;) > > > > I think a web-based tool that would allow to generate standard docbook > pages > > (at least most primitive ones) and allow to edit certain sections while > > supporting some basic stuff like paragraphs, links, styles (italic, bold) > > etc. would be a HUGE help. I can write docbook and have experience with > it > > and I still find it annoying and hard to remember all the details, I can > > only imagine how intimidating it appears to a newbie. > > You were extremely unlucky when you wrote the intl docs, sorry for that! :) > > Now we do however have skeletons for 99% cases, and even a 5minutes > tutorial on howto document exceptions[1]. > NOTE: Most of the 5minutes are spent explaining how to build the docs. > > > Sure, an online editing tool would be great but I don't think that is > a realistic expectation for the time being. I'd rather want PHP5.3 > documented before its release then someone spending all their time on > weird dirty mixed application that will probably not be ready until > PHP6. > > > > >> Why do you think there are so many user notes in the PHP manual ;) > > Speaking of which, we do also need volunteers to review them. > If you login to php.net (via bugsweb or > http://master.php.net/manage/users.php) you'll see three boxes > above(to the right) of all user notes: > 1) Edit (rarely used, mostly just to add tags for syntax > highlighting if people missed them > 2) Reject the note (questions and stuff like that) > 3) Delete (wtf notes, bad code/advise, huge code...) > > _EVERYONE_ with a php.net account can do that and it would be greatly > appreciated if people would remove the horror notes when they > encounter them. It would even be more appreciated if extension > maintainers regularly review the notes attached to their extensions > (currently Derick is prettymuch the online who does that). > > >> However...you will have to wade through the bad docs too. And I have no > >> solution for dealing with the "three million tools" issues. > > I don't understand this argument. > All you need for building and view the documentations are 4things: CVS > client, PHP, text editor and a browser. All of which you have > installed already if you have any interest in PHP at all. > > To build and view the docs follow these 6steps for the first time, > after you follow it once you only have to repeat 3 of the steps > > 1) cvs -d:pserver:[EMAIL PROTECTED]/repository co phpdoc > 1b) cd phpdoc > 2) php configure.php > 3) pear channel-discover doc.php.net && pear install doc.php.net/phd-beta > 4) phd -d .manual.xml -t chunkedhtml > 5) firefox html/index.html > 6) notepad en/reference/spl/spl/book.xml > > Now repeat step 2, 4, and 5 after each change you make with you text > editor. > > If you can install PHP on your operating system then you can build the > docs and contribute. > > -Hannes > > [1] http://doc.php.net/php/dochowto/article.thequicky.exceptions.php >
Re: [PHP-DOC] Re: [PHP-DEV] Re: [PHP-DOC] [DOC] Commit messages dead?
On Wed, Oct 1, 2008 at 20:03, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > > On Wed, Oct 1, 2008 at 19:17, Elizabeth M Smith <[EMAIL PROTECTED]> wrote: >> >> tools). Writing in XML is not a natural thing. An online interface >> where people can edit docs would seriously boost people helping out. >> Why do you think there are so many user notes in the PHP manual ;) > > I think a web-based tool that would allow to generate standard docbook pages > (at least most primitive ones) and allow to edit certain sections while > supporting some basic stuff like paragraphs, links, styles (italic, bold) > etc. would be a HUGE help. I can write docbook and have experience with it > and I still find it annoying and hard to remember all the details, I can > only imagine how intimidating it appears to a newbie. You were extremely unlucky when you wrote the intl docs, sorry for that! :) Now we do however have skeletons for 99% cases, and even a 5minutes tutorial on howto document exceptions[1]. NOTE: Most of the 5minutes are spent explaining how to build the docs. Sure, an online editing tool would be great but I don't think that is a realistic expectation for the time being. I'd rather want PHP5.3 documented before its release then someone spending all their time on weird dirty mixed application that will probably not be ready until PHP6. >> Why do you think there are so many user notes in the PHP manual ;) Speaking of which, we do also need volunteers to review them. If you login to php.net (via bugsweb or http://master.php.net/manage/users.php) you'll see three boxes above(to the right) of all user notes: 1) Edit (rarely used, mostly just to add tags for syntax highlighting if people missed them 2) Reject the note (questions and stuff like that) 3) Delete (wtf notes, bad code/advise, huge code...) _EVERYONE_ with a php.net account can do that and it would be greatly appreciated if people would remove the horror notes when they encounter them. It would even be more appreciated if extension maintainers regularly review the notes attached to their extensions (currently Derick is prettymuch the online who does that). >> However...you will have to wade through the bad docs too. And I have no >> solution for dealing with the "three million tools" issues. I don't understand this argument. All you need for building and view the documentations are 4things: CVS client, PHP, text editor and a browser. All of which you have installed already if you have any interest in PHP at all. To build and view the docs follow these 6steps for the first time, after you follow it once you only have to repeat 3 of the steps 1) cvs -d:pserver:[EMAIL PROTECTED]/repository co phpdoc 1b) cd phpdoc 2) php configure.php 3) pear channel-discover doc.php.net && pear install doc.php.net/phd-beta 4) phd -d .manual.xml -t chunkedhtml 5) firefox html/index.html 6) notepad en/reference/spl/spl/book.xml Now repeat step 2, 4, and 5 after each change you make with you text editor. If you can install PHP on your operating system then you can build the docs and contribute. -Hannes [1] http://doc.php.net/php/dochowto/article.thequicky.exceptions.php
