Good idea.

Get a CVS account to work w/ the PHPDOC team and start
writing some of the sections you suggest. Although
they would rather be in a tutorial document IMHO.

The PHPDOC team/list is the place to suggest this
ideas, not the notes to the manual.

(CC'ing to the phpdoc list)

--- [EMAIL PROTECTED] wrote:
> This is only my idea for PHP manual. Hope this is
> the right place to post.
> 
> I think current manual is great, useful and well
> documented. Great job!! Manual is enough for those
> who are programmed in other language especially C++
> or Java. However, the manual is not enough for many
> new PHP users, especially for newbie programmers. I
> think Feature section is a bit too advanced for new
> PHP users. It would be nice to have a new sub
> section in Features section or totally new section
> like "Programming PHP". It might have sections like
> "New to PHP/CGI/Web Programming", "Interact with
> browsers","Interact with server", "PHP modules",
> "Using Database" and "Beyond PHP" (It also time say
> good-bye to PHP3 because it seems many PHP4 features
> are not documented due to incompatibility with
> PHP3(?).
> 
> I think contents does not have be like a
> "Programming Book". I think brief descriptions for
> each topic is enough for starters. There would be
> different opinions putting those things in the
> manual. This is only my idea for new section.
> 
> [New to PHP/CGI/Web Programming] 
>  What is CGI
>    - Brief explanation of CGI.
>  Difference between client side script and server
> side script
>    - It seems many beginners are confusing and keep
> getting the similar or same questions on list.
>  About Dynamic HTML
>    - What is Dynamic HTML and Server generated HTML.
>  List of useful references.
>    - Many user does not read RFC, Cookie Spec, etc.
>    - Link to Zend tutorials/link to other similar
> site.
>    - XML related sites.
>  Simple form example to demonstrate how PHP works.
>  And so on.
> 
> [Interact with browsers]
>  How user data (get/post/cookie) is set
>   - $GLOBALS, $HTTP_GET_VARS, $HTTP_POST_VARS,
> $HTTP_COOKIE_VARS.
>   - It seems many users do not use $HTTP_*_VARS and
> use globals instead, even if use of $HTTP_*_VARS
> variables are recommended. 
>  What kind of request header info is set as server
> variable. 
>   - Common variables on various environment like
> REQUEST_URI, HTTP_REFERER, at least.
>  How to get array value from browser. (Is this
> documented somewhere?)
>  How to determine users browser.
>  How to use header() function and its reference. (It
> seems many users do not read RFC)
>  How to make a session.
>  And so on.
> 
> [Interact with server]
>  This section may be difficult to write since PHP
> supports many servers. Apache/IIS is the most
> popular one I believe. How about make a this section
> only applicable to Apache Module and IIS?
>  What is $HTTP_SERVER_VARS, $HTTP_ENV_VARS.
>  How to change PHP settings locally.
>  How to set up virtual host with Apache. 
>  And so on.
> 
> [PHP extensions]
>  For new users, PHP extension is better to be
> explained.
>  What is module.
>  What is default modules.
>  Brief description for each modules. What is for?
> What is does.
>  How to install new module to IIS/Apache.
>  And so on.
> 
> [Interact with database]
>  Since PHP works with many databases, it would be
> nice to describe those modules briefly.
> 
> [Beyond PHP]
>   Extending PHP and Interaction with other systems.
>   Creating PHP modules
>     - explain that users can write their own modules
> if needed.
>   Using COM
>   Using Java
>   Using XML-RPC/Soap
>   Others?
> 
>  http://www.php.net/manual/en/features.php 
> 
> 
> -- 
> PHP Notes Mailing List (http://www.php.net/)
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> To contact the list administrators, e-mail:
> [EMAIL PROTECTED]
> 


=====
--- Jesus M. Castagnetto <[EMAIL PROTECTED]>

__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

Reply via email to