headers
Jon Wood | 1 Dec 2002 02:49

Patch for Auth.php

Below is a patch to Auth.php fixing the creation of the Auth object in
the advanced example, including the DSN in the options array.

Jon

------------------------------------

diff -u -r1.44 Auth.php
--- Auth.php	1 Nov 2002 10:37:27 -0000	1.44
+++ Auth.php	1 Dec 2002 01:44:13 -0000
 <at>  <at>  -73,12 +73,10  <at>  <at> 
  *  Set up the Auth class in an auto_prepend file like this:
  *
  *    require_once "Auth/Auth.php";
- *
- *    // define dsn
- *    $dsn = "mysql://martin:test <at> example.com/test";
  *  
  *    // set options
  *    $options = array(
+ *      'dsn'           => 'mysql://martin:test <at> example.com/test',
  *      'table'         => 'myuser',
  *      'usernamecol'   => 'userlogin',
  *      'passwordcol'   => 'cryptpassword'
 <at>  <at>  -91,7 +89,7  <at>  <at> 
  *    }
  *
  *    // create auth object
- *    $myauth = new Auth( $dsn, $options, 'myloginform', true);
+ *    $myauth = new Auth($options, 'myloginform', true);
(Continue reading)

Permalink | Reply | 0 comments |
headers
Greg Beaver | 1 Dec 2002 05:38
Favicon

Update: phpDocumentor development

Hello all,

There have been some issues with the PEAR release of phpDocumentor due to
problems in pear.in for windows which render the project unusable without
minor adjustments.  These problems have been fixed and will be available
with the next release.  In the meantime, a clean install from
http://www.phpdoc.org will work until the PEAR release is fixed up.

The peardoc2 converter is now at about 95% complete.  The biggest stumbling
blocks were recently solved.  The spec for phpDocumentor's descriptions
allows certain html tags for formatting such as <b>, <i>, <ul>, etc.  This
required parsing the long description and replacing these with their docbook
equivalents, as well as parsing out paragraphs.  Using a derivative of the
parser that phpDocumentor uses to parse php and a new options.ini file for
every template, this problem was solved.  The other larger problem involved
a new DocBook format for package-level docs (tutorials would go there).
Currently, the spec calls for html-format package-level docs, but html is
not rigorous enough to convert back into DocBook reliably.  By allowing a
subset of DocBook tags (basically everything but the table tags), it is
possible to use the same derivative parser with a few changes to parse
DocBook-style package pages and spit out html-ready or pdf-ready package
pages.

With these solutions, the focus turns to moving the old HTMLdefaultConverter
and its 7 templates into a new Smarty-based converter that will have all the
flexibility of the HTMLSmartyConverter and the old look.  After this is
completed, there will simply be a few weeks of ironing out the mistakes that
will inevitably turn out in the peardoc2 templates of the DocBook converter
(unless I just happen to have understood the format perfectly on the first
try), and we will be ready for version 1.2.0rc1
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arnaud Limbourg | 1 Dec 2002 10:27
Picon

Re: Update: phpDocumentor development

> Hello all,
> 
> There have been some issues with the PEAR release of phpDocumentor due to
> problems in pear.in for windows which render the project unusable without
> minor adjustments.  These problems have been fixed and will be available
> with the next release.  In the meantime, a clean install from
> http://www.phpdoc.org will work until the PEAR release is fixed up.
> 
> The peardoc2 converter is now at about 95% complete.  The biggest stumbling
> blocks were recently solved.  The spec for phpDocumentor's descriptions
> allows certain html tags for formatting such as <b>, <i>, <ul>, etc.  This
> required parsing the long description and replacing these with their docbook
> equivalents, as well as parsing out paragraphs.  Using a derivative of the
> parser that phpDocumentor uses to parse php and a new options.ini file for
> every template, this problem was solved.  The other larger problem involved
> a new DocBook format for package-level docs (tutorials would go there).
> Currently, the spec calls for html-format package-level docs, but html is
> not rigorous enough to convert back into DocBook reliably.  By allowing a
> subset of DocBook tags (basically everything but the table tags), it is
> possible to use the same derivative parser with a few changes to parse
> DocBook-style package pages and spit out html-ready or pdf-ready package
> pages.

Cool, that will be a great help !

It enable us to spend more time writing tutorials ;)

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pierre-Alain Joye | 1 Dec 2002 15:29

Re: Update: phpDocumentor development

On Sat, 30 Nov 2002 23:38:30 -0500
"Greg Beaver" <greg <at> chiaraquartet.net> wrote:

> Hello all,
> 
> There have been some issues with the PEAR release of phpDocumentor due
> to problems in pear.in for windows which render the project unusable
> without minor adjustments.  These problems have been fixed and will be
> available with the next release.  In the meantime, a clean install
> from http://www.phpdoc.org will work until the PEAR release is fixed
> up.

What kind of problem did you get with pear.in under windows ? There is a
known bug due to php constants, which will be hopefully solved with the
4.3.0 release. But basically, it is easier to fix manually.

The main problem I have with phpDocumentor is the name of the command,
which is the same as the PHPDoc (phpdoc), which make impossible to
install the both packages.

> The other larger problem involved a new DocBook
> format for package-level docs (tutorials would go there).

How do you plan the use of phpDocumentor for the creation of tutorials ?
My favourite idea for this purpose is to allow people to use their
favourite word processing tools and convert it to docbook. This is the
way I choose for DocConvert.  That makes the work easier for the authors
as well for the translators.

> Currently, the spec calls for html-format package-level docs, but html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian Dickmann | 1 Dec 2002 17:31
Picon
Picon

Re: Problem with WebInstaller and SAPI/CGI

>   the "Next >>" link is printed as
>
>    http://wopr/php/php-cgi.exe?command=list-all&pageID=2

Richy needs to release a patched version of Pager.
The patch was committed a few weeks ago.

Christian Dickmann

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Christian Dickmann | 1 Dec 2002 17:46
Picon
Picon

Re: [go-pear] New web version of go-pear

> can we see that progress bar into somthing pearized :)

I will create such a package. But not now :)

Christian Dickmann

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Neil Santos | 1 Dec 2002 18:39

CMSystem written in PHP

>> [Monday] 02/12/2002 :: 01:20 -- NEWMSG

Hello everyone,

I'm new in this list, and I thought I should introduce myself a bit
first, before proceeding with the original purpose of this message.

My name is, as you may have already guessed, Neil Santos, and I'm from
the Philippines.  I began tinkering with PHP about a year ago, when I
wanted to put up a dynamic Web site (it used to be posted on
http://www.sector7bbs.com/aktuation/ but it's dead now).

Lately, I've offered to help Sam Williams in redesigning, and ultimately
maintaining http://www.faifzilla.org/.  I wanted to create an easier way
to modify the design of the site, without having to mess with the actual
pages.  CSS has gone a long way, but I thought I'd try pushing my luck a
little further, and make it easier on other people as well, especially
Sam.

I wanted to create my own CMS (content management system, for those who
aren't familiar with the term), since most of the CMSystems out are
commercial; something I didn't think was fit for FAIFzilla.

I didn't want to create one huge system, centered around one project, so
I ended up creating a parser encapsulated in a class.  People could then
inherit the parser class (which I've taken to calling `Raven'), and just
attach the functionality they need and it lacks.

While most of the functionality you'd expect in a CMS is done, the
project as a whole isn't, and is, in my opinion, far from being so.
(Continue reading)

Permalink | Reply | 10 comments |
headers
Björn Schotte | 1 Dec 2002 20:10
Picon

Re: CMSystem written in PHP

Hi,

* Neil Santos wrote:
> I'd like to be able to submit Raven into the PEAR database, if you, the

Besides the fact that there are around a million PHP based
CMSes out there, I don't think PEAR should get an application
repository.

So -1 & only my 0,02 EUR, Björn.

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 5 comments |
headers
Tal Peer | 1 Dec 2002 20:14
Picon

Re: CMSystem written in PHP

Björn Schotte wrote:
> Hi,
> 
> * Neil Santos wrote:
> 
>>I'd like to be able to submit Raven into the PEAR database, if you, the
> 
> 
> Besides the fact that there are around a million PHP based
> CMSes out there, I don't think PEAR should get an application
> repository.
> 
> So -1 & only my 0,02 EUR, Björn.
> 
-1 too. PEAR (as I see it) is a home for abstract classes, that means, 
that CMSes should *use* it, not be a part of it.

My 2 agorot..

-- 
Tal Peer
tal <at> php.net

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
George Schlossnagle | 1 Dec 2002 20:26
Favicon

Re: CMSystem written in PHP


On Sunday, December 1, 2002, at 02:10  PM, Björn Schotte wrote:

> Hi,
>
> * Neil Santos wrote:
>> I'd like to be able to submit Raven into the PEAR database, if you, 
>> the
>
> Besides the fact that there are around a million PHP based
> CMSes out there, I don't think PEAR should get an application
> repository.

While I agree, we may want to rename it from the PHP Extension and 
APPLICATION Repository then.  :)

That having been said I have three comments:

1) making your CMS available in PEAR package format may make 
installation easier for your users.
2) Perhaps there are components of your CMS that would be appropriate 
for PEAR (I haven't looked)
3) GPL'd software in PEAR kinda sucks.

>
> So -1 & only my 0,02 EUR, Björn.
>
> -- 
> PEAR Development Mailing List (http://pear.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
(Continue reading)

Permalink | Reply | 3 comments |

Gmane