ID: 21970
Updated by: [EMAIL PROTECTED]
Reported By: philip at cornado dot com
Status: Assigned
Bug Type: Documentation problem
Operating System: all
PHP Version: Irrelevant
Assigned To: aidan
New Comment:
>- techniques.patterns
>PHP 4 / 5 singleton + factory patterns
Before you'll do such an evil thing consider writing an article
"patterns misusing borders". There was once a good article about that
on phppatterns, but the site seems to be closed. And consider new
chapters like "Debugging PHP" and "Debugging Patterns" first. My IMHO,
but before patterns one should use project planning tools like
rationale to avoid his mind wasting time doing coding for coding. Also
consider alternative chapter "Framework approach" with OO,
function-like and pattern-built framework problems overview. I know
this is complicated, but these are questions every developer is
interested in - not about what is patterns and how they cool. Patterns
are good in reversed languages like Java and mostly for complex
projects with complicated structure (observers). Without project
planning and product development methodologies patterns are not
maintanable.
>- techniques.magic-quotes
>Info moved and aggregated from the security / faq
>
>- techniques.register-globals
>Info moved and aggregated from the security / faq
No. Security features should be in securty section. Users should not
read through all PHP manual and especially through patterns just to
figure out how to secure their server.
>* All the material in the features section will be
>incorporated into the techniques section.
I think there is clear distinction from "language feature" and
"techniques of using language feature"
+ Using PHP in...
...scripting (command line)
...scripting (application)
...integration (Java)
...integration (.NET)
...platform independent/dependent
...interfaces (smarty, GTK, plugins)
...enterprise
...PHP bussiness dictionary (like what is thin client, multitier arch
and so on - the basics everybody is speaking about, but nobody wants to
explain in common words)
Well, seems like all this info is subject to separate documentation
pack - it can contain a lot of info and clutter search results for
those newbies, who use PHP manual solely as reference to functions and
PHP bugs.
Previous Comments:
------------------------------------------------------------------------
[2005-09-09 09:33:27] [EMAIL PROTECTED]
Hmm, forgot about this in my last reply, but if we're adding "common
techniques" and such we should add a techniques.design.pagination, as
it's something extremely common that I see a lot of new programmers
asking about.
------------------------------------------------------------------------
[2005-09-09 09:27:40] [EMAIL PROTECTED]
Certainly techniques.patterns should be techniques.design.patterns?
------------------------------------------------------------------------
[2005-09-09 08:28:49] [EMAIL PROTECTED]
Summarising the feedback,
* I think we've agreed "techniques" is the way to go in terms of naming
the new section.
* I think getting-started will stay where it is.
* The new techniques section will be placed after the security
section.
* All the material in the features section will be incorporated into
the techniques section.
And the following new sections will be created,
- techniques.include-path
See philip's original post.
Also, I notice a lot of questions regarding include_paths in included
files, where the include path is relative to, getcwd, etc. This would
make a nice addition to the include-path section.
- techniques.patterns
PHP 4 / 5 singleton + factory patterns
- techniques.magic-quotes
Info moved and aggregated from the security / faq
- techniques.register-globals
Info moved and aggregated from the security / faq
- techniques.command-line
All the information about running PHP from the CLI
?- techniques.databasing
general good database practices (also moved from security section)
So far I think everyone has agreed on these. The ones we're not too
sure about being the tutorial-type sections. Perhaps these could be
placed in a subsection of techniques called "design".
- techniques.design.black-box
Detailing the foo.php?page=contact design
------------------------------------------------------------------------
[2005-01-25 07:44:08] [EMAIL PROTECTED]
Somewhere down the line this bug report got renamed so be sure it's not
closed until include_path is properly (extensively) documented.
Not everything belongs in a tutorial...I agree with Goba on all points.
------------------------------------------------------------------------
[2005-01-24 16:44:24] [EMAIL PROTECTED]
I agree with both Anatoly & Goba, here.
- Getting started needs to be easily found by new developers.
- And ~"Techniques" is a good name for the section we envisioned as
"Tutorials" they're programming (usually php-specific or web-specific)
techniques.
- Perhaps a note should be dropped into the intro to
"features/techniques" section that links to Getting Started.
S
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21970
--
Edit this bug report at http://bugs.php.net/?id=21970&edit=1
