A Framework That Builds Websites
You can't do it all in Flash. To create rich web applications (RIA), you need to pick a place to stand in a jungle of tools. The classier web developer peers out from a RoR or PHP environment, because the complete power of computing is available from that groundwork. The problem is, there are a dozen other tools necessary to complete user experience. How can one library provide a feature-rich developer environment, without being too open ended or missing key features?
HerbIgniter is here to accomplish that by providing a streamlined model, a supportive graphical interface libraries to handle commonly needed components, and a succinct range of features to provide maximum configurability combined with ease of use.
HerbIgniter is right for you if...
- You want a framework with a ton of features.
- You need exceptional performance.
- You need broad compatibility with standard hosting accounts that run a variety of PHP versions and configurations.
- You want a framework that requires nearly zero configuration.
- You want to design session-based, dynamic database-driven websites rapidly with a minimal learning curve.
- You prefer a framework that provides top-notch configurable high-end graphical website components.
- You want to build the web "on demand"
- You want to use a wide range of feature-rich components.
- You want to use AJAX, but don't want to spend time debugging it.
- You do not want to be forced to write a million files for each control.
- You eschew complexity, favoring simple solutions, but accept that the web has not evolved to be simple.
- You like logical frameworks.
- You already know PHP and are somewhat familiar with CodeIgniter®
Comparison of CodeIgniter (MVC) and HerbIgniter (TOD) Frameworks
| MVC and CodeIgniter® | TOD and HerbIgniter |
- Creates loopholes in an amorphous 'view' file, that has no clear identity and impacts logical progression (workflow)
- Simple or vague object purposes with segmented declarations of functionality across many files/directories
- No native AJAX support
- Forced adherence to MVC unless you hack it.
- Widespread use of object $this, discouraging the use of PHP classes
- Provides a loose object framework which has design shortcomings when implementing advanced functionality
- *Parts included with HerbIgniter
- Simplifies file structure: eliminates the 'view' file, by assuming we are writing a display object from the bottom up. All interactions with webservers begin and end with a "write", so the aspect of reading user input happens always less frequently than writing output to a view. So we don't need to separate the idea of controller, model and view after all: we're most likely visualizing data when we're developing for the web.
- Strong objective identity (complex object declarations) that maps data to output in object's methods, which are essentially the 'view' and 'process' components of any particular objective topic.
- Relies heavily on strict object declarations
