#21970 [Com]: Creating a new Tutorial section

ID: 21970 Comment by: cxv at bmn dot jb Reported By: philip at cornado dot com Status: Open Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment: http://www.meta-fx.com forex ÝÇÑ˜Ó Previous Comments: ------------------------------------------------------------------------ [2007-09-27 20:30:01] 66 at wp dot pl cf ------------------------------------------------------------------------ [2007-02-26 09:22:33] philip@php.net unassigned ------------------------------------------------------------------------ [2006-11-07 03:03:35] akaka at kadkad dot com asdsd ------------------------------------------------------------------------ [2005-09-09 20:53:07] goba@php.net Newbies don't use the manual for just reference purposes, it is quite on the contrary. ------------------------------------------------------------------------ [2005-09-09 11:59:09] techtonik@php.net >- 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. ------------------------------------------------------------------------ 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