<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://actionflow.devdonkey.org/lib/styles/feed.css" type="text/css"?>
<rss version="2.0">
    <channel>
        <title>ActionFlow</title>
        <description></description>
        <link>http://actionflow.devdonkey.org/</link>
        <lastBuildDate>Mon, 07 Jul 2008 02:23:38 -0400</lastBuildDate>
        <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
        <image>
            <url>http://actionflow.devdonkey.org/lib/images/favicon.ico</url>
            <title>ActionFlow</title>
            <link>http://actionflow.devdonkey.org/</link>
        </image>
        <item>
            <title>actionflow - old revision restored</title>
            <link>http://actionflow.devdonkey.org/actionflow?rev=1200083658&amp;do=diff1200083658</link>
            <description>simplicity and fluidity with a Rails twist

What's ActionFlow anyways ?!

 ActionFlow is a declarative flow controller usable by Ruby on Rails applications. Its an efficient, easy and simple Domain Specific Language which allows developers to organize a suite of user actions aimed at a precise goal.</description>
            <author>Luc Boudreau</author>
            <pubDate>Fri, 11 Jan 2008 15:34:18 -0400</pubDate>
        </item>
        <item>
            <title>creating_views</title>
            <link>http://actionflow.devdonkey.org/creating_views?rev=1183045749&amp;do=diff1183045749</link>
            <description>There are four ways to send events to an ActionFlow controller. 

	*  By a link
	*  By a form
	*  By an AJAX link
	*  By an AJAX form

 Any ActionFlow controller views can easily use these helper methods to create views that interact with the ActionFlow framework. To have all the details, consult the BaseHelper API.</description>
            <author>Luc Boudreau</author>
            <pubDate>Thu, 28 Jun 2007 11:49:09 -0400</pubDate>
        </item>
        <item>
            <title>basic_mapping_example</title>
            <link>http://actionflow.devdonkey.org/basic_mapping_example?rev=1183045349&amp;do=diff1183045349</link>
            <description>There are two main parts in an ActionFlow controller. Its mapping and it’s step implementations. Here’s an example mapping taken from the Demo Application. There are many more mapping instructions available and it’s up to you to read the API. Don’t be lazy and read it: it’s definitely worth it if you are going to use ActionFlow.</description>
            <author>Luc Boudreau</author>
            <pubDate>Thu, 28 Jun 2007 11:42:29 -0400</pubDate>
        </item>
        <item>
            <title>success_stories - created</title>
            <link>http://actionflow.devdonkey.org/success_stories?rev=1183043460&amp;do=diff1183043460</link>
            <description>I’d like to hear from the people who tried ActionFlow. Please provide feedback as to what went wrong and what was just perfect so that I can improve it to better fit your needs.

Use the discussion controls down this page, and thanks a million !</description>
            <author>Luc Boudreau</author>
            <pubDate>Thu, 28 Jun 2007 11:11:00 -0400</pubDate>
        </item>
        <item>
            <title>flow_execution_key</title>
            <link>http://actionflow.devdonkey.org/flow_execution_key?rev=1181163184&amp;do=diff1181163184</link>
            <description>The flow execution key is a random string of 64 alphanumeric characters. It allows the ActionFlow Session Handler to restore a given state and continue a flow execution from the correct state hash snapshot.

The flow execution key always has to be returned to the controller after the execution of a view by the user. Each submission of data has to be related to a flow key. If you submit data to an ActionFlow controller without providing a key, the controller will assume that you are requesting a …</description>
            <author>Luc Boudreau</author>
            <pubDate>Wed, 06 Jun 2007 16:53:04 -0400</pubDate>
        </item>
        <item>
            <title>session_handler</title>
            <link>http://actionflow.devdonkey.org/session_handler?rev=1181163143&amp;do=diff1181163143</link>
            <description>The session handling logic is encapsulated in the SessionHandler module extension which is added to the ActionFlow::Base class eval at the plugin initialization.

The session handler has the following responsibilities.

	*  Expose the state variable, which is a hash that saves data which is relevant to the current flow state. 
	*  Generate state snapshots in the session hash.
	*  Persist and restore each state data and make sure the state variable contains the data corresponding to the correct r…</description>
            <author>Luc Boudreau</author>
            <pubDate>Wed, 06 Jun 2007 16:52:23 -0400</pubDate>
        </item>
        <item>
            <title>state</title>
            <link>http://actionflow.devdonkey.org/state?rev=1181163042&amp;do=diff1181163042</link>
            <description>There is a mechanism available in ActionFlow which enables users to store data inside what is called a flow state. It is imlemented as a Hash object which offers a historical snapshot of himself according to a user’S position inside a flow. This allows users to hit the back button and restore exactly the flow state they were in at that precise point in the flow.</description>
            <author>Luc Boudreau</author>
            <pubDate>Wed, 06 Jun 2007 16:50:42 -0400</pubDate>
        </item>
    </channel>
</rss>
