It has been a while since we have released Beta 3 but we're still working hard on the next release. Here are somethings to look forward to in the upcoming RC1:
Improved CSS theme
Designing great looking web pages and applications has been made easier with the new integrated jQuery UI CSS theme-able classes. Just include the default theme or create your own and you're ready to go.
Improved Sanitizer
The new web page "post" and "get" properties makes it easier to get access to all your HTTP POST and GET values while being able to filter and sanitize values.
<?php
protected function saveData() {
$id = $this->post->intVal('id');
$name = $this->post->textVal('name');
$email = $this->post->emailVal('email');
$age = $this->post->intVal('age');
// code to save data...
}
?>
Improved Template Binder
New Template Binder optional make it possible to add CSS classes while rendering a template. It's also possible to dynamically format display values from a callback function.
Ajax Ready
Tighter integration with client-side JavaScript and the jQuery 1.4.2 and jQuery Tools 1.2.2 API make it possible to build Rich Ajax Applications using PHP.
New UI API
The UI support for Raxan has been overhauled to support new components and widgets. New features include support for inline properties (e.g. xt-ui-background, etc), new event handlers and a new RaxanUIContainer class.
Flash Messages
With the new flash message API, developers will be able to quickly display messages within a web page.
<?php
protected function speak($word){
if ( !$word) {
$this->flashmsg('I have nothing to say.');
}
}
?>
To display flash messages within the page, you only need to insert an HTML element with the class attribute set to flash-message:
<div class="flash-message"></div>
Server-Side HTML5 Validation
Basic HTML5 validation has been added to the framework to make it easier to validate client inputs. With just a few line of code, you can check for valid inputs:
<?php
protected function addItem($e){
$frm = $this->webForm;
if ( !$frm->checkValidity(true,'required') ) {
$this->flashmsg('Invalid input values');
} else {
$v = $frm->validValues();
// some code here....
$this->flashmsg('New item added');
}
}
?>
Since we're doing HTML5 Form validation on the server-side you only need to type the HTML once:
<input type="text" name="itemname" id="itemname" value="" maxlength="50" required />
<textarea name="description" id="description" cols="10" rows="5" maxlength="250" required></textarea>
<input type="submit" name="submit1" id="submit1" value="Submit" />
Supported HTML5 Validation constraints:
• Maxlength
• Required
• Min / Max (only works with type=number )
• Email
• URL
• Number
• Date
• Month
• Pattern
Page-View Design Pattern
Raxan Beta 3 introduced a switchboard page handler that was designed to manage actions requested by the client. In RC1, the Switchboard Page Handler and Action has been replaced with individual view handlers and view mode.
The Page-View pattern makes it easier for developers to load and display multiple content views while maintaining separation between content and logic.
- Page - The Page controller loads and interacts with the view and the model.
- View - Stores the content to be displayed. This can be either a be a static or a dynamic page.
The page controller receives a view mode request from the client to load and display a view. This information is passed to the view handler which then loads the requested view and the associated data/model. If a view was not specified, then the page controller will invoke the default _indexView() handler.
The view mode which forms part of the page controller's url is case sensitive and can only contain characters A-Z, 0-9 and _ (underscore). For example: items, contacts, book_list, orderItems, etc.
To request a view the page controller url must contain the desired view mode as part of the query sting as shown below:
http://domain.com/page-controller.php?vu=items
Where "vu" is the view mode query string parameter.
Once the view mode request is received by the page controller, the activeView property is set and the appropriate view handler will be invoked. The view handler is a special method that's only invoked when a specific view is requested. The method name consist of an underscore (_), the view mode and the suffix "View". For example:
<?php
// items view handler
protected function _itemsView() {
// code here
}
?>
Example:
The Page-View pattern allows developers to organize an application or page into Views and Events. For example, a blog application can be organized as follows:
Blog Page Layout
Views:
- index view (default view - list blog entries)
- detail view (show blog detail)
- form view (create or edit blog)
Events:
- save event
- delete event
Views are normally stored inside a views folder. This folder can be configured by setting the views.path configuration option inside the config file.
Download Developer Snapshot
You can download the latest Developer Snapshot or check out the code from the Google Code
After downloading the source file be sure to check out the quickref.html, CHANGELOG.txt and the notes.php example
Bugs, Patches & Questions
For questions, bugs or patches you can contact me via email, the Community Forum or create an issue using the Issue Tracker.
Posts: 8
Reply #7 on : Fri August 15, 2014, 04:28:12
Posts: 8
Reply #6 on : Fri August 15, 2014, 04:29:11
Posts: 8
Reply #5 on : Mon October 15, 2018, 19:58:18
Posts: 8
Reply #4 on : Sun December 23, 2018, 22:29:44
Posts: 8
Reply #3 on : Wed January 02, 2019, 19:13:03
Posts: 8
Reply #2 on : Fri January 11, 2019, 04:18:25
Posts: 8
Reply #1 on : Sat June 01, 2019, 11:34:18
Posts: 8
Reply #8 on : Fri July 11, 2014, 11:00:29