| MIME-Version: | 1.0 |
| Resent-Date: | Tue, 9 Jun 2009 12:25:24 -0400 |
| Errors-To: | jifty-devel-bounces [...] lists.jifty.org |
| List-Help: | <mailto:jifty-devel-request [...] lists.jifty.org?subject=help> |
| content-type: | text/plain; charset="utf-8" |
| X-Virus-Scanned: | amavisd-new at mail.schaffhausen.de |
| Received: | from 31b.bestpractical.com (diesel.bestpractical.com [127.0.0.1]) by diesel.bestpractical.com (Postfix) with ESMTP id 78BBC19B831B for <bug-jifty [...] rt.cpan.org>; Tue, 9 Jun 2009 12:25:25 -0400 (EDT) |
| Received: | by 31b.bestpractical.com (Postfix, from userid 501) id E48F1946F84; Tue, 9 Jun 2009 12:25:24 -0400 (EDT) |
| Received: | from diesel.bestpractical.com (diesel.bestpractical.com [127.0.0.1]) by diesel.bestpractical.com (Postfix) with ESMTP id 0710919B830B; Tue, 9 Jun 2009 12:13:38 -0400 (EDT) |
| Received: | from mail.schaffhausen.de (mail.schaffhausen.de [62.225.106.251]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by diesel.bestpractical.com (Postfix) with ESMTP id 0DFB519B82FA for <jifty-devel [...] lists.jifty.org>; Tue, 9 Jun 2009 12:13:25 -0400 (EDT) |
| Received: | from localhost (localhost [127.0.0.1]) by mail.schaffhausen.de (Postfix) with ESMTP id EBA547B57F for <jifty-devel [...] lists.jifty.org>; Tue, 9 Jun 2009 17:54:56 +0200 (CEST) |
| Received: | from mail.schaffhausen.de ([127.0.0.1]) by localhost (mail.schaffhausen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuDKFvmQAPEm for <jifty-devel [...] lists.jifty.org>; Tue, 9 Jun 2009 17:54:56 +0200 (CEST) |
| Received: | from gast91.elmshorn.avantaxx.de (unknown [172.16.3.91]) by mail.schaffhausen.de (Postfix) with ESMTP id C940A7B4F0 for <jifty-devel [...] lists.jifty.org>; Tue, 9 Jun 2009 17:54:56 +0200 (CEST) |
| Delivered-To: | cpan-bug+jifty [...] diesel.bestpractical.com |
| Delivered-To: | j [...] diesel.bestpractical.com |
| Delivered-To: | jifty-devel [...] diesel.bestpractical.com |
| Subject: | [jifty-devel] Order of Actions in Request |
| Date: | Tue, 09 Jun 2009 17:54:56 +0200 |
| X-Spam-Level: | |
| Precedence: | list |
| X-Beenthere: | jifty-devel [...] lists.jifty.org |
| To: | Nifty apps in a Jiffy <jifty-devel [...] lists.jifty.org> |
| Content-Transfer-Encoding: | 7bit |
| List-Unsubscribe: | <http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel>, <mailto:jifty-devel-request [...] lists.jifty.org?subject=unsubscribe> |
| X-Enigmail-Version: | 0.95.7 |
| List-Archive: | <http://lists.jifty.org/pipermail/jifty-devel> |
| X-Spam-Status: | No, score=-2.6 required=7.0 tests=BAYES_00 autolearn=ham version=3.2.3 |
| List-Post: | <mailto:jifty-devel [...] lists.jifty.org> |
| X-Mailman-Version: | 2.1.9 |
| Message-ID: | <4A2E85D0.8040006 [...] schaffhausen.de> |
| Reply-To: | Nifty apps in a Jiffy <jifty-devel [...] lists.jifty.org> |
| Resent-To: | bug-jifty [...] rt.cpan.org |
| Resent-From: | jesse [...] 72-60-82-231.pools.spcsdns.net |
| User-Agent: | Thunderbird 2.0.0.21 (Macintosh/20090302) |
| Return-Path: | <jesse [...] bestpractical.com> |
| X-Original-To: | bug-jifty [...] rt.cpan.org |
| X-Original-To: | jesse [...] bestpractical.com |
| X-Original-To: | jifty-devel [...] lists.jifty.org |
| List-Subscribe: | <http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel>, <mailto:jifty-devel-request [...] lists.jifty.org?subject=subscribe> |
| Sender: | jifty-devel-bounces [...] lists.jifty.org |
| X-Greylist: | delayed 1104 seconds by postgrey-1.27 at diesel; Tue, 09 Jun 2009 12:13:26 EDT |
| X-Spam-Checker-Version: | SpamAssassin 3.2.3 (2007-08-08) on diesel.bestpractical.com |
| Resent-Message-ID: | <20090609162524.GE5107 [...] 72-60-82-231.pools.spcsdns.net> |
| List-ID: | Nifty apps in a Jiffy <jifty-devel.lists.jifty.org> |
| From: | Eric-Christian Koch <koch [...] schaffhausen.de> |
| X-RT-Original-Encoding: | us-ascii |
| Content-Length: | 1398 |
Hello,
i wonder if someone of you can give me a hint.
In my template i created some actions with giving them an order value.
@actions = (
$record1->as_update_action( order => 1),
$record2->as_update_action( order => 2)
)
And added them to a link:
onclick => [ { submit => \@actions ...
However, the order value did not make it into the JSON as the request
was send to the server.
So it was undef while processed in Jifty::Request.
After some debuging i added the following javascript code to the
Action.data_structur function:
Action.prototype.data_structure = function() {
var a = {};
a['moniker'] = this.moniker;
a['class'] = this.actionClass;
if (this.register && this.register.id) {
var tmp = this.register.id.match(/^J:A-(\d+)-/);
if (tmp.length == 2)
a['order'] = tmp[1];
}
....
Now the JSON, send by the ajax request, contains the order value and the
actions are executed in the correct order.
Still, i dont know if i probably misunderstood something about the order
option.
I would realy like to know if someone of you has figured out how it is
supposed to work.
PS: Sorry for my bad english. ;)
Thanks in advance,
Eric
Show quoted text
_______________________________________________
jifty-devel mailing list
jifty-devel@lists.jifty.org
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel