archive-com.com » COM » S » SOLARPHP.COM

Total: 875

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Solar Framework for PHP 5
    Table B 2 Conventional Translation Key Prefixes Prefix Usage ACTION Displayed text for page controller action names DESCR Form element descriptions long text ERR Logic error and exception messages FAILURE Failure messages typically form related FORMAT Formatting strings for the locale HEADING Heading titles INVALID Invalid data message LABEL Form element labels short text LEGEND Fieldset legend titles SUCCESS Success messages typically form related PROCESS Displayed text for action processes

    Original URL path: http://solarphp.com/manual/appendix-standards.naming.locale-keys (2016-02-13)
    Open archived version from archive


  • Solar Framework for PHP 5
    php BazDib php Classes descended from Solar Base automatically convert specific error codes into exception class names and then attempt to use a related locale string for the exception message For example if you have this in your locale file php return array ERR FOO BAR A foo bar exception occurred ERR BAZ DIB Baz dib was raised you should look into it and you throw an exception using Solar

    Original URL path: http://solarphp.com/manual/appendix-standards.naming.exceptions (2016-02-13)
    Open archived version from archive

  • Solar Framework for PHP 5
    in an Acme Model domain a table named foo bars should map to the class Acme Model FooBars In general table names are expected to be in the plural For example blogs not blog and people or persons not person These are not hard coded restrictions You can always use any table name with any class name although you may need to set special options in the model class to

    Original URL path: http://solarphp.com/manual/appendix-standards.naming.models (2016-02-13)
    Open archived version from archive

  • Solar Framework for PHP 5
    Universal Configuration A 5 1 Config File Settings A 5 2 Instantiation Settings A 5 3 Order of Precedence A 6 Project System A 6 1 The source Directory A 6 2 The include Directory A 6 3 The config Directory A 6 4 The docroot Directory B Naming Conventions B 1 Introduction B 2 Vendor and Class Names B 3 Methods B 4 Global Variables and Functions B 5

    Original URL path: http://solarphp.com/manual/pt02 (2016-02-13)
    Open archived version from archive


  • The Solar project and its designates will have complete control and discretion over capabilities associated with Your credentials and may change them for any reason at any time Your name and email address or a derivative of it may be visible worldwide via the Internet 3 License Terms Code committed to a Solar repository must be governed by the New BSD License or another license or set of licenses acceptable to the Solar project for the Code in question Other licenses are not acceptable to the Solar project until declared so in writing at http solarphp com committers You will verify that committed Code contains appropriate boilerplate licensing text 4 Committing Code Created by Others You may check in Code to a Solar repository that was not written by You provided that a The checkin comment contains information or references to information sufficient to identify the author of the Code including at minimum an email address and b You make all reasonable and appropriate efforts to ensure that such Code conforms to the terms of this agreement 5 Cryptography You understand that cryptographic Code may be subject to government regulations with which the Solar project and or entities using such

    Original URL path: http://solarphp.com/solar-cla-1.0.txt (2016-02-13)
    Open archived version from archive

  • Solar Framework for PHP 5
    Front Controller 2 2 1 Dynamic Rewrite 2 2 2 Static Routing 2 2 3 Class Stack 2 3 Rewrite Rules 2 3 1 Short Form 2 3 2 Replacement Tokens 2 3 3 Long Form 2 4 Page Controller 2 4 1 Setup and Loading 2 4 2 Running the Action 2 4 3 Rendering the Results 2 4 4 Returning the Response Prev Up Next 1 15 Cleaner

    Original URL path: http://solarphp.com/manual/dispatch-cycle (2016-02-13)
    Open archived version from archive

  • Solar Framework for PHP 5
    Method In order the Solar start method does these things to set up the environment Loads the baseline classes needed for operations Solar Base Solar Class Solar Config and Solar File Registers Solar Class autoload as an SPL autoloader As a security measure cleans the superglobal arrays so that variables don t get overwritten by incoming user values Calls Solar Config load to read in configuration values and make them available to classes for self configuration and sets some values and configuration for the Solar arch class Calls ini set using the values from the Solar ini set configuration key Makes Solar Registry entries for all items from the Solar registry set configuration key If they do not exist already adds registry entries for the names inflect locale request and response These refer to instances of Solar Inflect Solar Locale Solar Request and Solar Http Response respectively Finally run any hook scripts functions or methods specified by the Solar start configuration key These let you specify behaviors and logic to be executed at the end of the startup routine What s A Registry Isn t That A Lot Of Objects The registry is a place to store instances of objects so they can be used by the system as a whole without having to pass them around as parameters to methods Registry objects are stored and retrieved using unique names any object in the registry can be retrieved using Solar Registry get Registry objects are lazy loaded That means you can define an object to go into the registry but it won t be instantiated until you attempt to retrieve it Thus the fact that Solar start defines several registry entries incurs very little performance reduction by itself 2 1 2 Configuration The Solar start method takes one parameter a

    Original URL path: http://solarphp.com/manual/dispatch-cycle.bootstrap-config (2016-02-13)
    Open archived version from archive

  • Solar Framework for PHP 5
    what page controller to instantiate At first it uses the routing config value to match the element against a particular page controller class If there are no matches it tries to automatically pick a class using the classes class stack prefixes If after all of this the front controller could not find a page controller class that matched the first element of the URI path info it will return a not found page otherwise it will instantiate the page controller class and pass it the possibly modified remainder of the URI Note that the three layers of modification and discovery dynamic rewrite static routing and class prefixes are complementary each can be used by itself alone or in combination with the others or not at all 2 2 1 Dynamic Rewrite This somewhat complicated topic is covered on the next page Note Once a rewrite rule is matched rewrite processing stops and passes along to static routing Any URI not matching a rewrite rule will be left untouched 2 2 2 Static Routing After any dynamic rewrites the front controller then looks at the first path info element of the URI and tries route it to a page controller class It does this in two steps via static routing and then via a class stack For the static routing the front controller looks at the routing config value to see if the first path info element has a page controller class defined for it php routes all journal URIs to the Acme App Blog class config Solar Controller Front routing array journal Acme App Blog 2 2 3 Class Stack If there were no static routing matches the front controller finally falls back to a stack of class prefixes Solar will append the first path info element of the URI

    Original URL path: http://solarphp.com/manual/dispatch-cycle.front-controller (2016-02-13)
    Open archived version from archive



  •