Limonade

Lemondoo

Tue, 10 May 2011 10:00:06 +0200

Lemondoo:

A nice tutorial about doing a Todo web app with Limonade.

PHPBuilder.com: Building Web Apps with the Limonade PHP Framework

Fri, 06 May 2011 21:27:25 +0200

PHPBuilder.com: Building Web Apps with the Limonade PHP Framework

Lemontrac bug tracker

Fri, 01 Apr 2011 08:22:33 +0200

Lemontrac bug tracker:

Angelo Rodrigues share in this post how he wrote a bug tracker with Limonade PHP.

Limonade PHP 0.5 is released!

Sat, 16 Oct 2010 18:22:00 +0200

It’s finally there with many fixes and new features since the 0.4.6. See the CHANGES file to learn more.

For those who use to work with the master branch, nothing really new but it’s a confirmation of the code stability, with an extra effort for documenting and testing the last features.

The TODO has been cleaned up and will show you more clearly what I plan for the next releases. If you want to contribute, you’re welcome ;-)

Thanks to all Limonade addicts !

— Fabrice Luraine

http://github.com/sofadesign/lemons

Fri, 08 Oct 2010 16:41:28 +0200

http://github.com/sofadesign/lemons:

I want to keep Limonade core thin, only with essentials features, but what about those useful stuff we carry from project to project ? Just keep and share those lemons together in http://github.com/sofadesign/lemons ;-)

"We need to be more specific in our READMEs and Web sites where we can and think about what a smart..."

Wed, 11 Aug 2010 11:59:55 +0200

“We need to be more specific in our READMEs and Web sites where we can and think about what a smart newcomer would want to see. We need “Getting Started” or “For Newcomers” pages that tell people exactly what to do without bending over backwards to cover edge cases or show off esoteric features. Tours that don’t take diversions. Download X. Type Y. Run code Z. Instructing, rather than showing a smorgasbord of options, from which a new, confused user would choose none. Rather than offer 5 vaguely different alternatives on a “How To Install” page, give the simplest, most generic route, then discuss the alternatives for “advanced users.””

- Does Ruby Suffer From An Overabundance Of Choice? by Peter Cooper

Building Cloud Communication Apps with Tropo and Limonade (part 3)

Tue, 22 Jun 2010 10:00:00 +0200

Building Cloud Communication Apps with Tropo and Limonade (part 3)

Limonade + LDAP example

Fri, 18 Jun 2010 10:00:00 +0200

Limonade + LDAP example

Building Cloud Communication Apps with Tropo and Limonade (part 2)

Tue, 15 Jun 2010 09:16:32 +0200

Building Cloud Communication Apps with Tropo and Limonade (part 2)

RAC: PHP RabbitMQ Administration Console

Fri, 14 May 2010 10:00:00 +0200

RAC: PHP RabbitMQ Administration Console :

RAC is an administration console for RabbitMQ, by Alvaro Videla and Neil Fang. It is written with Limonade PHP and uses the PHP Erlang Bridge Extension to communicate with RabbitMQ.

"The Limonade website names the aforementioned Camping and Sinatra frameworks as sources of..."

Tue, 27 Apr 2010 10:00:00 +0200

“

The Limonade website names the aforementioned Camping and Sinatra frameworks as sources of inspiration. It’s perhaps the most compact of the solutions described here in terms of the amount of code required to build something useful, with powerful demos such as the Wikir wiki (written in under 200 lines of code). But perhaps the most powerful evidence of Limonade’s minimalistic approach is the example included with the project README, which includes all of the code necessary to power a one-page website:

require_once 'lib/limonade.php';
dispatch('/', 'hello');
    function hello()
    {
        return 'Hello world!';
    }
run();

Minimalistic indeed!

”

- Top 10 Lightweight Frameworks for PHP Development by Jason Gilmore

"ALL code is ugly. Yours, mine, everyone’s. Code Is Ugly. Just face it. When someone says “beautiful..."

Tue, 13 Apr 2010 09:58:09 +0200

“ALL code is ugly. Yours, mine, everyone’s. Code Is Ugly. Just face it. When someone says “beautiful code”, hear “beautiful rotten entrails”. The only beautiful code, the most clean code, is no code at all. If it’s there, it’s ugly. The unfortunate fact of software development is that, in order to create beautiful software, we must use ugly code.”

- gist: 357981 - A better coding convention for lists and object literals in JavaScript (via mwunsch)

Cloud Telephony With Limonade and Cloudvox

Mon, 22 Mar 2010 10:00:00 +0100

[by Mark Headd]

A couple of months ago, I did a quick write up on a new cloud telephony company named Cloudvox. In the interim, I’ve been doing some playing around with their HTTP/JSON API for creating telephone applications, and I’ve been blown away by how simple and powerful a tool it is for building sophisticated cloud telephony applications.

This post will provide a quick overview of how the Cloudvox JSON API can be paired with PHP and the delightfully awesome Limonade Framework. If you’re not a PHP developer don’t despair - this example can easily be ported to other languages like Ruby (using Sinatra) or C# (using Kayak).

Cloudvox API Helper Classes

When writing apps for the Cloudvox JSON API, there are two things that we need to manage - the JSON that we will send to Cloudvox (using plain old HTTP) and the response Cloudvox sends back to our app (this will include any user input collected from the caller, and also things like a unique identifier for the call, caller ID and other information about the call).

To make managing both sides of our exchange with Cloudvox easier, I’ve created a set of PHP classes that can be used with any standard PHP IDE to make writing Cloudvox JSON and parsing Cloudvox responses simple and easy. You can download this class library from GitHub.

Using these classes is pretty straightforward:

Will render:

[{"name":"Speak","phrase":"Hello world!"},{"name":"Hangup"}]

Required properties are included in the constructor for each class - in most IDE’s this means that you can simply use Shift + Control + Space Bar when you create a new instance of the object to see what properties are required.

Optional properties on all classes are handled by using the PHP __set() method in the base class. This effectively let’s you overload the object and set properties which are not declared in the class definition. So for example, if we wanted to collect input from the caller (e.g., their zip code) we would use the GetDigits class, and overload it to add a URL to post the results to:

url = “http://somehost.com/myscript.php”;
?>

The problem with overloading in PHP is that you don’t get the benefit of having your IDE display overload options (it can’t because the properties that we wish to set are not declared in the class definition). There also isn’t any way to control what overloaded properties get set, so its possible to add things the Cloudvox won’t understand.

I’m not sure there is any way around this given the way that PHP has implemented overloading. I do plan to work on a set of Cloudvox classes using another language that handles overloading a bit better, like C#, but for now you should only overload to set the url and method properites for classes that can use them (see the Cloudvox docs for more details).

Sipping on some Limonade

If you know of the excellent Ruby Framework Sinatra but you want to code your project in PHP, fear not - check out the equally excellent PHP framework called Limonade. It’s the functional equivalent of Sinatra for PHP.

Using Limonade with our set of Cloudvox JSON classes makes building cloud telephony applications very simple. The biggest benefit is that you don’t have to split up the different steps in your application (i.e., collecting input, validating input, re prompting, etc.) into different PHP files (which can be kind of a pain) - all of your steps can be contained within a single file.

Limonade lets you set a URL “route” that Cloudvox can send HTTP requests to with results, and to get rendered JSON for another application step. For example:

This “Hello World” example - defined in a script named sample.php - could be accessed by hitting http://somehost.com/index.php?/start. To make things easier, we’ll use a little Apache magic to allow URL rewriting:

This will let us access the above URL by hitting http://somehost.com/index.php/start.

A simple demo app using the Cloudvox JSON helper classes and the Limonade Framework can be seen below. You can use this sample application with a new Cloudvox account to get started building cloud telephony applications.

This simple app demonstrates how powerful the Cloudvox JSON API is for creating cloud telephony apps. When coupled with an elegant framework like Limonade, sophisticated, cloud-based telephony applications are readily available to any developer that wants to build one.

The helper classes for the Cloudvox API are obviously a work in progress, so if anyone reading this has comments or suggestions feel free to let me know - mheadd [at] voiceingov.org.

Two new websites built with Limonade: RoadFinger by Imre Mehesz Night party by Matěj Grabovský

Tue, 16 Mar 2010 10:00:00 +0100

Two new websites built with Limonade:

RoadFinger by Imre Mehesz
Night party by Matěj Grabovský

http://www.limonade-php.net

Mon, 15 Mar 2010 16:06:27 +0100

Limonade now has its own domain name ;-)

How to use content_for and partial

Wed, 10 Mar 2010 09:57:00 +0100

This tutorial will teach you how to use content_for().

As an example, let’s use this default layout:


  
    Our big bold header

See that we have not only our usual $content variable to render the content, but also a second variable called $side, which will be responsible to render our sidebar.

Next, create a controller function to handle the home action of our app:

# GET /
dispatch('/', 'home');
function home() {
  return render('home.html.php');
}

And, the home.html.php view file:




  Item 1
  Item 2




Home Action
Main content…

Finally, refresh the page to see that our sidebar now receives the content of our 'side' block.

To improve our code, let’s use the partial function, which will render view file at that point within the current rendered view.

Change the file home.html.php to:



  



Home Action
Main content…

And create a file called _sidebar.html.php in the view folder. Note that the underscore is optional.


  Item 1
  Item 2

Now you can break your views into modular files. It’s useful to insert specific CSS or JS and to make some AJAX stuff.

Want to share your limonade experience, your tips, a tutorial ? Now you can submit them...

Mon, 08 Mar 2010 19:48:16 +0100

Want to share your limonade experience, your tips, a tutorial ? Now you can submit them directly on this tumblr.

New limonade branching model

Sat, 23 Jan 2010 20:07:58 +0100

master branch is now the bleeding edge / integration branch
stable branches are named: X.X-stable (currently last stable is 0.4-stable)
tags remains the same: vX.X.X (0.4.6 is actualy the last tag)

How to Handle a Pull Request from GitHub when Fork Queue doesn't work

Sat, 23 Jan 2010 17:12:00 +0100

Since thursday, the Limonade github fork queue seems to be broken (or something’s wrong with GitHub). But I wanted to apply Colin’s last commit before working on the project today.

So, I followed this article and finally, it was very easy.

# Setup repo as a remote branch
git remote add -f cbrumelle git://github.com/cbrumelle/limonade.git

# Create the local copy
git checkout -b cbrumelle/0.5

# Get their changes into my personal working branch:
git checkout 0.5
git cherry-pick 6f556e7 #

Then I clean up my project by removing Colin’s branches (maybe there’s a nicer way to do that):

# First I list my branches
git branch -a

# this is the output:
  0.4
* 0.5
  cbrumelle/0.5
  master
  remotes/cbrumelle/0.4
  remotes/cbrumelle/0.5
  remotes/cbrumelle/master
  remotes/origin/0.4
  remotes/origin/0.5
  remotes/origin/master

# Then I delete the local copy
git branch -d cbrumelle/0.5

# And the remote ones
git branch -r -d cbrumelle/0.4
git branch -r -d cbrumelle/0.5
git branch -r -d cbrumelle/master

# finally remove remote repository reference
git remote rm cbrumelle

Limonade 0.4.6 is available

Mon, 30 Nov 2009 10:05:58 +0100

Changes:

[CHANGED] for IIS/Windows compatibility: file_path() normalizes paths in *nix way, even on windows (backslashes are converted in slashes, double slashes are replaced by one). Refactoring options paths in run() to fix paths on windows.
[FIXED] Removes php short open tags in default limonade views to be compatible with php5.3 default configuration (short_open_tags disabled)
[FIXED] Big security issue in render_file that allows accessing any files from outside public folder using ../ [#35]

I have updated Wikir and the blog example. Please update your code!