Expert PHP 5 Tools Packt Open Source Project Royalties
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Documenting Your PHP Code with Phpdoc and Docbook XML -.. Phpbee
Documenting your PHP code with PHPDoc and DocBook XML Gábor Hojtsy International PHP Conference 2002 November 3-6. 2002. Questions • Who used/know about PHPDoc? • JavaDoc? • DocBook XML? • XML at all? • Anyway who documents his/her code regularly using any format? Documenting your PHP code 2 About myself •Gábor Hojtsy • [email protected] • Student at Budapest University of Technology and Economics • PHP.net Webmasters Team • PHP Documentation Team [build system, XSLT rendering, CHM format, Hungarian translation] Documenting your PHP code 3 Session outline • Documentation types • Developer documentation • Possible formats • Inline documentation in PHP code • Standalone documentation in DocBook • Tools to handle the two and merge contents Documenting your PHP code 4 Documentation types • Software written in PHP • Plans, concepts, specification [UML] • As the software is stable – User’s documentation • Help buttons on web pages • Support pages, simple manuals – Developer’s documentation Documenting your PHP code 5 Developer’s documentation • General information – Authors, License, Links • Concepts explained – Reasons to develop this software – Technologies, libraries used • Implementation details – Meta information about classes, functions, variables, constants; with usage examples • Historical information – Previously supported API[s], future directions, todo Documenting your PHP code 6 Expected qualities • All information in one documentation • Easily accessible / modifiable – Industry- wide used format – Cross platform tools for viewing and -
Zend Studio 5.5 for I5 /OS
Zend StudioTM User Guide: Zend Studio 5.5 for i5 /OS By Zend Technologies, Inc. www.zend.com Zend Studio 5.5 for i5 /OS – User Guide Disclaimer The information in this document is subject to change without notice and does not represent a commitment on the part of Zend Technologies Ltd. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser’s personal use, without the written permission of Zend Technologies Ltd. All trademarks mentioned in this document, belong to their respective owners. © 1999-2007 Zend Technologies Ltd. All rights reserved. Zend Studio for i5/OS version 5.5 issued January 2007. Product Version: Zend Studio for i5/OS version 5.5 DN: ZSi5_OS-UG-270507-5.5-005 www.zend.com Page ii Zend Studio 5.5 for i5 /OS – User Guide Table of Contents Chapter 1 - Introduction.............................................................................................. 1 Zend Studio Components........................................................................................... 1 Zend Studio for i5/OS version 5.5 ............................................................................ 2 Zend Studio Workflow .............................................................................................. 3 New in this Version ................................................................................................. 4 Highlighted Features and Benefits -
Facebook API Developers Guide
Available as a PDF Electronic Book or Print On Demand Facebook API Developers Guide CHAPTER 1 Introducing the Facebook Platform . 1 CHAPTER 2 Getting Ready for Facebook Application Development . 9 CHAPTER 3 Learning Facebook Platform Fundamentals . 31 CHAPTER 4 Building a Facebook Application, Start to Finish. 71 CHAPTER 5 Going Further with Your Application . 129 137 PAGES Wayne Graham www.allitebooks.com www.allitebooks.com Facebook API Developers Guide WAYNE GRAHAM www.allitebooks.com Facebook API Developers Guide Copyright © 2008 by Wayne Graham All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13: 978-1-4302-0969-0 ISBN-10: 1-4302-0969-0 eISBN-13: 978-1-4302-0970-6 Printed and bound in the United States of America (POD) Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trade- marked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Ben Renow-Clarke Technical Reviewer: Mark Johnson Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Kevin Goff, Matthew Moodie, Joseph Ottinger, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Senior Project Manager: Tracy Brown Collins Copy Editor: Kim Wimpsett Compositor: Richard Ables Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013. -
E-LEARNING FRAMEWORKS 29 Introduction
Voice Interactive Classroom, a service- oriented software architecture to enable cross-platform multi-channel access to Internet-based learning Víctor Manuel Álvarez García UNIVERSITY OF OVIEDO DEPARTMENT OF COMPUTER SCIENCE In Partial Fulfilment of the Requirements for the Degree of EUROPEAN DOCTOR OF PHILOSOPHY Universidad de Oviedo Voice Interactive Classroom, a service-oriented software architecture to enable cross-platform multi-channel access to Internet-based learning Víctor Álvarez García Depósito Legal: AS. 00480-2011 http://hdl.handle.net/10803/77825 ADVERTENCIA. El acceso a los contenidos de esta tesis doctoral y su utilización debe respetar los derechos de la persona autora. Puede ser utilizada para consulta o estudio personal, así como en actividades o materiales de investigación y docencia en los términos establecidos en el art. 32 del Texto Refundido de la Ley de Propiedad Intelectual (RDL 1/1996). Para otros usos se requiere la autorización previa y expresa de la persona autora. En cualquier caso, en la utilización de sus contenidos se deberá indicar de forma clara el nombre y apellidos de la persona autora y el título de la tesis doctoral. No se autoriza su reproducción u otras formas de explotación efectuadas con fines lucrativos ni su comunicación pública desde un sitio ajeno al servicio TDR. Tampoco se autoriza la presentación de su contenido en una ventana o marco ajeno a TDR (framing). Esta reserva de derechos afecta tanto al contenido de la tesis como a sus resúmenes e índices. WARNING. Access to the contents of this doctoral thesis and its use must respect the rights of the author. -
Php Developer Best Practices
PHP DEVELOPER BEST PRACTICES Mike Naberezny Matthew Weier O’Phinney Mike Naberezny • http://mikenaberezny.com • http://maintainable.com • http://ohloh.net/accounts/mnaberez ZendCon ‘06 ZendCon ‘07 Sep 15, 2008 | PHP Developer Best Practices Matthew Weier O’Phinney • http://weierophinney.net/matthew • http://framework.zend.com • http://ohloh.net/accounts/weierophinney ZendCon ‘06 ZendCon ‘07 Sep 15, 2008 | PHP Developer Best Practices About You • Web developer, using PHP • Is your code well organized and maintainable? • Are you using source control? • Is your software documented? • Do you have automated tests for your software? Sep 15, 2008 | PHP Developer Best Practices Agenda • Today we will present ideas and techniques that you can use to improve your development process. • Not every technique can apply to every project. • Start small; implement a few new practices at a time. • Find what works for your team and iterate on that. • Use this talk as a starting point to go off and learn more. Sep 15, 2008 | PHP Developer Best Practices Agenda • Source Control • Coding Standards • Testing • Documentation • Deployment • Q & A Sep 15, 2008 | PHP Developer Best Practices Source Control Sep 15, 2008 | PHP Developer Best Practices Source Control • Problems Source Control Solve • How do I know if somebody did something? • How do others know I did something? • How do I get my updates from others? • How do I push my updates out to others? • Do we have the old version? • What changed? Sep 15, 2008 | PHP Developer Best Practices Source Control • General