[Jifty-commit] r3913 - in jifty/trunk: .
jifty-commit at lists.jifty.org
jifty-commit at lists.jifty.org
Thu Aug 16 23:08:51 EDT 2007
Author: sterling
Date: Thu Aug 16 23:08:51 2007
New Revision: 3913
Modified:
jifty/trunk/ (props changed)
jifty/trunk/lib/Jifty/Manual/Glossary.pod
Log:
r8678 at dynpc145: andrew | 2007-08-14 19:26:11 -0500
Adding tangent and return to the glossary.
Modified: jifty/trunk/lib/Jifty/Manual/Glossary.pod
==============================================================================
--- jifty/trunk/lib/Jifty/Manual/Glossary.pod (original)
+++ jifty/trunk/lib/Jifty/Manual/Glossary.pod Thu Aug 16 23:08:51 2007
@@ -141,6 +141,10 @@
success or failure, and further detail about why or how. It can also contain
arbitrary "content". See L<Jifty::Result>.
+=item return
+
+After performing a L</tangent> a user may perform a L</return> to invoke the L</continuation> created by the original tangent.
+
=item schema
The B<schema> for a L</model> represents the structure of the data stored in an individual item in that model's L</collection>. See L<Jifty::DBI::Schema>.
@@ -176,6 +180,10 @@
user type them again. Most L</action>s have form fields which are sticky on
failure, so the user can update the information and try again.
+=item tangent
+
+A tangent is a link or redirect that causes Jifty to save the current state into a L</continuation> for a later L</return>. This operation is handy for situations when you want to jump to another page or form, but return to this page when the user is done with the "tangent" page. Because of the use of continuations, this can be especially handy because a user could go on multiple tangents and eventually return to the start.
+
=item upgrade
Generally, your Jifty application will change over time. Most of these changes will be simple changes to behavior or appearance. When changes are made to the L</schema> structure of your database, you may need to perform an B<upgrade>. An B<upgrade> is the process by which you rename columns, initialize data, or otherwise update information that needs to be updated when a change to the database needs to be made. See L<Jifty::Upgrade>, L<Jifty::Manual::Upgrading>, and L<Jifty::Script::Schema>.
More information about the Jifty-commit
mailing list