»
S
I
D
E
B
A
R
«
Sponsored Links
lexa-tools framework for PHP 5.3
Jun 4th, 2011 by Alex

lexa-tools library is not as much a framework as a set of utililies (tools). You are free to organize the site as you’d like. No special folder structure is required. No need to declare any classes. No config files and no magic conventions. The library just arms you with a handy procedural API.

Most ideas were borrowed from Ruby on Rails when I was porting an application from Rails to PHP. If you have had experience with Rails then you would notice a lot of familiar concepts and names.

Visit the lexa-tools homepage

Related Blogs

    Agile Toolkit — PHP Web UI Framework
    Mar 26th, 2011 by romans

    Not often you come over the framework which provides out-of-the-box User Interface, has powerful Model-View-Controller concept and is Easy to Use at the same time. Agile Toolkit does this in style. But what is also important, it’s solid and extensible. The interactive introduction will spoil you with some UI code/samples and touch base of the main features unique to Agile Toolkit. Prepare to be addicted.

    http://agiletoolkit.org/intro

    Features:

    • Simple !
    • Full jQuery UI integration
    • Model View Controller
    • PHP5.2+
    • Fully object-oriented
    • Fast and Secure
    • Open Source & Commercial Licenses

    Sample syntax to add 2 CRUD (Create Read Update Delete) views on your page based on models:

    $page->add(’CRUD’)->setModel(’User’,array(’name’,’surname’));

    $page->add(’CRUD’)->setModel(’Purchases’)->addCondition(’confirmed’,true);

    More goodies on intro page

    Related Blogs

      what is php framework?
      Feb 26th, 2011 by wood

      The idea behind a framework is to offer a design you can use across multiple applications. All applications have a number of basic things in common. A framework is designed to provide a structure for those common elements (database interaction, presentation layer, application logic) so you spend less time writing up database interface code or presentation-layer interfaces and more time writing the application itself. The architecture represented by breaking an application up in this fashion is referred to as Model-View-Controller (MVC). Model refers to your data, View to your presentation layer, and Controller refers to the application or business logic.

      From IBM.com

      What do you think?let me know.

      Related Blogs

        Tuxxedo Engine — Introduction
        Sep 17th, 2010 by Kalle Sommer Nielsen

        Greetings

        I’m Kalle and I would like to introduce a brand new PHP5 based framework, named Tuxxedo Engine. Tuxxedo is a small open source org., managed by a few people set to create scalable/performance, API rich and modern applications, for this purpose we started working on Tuxxedo Engine in late 2006 and have afterwards been rewriting it almost 10 times to get the performance and re-usable API we were looking for. We are near a gold release on Engine (we are currently in the RC3 stage).

        Tuxxedo Engine is unlike many other frameworks more of a library, with different backends (bootstrapers: standard & MVC) to allow a generic interaction with the framework. It comes with all the most basic things a developer need to write a medium to large sized complex website application or service. Tuxxedo Engine is written using PHP 5.3 with integral support for namespaces (the code itself is even using them) and uses many built-in language features of PHP rather than hacking or wrapping around them if possible.

        The standard library includes the following major components:

        • Database Access Layer
          Allows access to multiple databases at the same time, different database driver backends and even integral PDO support.
        • Datamanagers
          ORM alike interface to general manipulation of data. The datamanagers provides a unified way to manipulate, add or remove data for none-linked tables, which does not render this an ORM, it follows a pattern thats closely matching leading ORM classes or based frameworks.
        • Exceptions
          Exceptions are used almost everywhere around the Engine to signal a fault, there is a couple of different types that allows to store different type of data for the error handler
        • Internationalization
          Globalization/Internalization allows the developer to write applications in multiple languages and have a simple yet strong API for dealing languages and phrases.
        • MVC
          Model-View-Controller is an integral part of Engine, written as a standalone component to allow the best possible flexibility. The MVC also includes a Router component among other features.
        • Styles & Templates
          This is perhaps one of the strongest API’s written. Support for multiple styles and per user specific selections, template compiler, template conditions and different storage handlers. Most notable here is the Compiler that compiles Template markup code into PHP executable.
        • Datastore caching
          Engine comes with a simple yet flexible API. The datastore caching is currently per database based and works by caching generally used blocks of data to draw it all out of the database at the web request starting point.
        • Filter
          Although Engine doesn’t come with a complete validation API, the filter extension is designed  to work in-place for filtering standard input data (POST, GET, COOKIE and user applied data). The internal API will take advantage of the PHP filter extension if available for performance.
        • Error handling
          This feature was one of the initial features during the early stages of the development and is perhaps one if not the one most useful feature for developers. Engine uses a strong error handling mechanism that allows storing of non fatal errors in a buffer and direct integration for developers in Debugging mode (more of this below) and have a unified interface for handling exceptions and fatal errors in a userland mode that will detect if the application currently have reach so far in the application that it can produce user themed errors or fallback to the fatal error screen (BSOD).
        • Debugging
          Debugging is always tricky, even for experinced developers. Engine comes with a builtin debugging mode that can be triggered by the configuration file and will allow more verbose errors, for example database errors will have a complete description of what happened. BSOD errors will have a backtrace and executed queries along with other relevant debugging information to show where and what caused the error to be triggered. SQL queries that fail will also some show vendor specific information that can be used to tackle the error with.
        • Autoloading
          All of the Engine uses a unified way to autoload object oriented code, or namespaced organized code. The autoloader will figure out default paths based on the /library folder, and allows frameworks with similar structure to simply be “dropped-in” and they will become autoloadable. The autoloader also allows custom paths for allowing loading of external frameworks that uses a different structure into Engine, or even per application logic structure.
        • Registry
          The registry is the master object in all of Engine, and dominates access to all components thats loaded into the current runtime, or allows loading new ones in a unified way. The registry also allows storing other data across components without hijacking the global scope or coupling components more together than it would make logically sense.
        • Session
          Sessions in Engines referens to two terms, being able to use the PHP session extension and being able to have user sessions in the application. The user session part is covered below. Sessions in Engine are written as simple as possible and protects against session hijacking and CSRF internally without any user interaction. The session class works as a wrapper for prefixing session variables so that multiple applications can run on the same domain or server without interfering with each other.
        • User API
          The standard web application feature set is not complete without a well-thought API for dealing with users of applications, the API is written with users, roles and permissions in mind. Internally the API makes use of datamanagers to allow application users to authenticate for user online statistics.

        Developer Tools

        Unlike many other frameworks, Engine comes with a setup for developmental related tools, that can be used to speed up new application developments. The Developer Tools is written as an application on top of Engine to how any application can interact with it. Although not all API’s are exposed in this GUI interface, its subjected to be continuously developed during the release phrases.

        API generators

        Engine comes with a lexical scanner for generating API analytics for exporting the framework API into a reflection manner. These are generic and works for both applications written on top of Engine and even for other projects. This component is subject to constant development for allowing applications in the end to generate developer documentation for applications in various formats.

        Links

        Download

        Tuxxedo Engine is expected to go gold once proper documentation have been written using some of the API generators. However the latest release, which is as of writing, 1.0.0 Release Candidate 3 is marked as stable both API wise. Its not expected to be followed by anymore release candidates unless serious flaws is found beforehand. which boosts performance and adds some of the more advanced session protection written about above. The list of available downloads is kept at Google Code:

        Please use this blog entry to post comments about what you think of the framework, its features and other questions you may want to ask, don’t hold yourself back, we don’t bite :)

        Ps. the Tuxxedo.net domain is currently under DNS change so the site may appear unavailable for some.

        Related Blogs

          Zeanwork Framework PHP – from Brazil
          Sep 9th, 2010 by Josemar Davi Luedke

          Hello!

          We have a new brazilian PHP framework, it is the Zeanwork, that was developed by me.

          I invite you to know about this project!

          Official Website: http://zeanwork.com.br
          Documentation: http://zeanwork.com.br/doc
          Download: http://zeanwork.com.br/downloads
          Forum: http://zeanwork.com.br/forum
          Tutorials: http://zeanwork.com.br/tutorials
          Screencasts: http://zeanwork.com.br/screencasts

          Currently, all the project documentation is only avaliable in Portuguese, but its something worth checking out.

          Related Blogs



            »  Substance: PHP Frameworks   »  SiteMap