New Release: Pronto 0.5

Today is a red letter day.  Pronto has finally matured enough that it can be crowned with a real version number.  We've also released an additional example application, which is a simple blog.  Every framework seems to focus on blogs as examples, so we didn't want to be left out.

Notable Changes:

  • Altered URL routing to allow named subpatterns, which are then merged into a final (internal) request variable array along with GET/POST.
  • Added SQLite 2/3 drivers (untested)
  • Put MySQL into ANSI mode so we can escape reserved words using double-quotes instead of backticks. Backticks will still work as well.
  • Modified internal use of registry to prefix internal objects with pronto: for namespace control.
  • Added argument to Validator::validate() and Validator::required() that overrides the default request argument set.
  • Fixed google_translate.php and added translate_all.php to translate English to other languages supported by Google Translate.
  • Added a change-language box to the default Pronto layout
  • Added a PDO database driver
  • Started using multibyte string functions where appropriate
  • Added ppImage::auto_rotate()
  • Changed session behaviour to initialize/use only if its required.  This makes Pronto easier to use behind an http reverse proxy such as Varnish
  • Altered path settings to Pronto and application code can live anywhere, even outside the web root.  To move them, alter DIR_FS_PRONTO and DIR_FS_APP in config.php, then alter the require() line in index.php
  • Added tpAJAX::autocomplete()
  • Modules can now use their own config/navigation.php
  • Chnaged tpAJAX::popup_div() to tpAJAX::popup_bind(), now takes real jQuery selectors as targets
  • Upgraded TinyMCE to 3.2.0.2, swapped out ajaxfilemanager for tinybrowser
  • Revamped navigation menus to support multi-depth sub menus
  • Changed tpAJAX::dialog() to be simpler and more versatile
  • Merged functionality of dialogs and popups so they both use tpAJAX::buttons()
  • Many deprecated methods removed:
    • Removed PHPMailer (deprecated by SwiftMailer) and FCKEditor (deprecated by TinyMCE)
    • Removed old backwards-compatible DB methods
    • Removed Page::validate() and Page::required() shortcut methods
    • Plugins must be referenced through $this->plugins
    • Removed Web::url() and Web::full_url() shortcut methods
    • tpTable::build_grid() no longer uses cb_fn or valuefn parameters


Links:

 

7 Responses

  1. Achille Says:
    July 24, 2009 at 3:03 am -0700

    No update? Project is dead?
  2. Judd Vinet Says:
    July 24, 2009 at 5:08 am -0700

    Nope, the project is very much alive!

    I will be making a new a release soon. There have been a number of notable changes. If you can't wait, though, you can get a GIT checkout:

    $ git clone git://zeroflux.org/pronto.git ./pronto
  3. Achille Says:
    July 24, 2009 at 10:19 am -0700

    Thank you!
    I go to test it!
  4. Achille Says:
    July 24, 2009 at 10:39 am -0700

    Please, can you tell me more about "a number of notable changes" so i can test it?
  5. Judd Vinet Says:
    July 24, 2009 at 12:18 pm -0700

    The biggest change is probably in the model layer. The old model class still does exist (pronto/core/model.php) but is deprecated in favour of the RecordModel and RecordSelector classes.

    See http://www.zeroflux.org/blog/post/251 for more details.

    There is also a "fly model" that you can use through the factory. This is useful when you have a small table that may not have a dedicated model class, but you'd still like to query it through the fluent RecordSelector API.

    Example:

    $m =& Factory::fly_model('table_name');
    $records = $m->find("name='%s'", $name)->limit(10)->load();
    // do stuff
  6. Keith Says:
    January 11, 2010 at 6:25 am -0800

    I stumbled across the Pronto Project over the weekend while looking for ANYTHING better for the PHP-oriented projects I tackle. Unfortunately, the date-time-stamp on these News comments doesn't seem to be working correctly (the date just shows today's date each different time I've looked).

    So, I can't tell if Pronto is alive and well in 2010, or if a new release is actually eminent, etc.

    It looks so very interesting, but can you give me an idea what's up?

    Thanks much -- looking forward to hearing form you!
  7. Judd Says:
    January 11, 2010 at 3:16 pm -0800

    Hi Keith,

    Sorry about the date/time bug -- fixed now.

    Yes, Pronto is still alive and well. I've been extremely busy lately and have been continually leaving Pronto releases on the backburner, but development itself still continues.

    The main reason I haven't made a release is because the documentation is not up to date. But I'll endeavour to make a new release soon, docs or no. Stay tuned.

Add Your Comment