PEAR2 & Pyrus - The look ahead

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Sandbox available to all

    The default exception is good enough Exception implement an interface, each package has their own base exception namespace PEAR2PackageName; interface Exception {}

    Uses OpenSSL2 PKCS#12 and X.509 certificates for package signing and verification

    Smaller / Faster: Uses internal PHP 5.3+ feature to drop code size Robus: Uses XML and Sqlite3 for redundant register, can recover corrupt registries and so on

    • Build process is easier then PEAR1, no more editing XML files • Code layout has to follow the PEAR2 rules • Project info goes in Readme file • Developer list goes in Credits file • Release notes go in Release-0.1.0 file • Run makepackage.php • Get a package

    4 Favorites

    PEAR2 & Pyrus - The look ahead - Presentation Transcript

    1. PEAR2 & Pyrus, The Look Ahead
    2. Head of R&D at echolibre , pear extraordinaire, author and from Iceland Head of R&D at echolibre , pear extraordinaire, published author and an Icelander Who is Helgi ? Head of R&D at echolibre , pear extraordinaire, author and from Iceland
    3. What is PEAR today
      • Structured library
      • Distribution system
      • Standards
      • Community
    4. PEAR - New things
      • PEAR Group elected by developers
      • Mirrors
      • More QA (Test coverage, Doc coverage)
      • Documentation
    5. PEAR - Problems
      • Documentation
      • High bus factor
      • Attracting new people
      • Image issues
    6. PEAR2 Dissected
    7. What is PEAR2
      • Concept overhaul of PEAR
      • PHP 5.3+
      • New Installer
    8. New proposal process
      • New packages go into the Sandbox
      • Channel for stable packages only
      • Sandbox to main channel at beta
    9. From sandbox to production
      • Complete-sih documentation
      • 50%+ code coverage in unit tests
      • API approved by other developers
      • Final package name
    10.  
    11. Documentation with PhD
      • Uses the new awesome PhD
      • Still Docbook
      • Easy to setup
      • Integration of full books possible (TDG)
    12. Documentation with PhD The PEAR manual is built in 5 minutes, not hours !
    13. Exceptions
      • No base exception to extend from
      • SPL exceptions encouraged
    14. Include / Require Once
      • Not allowed !
      • Users given the choice
    15. Include / Require Once
      • PEAR2 Autoload
      • allfiles.php – Includes everything
      • Include files that are highly tweaked
    16. Unzip and go
      • Classical unzip just works
      • Extracted packages can be upgraded
    17. Namespaces
        Will be used in PEAR2
    18. Namespaces Namespace PEAR2; class MyClass {} Namespace PEAR2HTTP; class Request {} Class: PEAR2HTTPRequest Package Name: PEAR2_HTTP_Request
    19.  
    20. PEAR Pyrus Pyrus_Developer
    21. The new installer
      • Easier to use
      • No installation of the installer just grab phar
      • Capable of packaging entire apps in phars
      • Can manage multiple installed PEAR trees
    22. The new installer
      • Custom tree can use deps from the system
      • Easy packaging when using PEAR2 svn layout
      • More security
    23. The new installer
      • Smaller
      • Faster
      • More robust
      • Better handling of PECL
      • Easy to embed in your app
    24. Status
      • Waiting for PHP 5.3.1
      • Finishing touches on pear2.php.net
      • Almost ready for alpha!
      • 80% Test Coverage
    25. How to use
      • php pyrus.phar command
      • php pyrus.phar [directory] command
    26. Pyrus_Developer
      • generate-pear2
      • make
      • package
      • generate-ext
      • pickle
      • build
    27. Handling package xml files
      • Use the standard directory structure
      • Package info goes into README
      • Developer info goes into CREDITS
      • Release notes go into RELEASE-0.1.0
      • Run a 20 line package.php
      • Voila ! Package is created
    28. Simple Channel Server
      • PEAR Channel info REST server
      • No dependencies except for pyrus
      • Builds static XML and package files
      • No web frontend
    29. Questions? Email: [email_address] Twitter: @h http://joind.in/talk/view/955

    + Helgi Þormar ÞorbjörnssonHelgi Þormar Þorbjörnsson, 4 weeks ago

    custom

    478 views, 4 favs, 0 embeds more stats

    Ever wondered what PEAR2 and Pyrus are all about ? more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 478
      • 478 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 4
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories