DOCSLIB.ORG

Toward Unified Web Application Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Toward Unified Web Application Development This is an electronic reprint of the original article. This reprint may differ from the original in pagination and typographic detail. Author(s): Laine, M., Shestakov, D., Litvinova, E., and Vuorimaa, P. Title: Toward Unified Web Application Development Year: 2011 Version: Final published version Please cite the original version: Laine, M., Shestakov, D., Litvinova, E., and Vuorimaa, P. (2011). Toward Unified Web Application Development. IT Professional, 13(5), 30-36. DOI: 10.1109/MITP.2011.55 Rights: © 2011 IEEE. Reprited, with permission, from Laine, M., Shestakov, D., Litvinova, E., and Vuorimaa, P. (2011). Toward Unified Web Application Development. IT Professional, 13(5), 30-36. DOI: 10.1109/MITP.2011.55 In reference to IEEE copyrighted material which is used with permission in this dissertation, the IEEE does not endorse any of [university/educational entity's name goes here]'s products or services. Internal or personal use of this material is permitted. If interested in reprinting/republishing IEEE copyrighted material for advertising or promotional purposes or for creating new collective works for resale or redistribution, please go to http://www.ieee.org/publications_standards/publications/rights/rights_link.html to learn how to obtain a License from RightsLink. This publication is included in the electronic version of the article dissertation: Laine, Markku. Unified Web Application Development - A Declarative Approach to Empower End-User Developers. Aalto University publication series DOCTORAL DISSERTATIONS, 6/2018. All material supplied via Aaltodoc is protected by copyright and other intellectual property rights, and duplication or sale of all or part of any of the repository collections is not permitted, except that material may be duplicated by you for your research use or educational purposes in electronic or print form. You must obtain permission for any other use. Electronic or print copies may not be offered, whether for sale or otherwise to anyone who is not an authorised user. Powered by TCPDF (www.tcpdf.org) THE FUTURE OF WEB APPS Toward Unifi ed Web Application Development Markku Laine, Denis Shestakov, Evgenia Litvinova, and Petri Vuorimaa, Aalto University School of Science Web application development in the context of the conventional three-tier architecture is complex, typically requiring a team of experts. Recent Web application architectures and frameworks simplify the development process, potentially turning tier-specific experts into one-person developer teams. raditional Web application develop- Classification of Programming ment requires a good understanding Languages of heterogeneous systems, program- Numerous programming languages have been T ming languages, concepts, and frame- developed over the years. One way of better un- works. For example, in a Web application based derstanding their similarities and differences is on the conventional three-tier architecture,1 the to classify them into a hierarchy of paradigms presentation (user interface), logic (server), and based on their computation model. Typically, data (data management) tiers are all authored top-level classification comprises two paradigms— using conceptually different programming imperative (such as C, Java, and JavaScript) and languages.2 declarative (such as CSS, HTML, and SQL)— Novel Web application architectures have which we can further divide into subparadigms, emerged that aim to reduce this complexity as shown in Figure 1.3 by expanding the concepts used on a single The main difference between the two top-level tier to cover all three tiers. In addition to re- paradigms is that declarative languages specify ducing the amount of required knowledge and what a program should do (the desired results), simplifying the development process, these ar- rather than how to do it (the algorithms needed chitectural approaches also allow tier-specific to achieve the results). This higher abstrac- experts to author an entire Web application on tion level makes declarative languages easier their own. to reason about and raises their semantic level. 30 IT Pro September/October 2011 Published by the IEEE Computer Society 1520-9202/11/$26.00 © 2011 IEEE Programming language paradigms Imperative languages, on the other hand, have more expressive power Imperative Declarative but are generally harder to use and understand.4 This classification of Object- Parallel top-level paradigms isn’t absolute Procedural Logic Functional Database though—some programming lan- based processing guages are more declarative than • C • Java • Java • Prolog • Lisp • SQL others, and some even support multi- ple paradigms. Figure 1. A hierarchy of programming language paradigms (based 3 Another notable difference be- on Doris Appleby and Julius VandeKopple’s work ). The top-level tween imperative and declarative lan- classification comprises two paradigms—imperative and declarative. guages is their scope of use. Typically, imperative languages (such as C and Java) are more general-purpose and applicable for data tiers) makes the development process more solving a variety of problems, whereas declara- complex.5 tive languages are more applicable for solving One way of simplifying the development domain-specific problems, such as defining the process is to expand what is normally used on structure (HTML) or styling (CSS) of a webpage, a single tier to cover all three tiers. An author or managing data (SQL) stored in a relational could also select a single programming language database. This, of course, makes a certain de- and paradigm (imperative or declarative) from a clarative lang uage a good fit for solving the prob- specific tier to use throughout the entire Web lems for which it was specifically designed and a application. poor fit for others because it lacks expressiveness in that domain. Expanding the Presentation Tier: XFormsDB The Evolution of Web A Web designer working on the presentation tier Application Architectures is, as a rule, familiar with declarative XHTML As Figure 2a shows, authors (that is, Web de- and CSS but not skillful in the server-side aspects signers, Web developers, and database experts) of a Web application. Such an expert can ben- implement a typical Web application’s presenta- efit from an architectural approach expanding tion tier using declarative XHTML, combined a presentation-centric language with common with imperative JavaScript to provide additional server-side and database-related functionality. interactivity. They implement the application XFormsDB (developed by Markku Laine, http:// logic residing on the server side using an object- code.google.com/p/xformsdb) is an example of oriented imperative language, such as Java, Ruby, presentation-centric architectural expansion.6 or PHP. They carry out communication between The idea behind the declarative XFormsDB these two tiers using declarative formats (for ex- markup language7 is to naturally extend XForms ample, XML or JSON—JavaScript Object No- (see the sidebar) with the most common server- tation) and the Ajax technique. Finally, on the side and database-related functionality (see undermost tier of the application—that is, the Figure 2b) so authors no longer have to resort data tier—they use either an object-relational to imperative client-side scripting or server-side mapping (ORM) library or declarative SQL programming languages. To manage the data statements to manage data stored in a relational stored in data sources, XFormsDB uses de- database. clarative XPath, but it also lets authors use the The problem with this conventional archi- declara tive XQuery to execute more complex que- tecture is that it requires different tier-specific ries (see the sidebar). The XFormsDB framework experts because of the various programming is bundled with the Apache Tomcat Web server, languages, programming paradigms, and data the eXist-db native XML database,8 and the models on each tier. In addition, the partition- Orbeon Forms Ajax-based server-side XForms pro- ing of a Web application between the client cessor, which can transform requested webpages (presentation tier) and the server (logic and into cross-browser JavaScript and HTML files. computer.org/ITPro 31 THE FUTURE OF WEB APPS XHTML+ Presentation XML XForms XForms Logic XML XForms Presentation Data XML (XPath) (b) XML+ XHTML+ Presentation JavaScript JSON XHTML+ Presentation Object- Java oriented Object- Object- Java/Ruby/PHP Logic Logic Java Logic oriented oriented Java Object- Data (ORM) oriented SQL/ORM Data Relational (c) (a) Data XHTML+ Presentation XML XQuery XQuery Logic XML XQuery Data XML (d) Figure 2. Presentation, logic, and data-centric approaches for expanding (a) the conventional three-tier Web application architecture. Different Web application frameworks exist for each tier: (b) XFormsDB expands the presentation tier, (c) the Google Web Toolkit is for the logic tier, and (d) Sausalito expands the data tier. For each architecture, technologies appear on the left and data models are on the right. Expanding the Logic Tier: imperative Java—beyond its intended scope so The Google Web Toolkit that it can be used not only to author the server- A Web developer working on the logic tier pos- side application logic but also a Web application sesses excellent technical knowledge but doesn’t user interface (see Figure 2c). (Authors could necessarily have the need or motivation to imple- also use XHTML to create the user interface). ment a fancy user interface for a Web application. When a GWT-based Web application
Load more

Recommended publications
  • A Framework for PHP Program Analysis
    A Framework for PHP Program Analysis Mark Hills Postdoc in Software Analysis and Transformation (SWAT) CWI Scientific Meeting February 8, 2013 http://www.rascal-mpl.org Overview • Motivation • Goals • Current Progress • Related Work 2 3 PHP: Not Always Loved and Respected • Created in 1994 as a set of tools to maintain personal home pages • Major language evolution since: now an OO language with a number of useful libraries, focused on building web pages • Growing pains: some “ease of use” features recognized as bad and deprecated, others questionable but still around • Attracts articles with names like “PHP: a fractal of bad design” and “PHP Sucks, But It Doesn’t Matter” 4 So Why Focus on PHP? • Popular with programmers: #6 on TIOBE Programming Community Index, behind C, Java, Objective-C, C++, and C#, and 6th most popular language on GitHub • Used by 78.8% of all websites whose server-side language can be determined, used in sites such as Facebook, Hyves, Wikipedia • Big projects (MediaWiki 1.19.1 > 846k lines of PHP), wide range of programming skills: big opportunities for program analysis to make a positive impact 5 Rascal: A Meta-Programming One-Stop-Shop • Context: wide variety of programming languages (including dialects) and meta-programming tasks • Typical solution: many different tools, lots of glue code • Instead, we want this all in one language, i.e., the “one-stop-shop” • Rascal: domain specific language for program analysis, program transformation, DSL creation PHP Program Analysis Goals • Build a Rascal framework for creating
    [Show full text]
  • Muhammad Touqeer Shafi
    Muhammad Touqeer Shafi E-mail: [email protected] CONTACT Website: http://pk.linkedin.com/pub/touqeer- shafi/22/634/b44/ Phone: +923142032499 WORK EXPERIENCE Ovrlod Pvt Ltd January 2014 — Present Software Engineer Design, program, and deliver web/local development projects (PHP, .Javascript and related platforms) within designated schedules. • Support development of projects from inception through alpha/beta testing and final delivery • Identify, communicate, and overcome development problems and creative challenges related to complex web • Keep current with programming languages/platforms within the web development/web application, and • Comprehend and follow specific project life-cycle instructions and procedures when required • Revise and troubleshoot development work as required • Provide tactical application mentorship to other developers in area of expertise • Heavily contribute to and actively follow technical documentation related to interactive development cycles • Act as a go-to person within technical area of expertise • Effectively present technical information in one-on-one and small group situations to vendors, clients, and agency staff • Apply common-sense understanding to carry out detailed but objective written or oral instructions • Engage in a pattern of learning and research Mamdani Web October 2011 — December 2013 Php Developer Write “clean”, well designed code. Produce detailed specifications. Troubleshoot, test and maintain the core product software and databases to ensure strong optimization and functionality.
    [Show full text]
  • A Guide to Native Plants for the Santa Fe Landscape
    A Guide to Native Plants for the Santa Fe Landscape Penstemon palmeri Photo by Tracy Neal Santa Fe Native Plant Project Santa Fe Master Gardener Association Santa Fe, New Mexico March 15, 2018 www.sfmga.org Contents Introduction………………………………………………………………………………………………………………………………………………………………………………………………………….. ii Chapter 1 – Annuals and Biennials ........................................................................................................................................................................ 1 Chapter 2 – Cacti and Succulents ........................................................................................................................................................................... 3 Chapter 3 – Grasses ............................................................................................................................................................................................... 6 Chapter 4 – Ground Covers .................................................................................................................................................................................... 9 Chapter 5 – Perennials......................................................................................................................................................................................... 11 Chapter 6 – Shrubs .............................................................................................................................................................................................
    [Show full text]
  • Redalyc.Effect of Deficit Irrigation on the Postharvest of Pear Variety
    Agronomía Colombiana ISSN: 0120-9965 [email protected] Universidad Nacional de Colombia Colombia Bayona-Penagos, Lady Viviana; Vélez-Sánchez, Javier Enrique; Rodriguez-Hernandez, Pedro Effect of deficit irrigation on the postharvest of pear variety Triunfo de Viena (Pyrus communis L.) in Sesquile (Cundinamarca, Colombia) Agronomía Colombiana, vol. 35, núm. 2, 2017, pp. 238-246 Universidad Nacional de Colombia Bogotá, Colombia Available in: http://www.redalyc.org/articulo.oa?id=180353882014 How to cite Complete issue Scientific Information System More information about this article Network of Scientific Journals from Latin America, the Caribbean, Spain and Portugal Journal's homepage in redalyc.org Non-profit academic project, developed under the open access initiative Effect of deficit irrigation on the postharvest of pear variety Triunfo de Viena (Pyrus communis L.) in Sesquile (Cundinamarca, Colombia) Efecto del riego deficitario en la poscosecha de pera variedad Triunfo de Viena (Pyrus communis L.) en Sesquilé (Cundinamarca,Colombia) Lady Viviana Bayona-Penagos1, Javier Enrique Vélez-Sánchez1, and Pedro Rodriguez-Hernandez2 ABSTRACT RESUMEN A technique settled to optimize the use of water resources is Una técnica para optimizar el uso del recurso hídrico es el Riego known as Controlled Deficient Irrigation (CDI), for which this Deficitario Controlado (RDC), por esto se realizó un experi- experiment was carried out to determine the effect of a three mento para ver el efecto de tres láminas de agua correspondien- water laminae: 100 (T1), 25 (T2) and 0% (T3) crop´s evapotrans- tes al 100 (T1), 25(T2) y 0% (T3) de la evapotranspiración del piration (ETc) on the rapid growth phase of the pear fruit variety cultivo (ETc), en la fase de crecimiento rápido del fruto de pera Triunfo de Viena.The fruit quality (fresh weight variation, variedad Triunfo de Viena.
    [Show full text]
  • Laravel in Action BSU 2015-09-15 Nathan Norton [email protected] About Me
    Laravel in Action BSU 2015-09-15 Nathan Norton [email protected] About Me ● Full Stack Web Developer, 5+ years ○ “If your company calls you a full stack developer, they don’t know how deep the stack is, and neither do you” - Coder’s Proverb ● Expertise/Buzz words: ○ PHP, Composer, ORM, Doctrine, Symfony, Silex, Laravel, OOP, Design Patterns, SOLID, MVC, TDD, PHPUnit, BDD, DDD, Build Automation, Jenkins, Git, Mercurial, Apache HTTPD, nginx, MySQL, NoSQL, MongoDB, CouchDB, memcached, Redis, RabbitMQ, beanstalkd, HTML5, CSS3, Bootstrap, Responsive design, IE Death, Javascript, NodeJS, Coffeescript, ES6, jQuery, AngularJS, Backbone.js, React, Asterisk, Lua, Perl, Python, Java, C/C++ ● Enjoys: ○ Beer About Pixel & Line ● Creative Agency ● Web development, mobile, development, and design ● Clients/projects include Snocru, Yale, Rutgers, UCSF, Wizard Den ● Every employee can write code ● PHP/Laravel, node, AngularJS, iOS/Android ● “It sucks ten times less to work at Pixel & Line than anywhere else I’ve worked” - Zack, iOS developer Laravel ● Born in 2011 by Taylor Otwell ● MVC framework in PHP ● 83,000+ sites ● Convention over configuration ● Attempts to make working with PHP a joy ● Inspired by Ruby on Rails, ASP.NET, Symfony, and Sinatra ● Latest version 5.1, finally LTS Laravel Features ● Eloquent ORM ● Artisan command runner ● Blade Templating engine ● Flexible routing ● Easy environment-based configuration ● Sensible migrations ● Testable ● Caching system ● IoC container for easy dependency injection ● Uses Symfony components ● Web documentation
    [Show full text]
  • Frameworks PHP
    Livre blanc ___________________________ Frameworks PHP Nicolas Richeton – Consultant Version 1.0 Pour plus d’information : www.smile.fr Tél : 01 41 40 11 00 Mailto : [email protected] Page 2 les frameworks PHP PREAMBULE Smile Fondée en 1991, Smile est une société d’ingénieurs experts dans la mise en œuvre de solutions Internet et intranet. Smile compte 150 collaborateurs. Le métier de Smile couvre trois grands domaines : ! La conception et la réalisation de sites Internet haut de gamme. Smile a construit quelques uns des plus grands sites du paysage web français, avec des références telles que Cadremploi ou Explorimmo. ! Les applicatifs Intranet, qui utilisent les technologies du web pour répondre à des besoins métier. Ces applications s’appuient sur des bases de données de grande dimension, et incluent plusieurs centaines de pages de transactions. Elles requièrent une approche très industrielle du développement. ! La mise en œuvre et l’intégration de solutions prêtes à l’emploi, dans les domaines de la gestion de contenus, des portails, du commerce électronique, du CRM et du décisionnel. www.smile.fr © Copyright Smile - Motoristes Internet – 2007 – Toute reproduction interdite sans autorisation Page 3 les frameworks PHP Quelques références de Smile Intranets - Extranets - Société Générale - Caisse d'Épargne - Bureau Veritas - Commissariat à l'Energie Atomique - Visual - Vega Finance - Camif - Lynxial - RATP - AMEC-SPIE - Sonacotra - Faceo - CNRS - AmecSpie - Château de Versailles - Banque PSA Finance - Groupe Moniteur - CIDJ - CIRAD - Bureau
    [Show full text]
  • Pear and Nashi Production in Australia Introduction
    Case Study 26 Pollination Aware and Pear Nashi This case study is the primary source of information on potential pollination services for the industry. It is based on data provided by industry, the ABS and other relevant sources. Therefore, information in this case study on potential hive requirements may differ to the tables in the Pollination Aware report (RIRDC Pub. No. 10/081) which are based on ABS (2008) Agricultural Commodities Small Area Data, Australia 2005-06. Introduction Pear trees (Pyrus spp., family Rosaceae) are native to coastal colours ranging from tan to brown and a rough texture. Both and mildly temperate regions of western Europe, North Africa, types grow easily, produce sweet and juicy fruit that are a low and extending east across parts of Asia. The two main types of calorie source of carbohydrates, fibre, and pectin. pear cultivated around the world are the European pear (Pyrus Most pear varieties are considered self-infertile and require communis L) and the Asian pear or ‘nashi’ (Pyrus pyrifolia). For cross-pollination with another variety to set fruit. Honey bees the purpose of this study the European pear is referred to as the are regarded as the most efficient and most important pollinators ‘pear’ and the Asian pear as the ‘nashi’. The fruit mainly carry of pear trees (McGregor 1976; Stern et al. 2004). This is despite the distinctive ‘pear shape’, technically referred to as pyriform (a the fact that pear flowers produce very little nectar, with bees narrow stem area and full bulbous-like base); however, the nashi primarily foraging on them for pollen (McGregor 1976).
    [Show full text]
  • Organizing Your PHP Projects
    Organizing Your PHP Projects Paul M. Jones Read These • “Mythical Man-Month”, Brooks • “Art of Project Management”, Berkun • “Peopleware”, DeMarco and Lister 2 Project Planning in One Lesson • Examine real-world projects • The One Lesson for organizing your project • Elements of The One Lesson • The One Lesson in practice 3 About Me • Web Architect • PHP since 1999 (PHP 3) • Solar Framework (lead) • Savant Template System (lead) • Zend Framework (found. contrib.) • PEAR Group (2007-2008) 4 About You • Project lead/manager? • Improve team consistency? • Want to share your code with others? • Want to use code from others? • Want to reduce 5 Goals for Organizing • Security • Integration and extension • Adaptable to change • Predictable and maintainable • Teamwork consistency • Re-use rules on multiple projects 6 Project Research; or, “Step 1: Study Underpinnings” 7 Project Evolution Tracks One-Off Heap Standalone App Library ? Modular App Collection Framework CMS 8 One-Off Heap • No discernible architecture • Browse directly to the scripts • Add to it piece by piece • Little to no separation of concerns • All variables are global • Unmanageable, difficult to extend 9 Standalone Application • One-off heap ++ • Series of separate page scripts and common includes • Installed in web root • Each responsible for global execution environment • Script variables still global 10 Standalone Application: Typical Main Script // Setup or bootstrapping define('INCLUDE_PATH', dirname(__FILE__) . '/'); include_once INCLUDE_PATH . 'inc/prepend.inc.php'; include_once INCLUDE_PATH . 'lib/foo.class.php'; include_once INCLUDE_PATH . 'lib/View.class.php'; // Actions (if we're lucky) $foo = new Foo(); $data = $foo->getData(); // Display (if we're lucky) $view = new View(INCLUDE_PATH . 'tpl/'); $view->assign($data); echo $view->fetch('template.tpl'); // Teardown include_once INCLUDE_PATH .
    [Show full text]
  • Prado Basin Sediment Management Demonstration Project Biological Conditions Technical Report
    PRADO BASIN SEDIMENT MANAGEMENT DEMONSTRATION PROJECT BIOLOGICAL CONDITIONS TECHNICAL REPORT Prepared By Orange County Water District 18700 Ward Street Fountain Valley, CA 92708 Contact: Richard Zembal Daniel Bott July 2013 Table of Contents Section Page 1.0 INTRODUCTION ......................................................................................1-1 2.0 REGULATORY FRAMEWORK ................................................................ 2-1 3.0 ENVIRONMENTAL SETTING .................................................................. 3-1 3.1 Regional Setting ................................................................................... 3-1 3.2 Local Setting ......................................................................................... 3-3 3.3 Relevant Biological Resource Management Programs ......................... 3-8 4.0 BIOLOGICAL RESOURCES ....................................................................4-1 4.1 Methodology ......................................................................................... 4-1 4.2 Vegetation Communities ....................................................................... 4-3 4.3 Sensitive Communities/Special Status Plants ..................................... 4-11 4.4 Wildlife ................................................................................................4-19 4.5 Wildlife Movement Corridors ............................................................... 4-51 5.0 SUMMARY OF BIOLOGICAL RESOURCES .......................................... 5-1 6.0
    [Show full text]
  • NLE-GRID T3 Multi-Component Application Builder Natural Language Engineering on a Computational Grid POSC/PLP/60663/2004 — INESC-ID Lisboa Tech
    Instituto de Engenharia de Sistemas e Computadores Investigação e Desenvolvimento em Lisboa Laboratório de Sistemas de Língua Falada NLE-GRID T3 Multi-Component Application Builder Natural Language Engineering on a Computational Grid POSC/PLP/60663/2004 — INESC-ID Lisboa Tech. Rep. 33/2008 — Lu´ıs Marujo, Wang Lin, David Martins de Matos L2F – Spoken Language Systems Laboratory INESC ID Lisboa, Rua Alves Redol 9, 1000-029 Lisboa, Portugal {ldsm,wlin,david}@l2f.inesc-id.pt This report details the restructuring of the original Galinha system, in order to build the web portal for allowing access to modules, applications, and library interfaces in the our system. The interface uses the application server as a bridge between the interface’s pre- sentation layer (HTML/JavaScript, at the browser level) and the infrastructure. In this way, users can ignore details about the underlying infrastructure when submitting jobs for execution via a web interface or the portal’s application programming interface. This revision: January 30, 2008 NLE-GRID T3: Multi-Component Application Builder Natural Language Engineering on a Computational Grid POSC/PLP/60663/2004 Lu´ıs Marujo, Wang Lin, David Martins de Matos L2F – Spoken Language Systems Laboratory INESC ID Lisboa, Rua Alves Redol 9, 1000-029 Lisboa, Portugal {ldsm,wlin,david}@l2f.inesc-id.pt Abstract. This report details the restructuring of the original Galinha system, in order to build the web portal for allowing access to modules, applications, and library interfaces in the our sys- tem. The interface uses the application server as a bridge between the interface’s presentation layer (HTML/JavaScript, at the browser level) and the infrastructure.
    [Show full text]
  • Ussurian Or Harbin Pear
    Ussurian or Harbin Pear slide 46a slide 46b 360% 360% slide 46c slide 46d 360% 380% III-91 Ussurian or Environmental Requirements Harbin Pear Soils Soil Texture - Prefers clay loam to sandy loam soils. (Pyrus ussuriensis) Soil pH 5.0 to 7.5. Does not tolerate saline soils. Windbreak Suitability Group - 1, 3, 5. General Description Cold Hardiness The hardiest of all pears, introduced from northeastern USDA Zone 3. Asia. White flowers, semi-glossy foliage and dense, variably-rounded forms are of particular interest. Water The largest tree in North Dakota is 29 feet tall with Medium, requires well-drained soils. a canopy spread of 24 feet. Light Leaves and Buds Full sun. Bud Arrangement - Alternate. Bud Color - Buds with overlapping scales, blackish-brown. Uses Bud Size - 1/8 to 1/4 inch. Conservation/Windbreaks Leaf Type and Shape - Simple, ovate. Small to medium tree for farmstead and field windbreaks Leaf Margins - Setosely-serrate. and riparian plantings. Leaf Surface - Smooth or nearly so, leathery. Leaf Length - 2 to 4 inches. Wildlife Used for food by a wide variety of birds and mammals. Leaf Width - 1½ to 2½ inches. Nesting site for songbirds. Leaf Color - Semi-glossy, dark green; orange to yellow fall color. Agroforestry Products Food - The fruit is hard, but may have use for jams Flowers and Fruits and jellies. Sweeter after a frost. Flower Type - Umbel-like racemes. Medicinal - Pyrus species are a source of phloretin, Flower Color - Faintly pink in bud, finally white. an antibiotic. Fruit Type - Subglobose 1-inch pome, short-stalked. Urban/Recreational Fruit Color - Fruits are greenish-yellow.
    [Show full text]
  • Right” Way Your Guide to PHP Best Practices, Coding Standards, and Authoritative Tutorials
    PHP: The ”Right” Way Your guide to PHP best practices, coding standards, and authoritative tutorials. Phil Sturgeon and Josh Lockhart This book is for sale at http://leanpub.com/phptherightway This version was published on 2015-01-05 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License Tweet This Book! Please help Phil Sturgeon and Josh Lockhart by spreading the word about this book on Twitter! The suggested hashtag for this book is #phptherightway. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#phptherightway This book is built entirely from the hard work put in from the PHP community via GitHub. There are too many to name, but you know who you are. Without all the pull requests and suggests from you guys people would still be durp-clicking around 10 year old tutorials with PHP 4 code examples like it’s 2003. Contents 1. Getting Started .............................................. 1 1.1 Use the Current Stable Version (5.6) ................................ 1 1.2 Built-in web server ......................................... 1 1.3 Mac Setup .............................................. 1 1.4 Windows Setup ........................................... 2 2. Code Style Guide ............................................ 3 3. Language Highlights .......................................... 5 3.1 Programming Paradigms .....................................
    [Show full text]