I would rather take some code example and show refactoring facilities of NetBeans in details. In case the first line reads /, it is interpreted as the start of a comment block. The /// is ignored as well since it is interpreted as // /. It would make a nice part of a book about programming architecture, but doesn't really belong to this one. In case the first line reads //, it is interpreted as //, thus you comment the and don't comment the remainder of the block. Don't get me wrong, that's a pretty good introduction to the domain-driven design, concise and easy to grasp even for a beginner. I've been a bit confused to find at the end of the book a chapter not really connected to the main thread (NetBeans IDE). I can't imagine someone not have asked about it on Stack Overflow (e.g., like for MySQL/SQL). By the way, as for plugins coverage, Git and Selenium Module for PHP are good choices, but what about phpcsmd or, let's say, NetBeans UML? As this may be the top search engine hit for 'PHP comment characters', see Comments (official documentation) - 'PHP supports 'C', 'C++' and Unix shell-style (Perl style) comments.'. Besides, introductions to popular plugins such as Prefixr and ZendCoding would be most welcome. Thus, for a book about NetBeans I would expect some input regarding HTML refactoring, CSS auto-completion, JavaScript code templates and so on. Well, the authors himself shows study cases using JavaScript, jQuery, CSS and HTML. And NetBeans provides comprehensive environment which covers all our needs for web-development including HTML, XML, CSS (with plugins CoffeeScript, TypeScript and so on). But in practice we don’t do just PHP coding, but web-development. I will definitely recommend the book to my colleges.Īll over the book the author focuses on the Netbeans facilities meant for PHP only. Oh, I've got liked to that lively trick of using subsections such as "Time for action", "What just happened?", "Have a go hero", "Pop quiz" that prevent you of getting lost during the reading. ![]() Every subject adheres the pattern: task, solution, what we have learned. Besides, covering the common facilities of NetBeas the books provides comprehensive input regarding automated-testing flow, version control integrated tools on Git example, PHPDoc practices and API-documentation generation. In order to avoid the case "Why didn't I use it for all this time?!", I would even call it as a must-read book for anybody working with NetBeans. After years of usage you still can run into an overlooked tool which remarkably boosts your coding productivity. At the first glance it looks quite simple, but the deeper you are, the more layers you discover. I, personally, have been using NetBeans for about 4 years and still find in the book the features I wasn't aware about or unfairly ignored for so long. You have to go to Tools -> Options -> Miscellaneous -> Files and add the necessary file names or extensions under 'files ignored by the IDE' in the Ignored Files Pattern field regexp. ![]() It must be valuable as for beginners as for experienced NetBeans users. In my version of Netbeans (6.9.1 on Win 7), there is no button under Project Properties -> Source in which to enter exclusion patterns. One of those where it's hard to put the book down until the end. However, a little familiarity with PHP development is expected. Familiarity with NetBeans is not assumed. It's non-standard, at least.Recently I've laid my hands on a copy of "PHP Application Development with NetBeans" by M A Hossain Tonu ( It appeared to be a really nice reading. A Beginner's Guide The book is aimed at PHP developers who wish to develop PHP applications while taking advantage of NetBeans functionality to ease their software development efforts and utilize the powerful features of the IDE. Based on that, I would say leave out the void. phpDocumentor will display the optional description unmodified. In addition, if a function returns multiple possible values, separate them using the | character, and phpDocumentor will parse out any class names in the return value. ![]() If a class name is used as the datatype in the tag, phpDocumentor will automatically create a link to that class's documentation. ![]() If you want to explicitly show multiple possible return types, list them pipe-delimited without spaces (e.g. The datatype should be a valid PHP type (int, string, bool, etc), a class name for the type of object returned, or simply "mixed". is an alias for to support tag formats of other automatic documentors The tag is used to document the return value of functions or methods. The website datatype datatype1|datatype2 description After a little googling, the wikipedia page This tag should not be used for constructors or methods defined with a void return type. If it makes it clear for the documentation, then leave it in, but it isn't strictly necessary.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |