Y''all may be interested in the discussion on #6645 (Prototype), re the behavior of Ajax.Request. http://dev.rubyonrails.org/ticket/6645 This started because of changeset [5448] (the "Ajax mega-patch" - #6366) http://dev.rubyonrails.org/changeset/5448 http://dev.rubyonrails.org/ticket/6366 TAG --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Tom Gregory schrieb:> Y''all may be interested in the discussion on #6645 (Prototype), re > the behavior of Ajax.Request. > http://dev.rubyonrails.org/ticket/6645 > > This started because of changeset [5448] (the "Ajax mega-patch" - #6366) > http://dev.rubyonrails.org/changeset/5448 > http://dev.rubyonrails.org/ticket/6366Thanks Tom, that brought some light to a broken PHP application (PostNuke .8 SVN) using scriptaculous 1.6.5 (which I will now revert to 1.6.4). Imho the change in the Form.serialize behaviour has a major impact on everthing outside of Ruby. *I* consider this as a major bug for non-Rubians ;-). A possible solution would be a parameter to have a "switch" to make the Form.serialize output backwards compatible. Frank -- "Laut einer Studie der deutschen Ärztevereinigung sterben immer mehr Rentner vor dem Computer. Sie drücken versehentlich die Tastenkombination Alt+Entfernen." http://www.landseer-stuttgart.de http://www.pn-cms.de --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 11/20/06, Frank Schummertz <frank.schummertz-wuHXZRSNxgaBAmxm6OvjtTjhTm2NLCe8@public.gmane.org>> Imho the change in the Form.serialize behaviour has a major impact on > everthing outside of Ruby. *I* consider this as a major bug for > non-Rubians ;-).What is the bug anyway? The second last comment by mislav says: $H("folder=foo&uid[]=10801&uid[]=10802&uid[]=10803".toQueryParams()).toQueryString() gives "folder=foo&uid%5B%5D=10801&uid%5B%5D=10802&uid%5B%5D=10803" and this is how it should be. And it is the format PHP expects it. If you want an array in PHP, you have to use "foo[]", example 12-11 and the paragraph above at http://www.php.net/manual/en/language.variables.external.php --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Ajax.Request recently changed in the trunk. It now accepts hashes for parameters (good), but internally converts query strings to hashes, then back again (bad, IMHO). The bug description includes the following: "My idea behind this was to encourage handling query params as hashes throughout the whole framework - my next ticket/patch will be about Form.serialize returning a hash (not a string) because the results are usually passed directly to an Ajax.Request anyway. But before that, something must be sorted out - parameters with multiple values (yeah, again)." I personally think this is a bad idea--at least the way it''s currently implemented--but wanted a broader response from the intelligent people on the list, whether or not you agree with me. As for the specific case cited, I think it *was* a problem after the "mega-patch" but has since been fixed in the trunk. Not sure on that, though, it wasn''t something I tested, but rather a complaint from another user. TAG On Nov 20, 2006, at 1:26 PM, Martin Bialasinski wrote:> > On 11/20/06, Frank Schummertz <frank.schummertz-wuHXZRSNxgaBAmxm6OvjtTjhTm2NLCe8@public.gmane.org> > >> Imho the change in the Form.serialize behaviour has a major impact on >> everthing outside of Ruby. *I* consider this as a major bug for >> non-Rubians ;-). > > What is the bug anyway? The second last comment by mislav says: > > $H("folder=foo&uid[]=10801&uid[]=10802&uid[]=10803".toQueryParams > ()).toQueryString() > > gives > > "folder=foo&uid%5B%5D=10801&uid%5B%5D=10802&uid%5B%5D=10803" > > and this is how it should be. And it is the format PHP expects it. > If you want an array in PHP, you have to use "foo[]", example 12-11 > and the paragraph above at > http://www.php.net/manual/en/language.variables.external.php > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Martin Bialasinski schrieb:> What is the bug anyway? The second last comment by mislav says:The bugs is that this function changed its behaviour and is not usable now without Ruby. For me as PHP developer this is more reason than I need to call this a bug :-) Frank -- "Laut einer Studie der deutschen Ärztevereinigung sterben immer mehr Rentner vor dem Computer. Sie drücken versehentlich die Tastenkombination Alt+Entfernen." http://www.landseer-stuttgart.de http://www.pn-cms.de --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 11/20/06, Tom Gregory <tomg-PGZyUNKar/Q@public.gmane.org> wrote: I don''t use the Ajax routines from prototype.js, but I will comment anyway :-)> Ajax.Request recently changed in the trunk. It now accepts hashes > for parameters (good), but internally converts query strings to > hashes, then back again (bad, IMHO).You mean it accepts both a String or an Object as the values to be transmitted, but does the round-trip for strings? Seems unnecessary.> "My idea behind this was to encourage handling query params as hashes > throughout the whole frameworkGood idea.> - my next ticket/patch will be about > Form.serialize returning a hash (not a string)Uuh, changing the default return type of the function? Sounds like a bad idea.> But before > that, something must be sorted out - parameters with multiple valuesThat is sorted out, it seems. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 11/20/06, Frank Schummertz <frank.schummertz-wuHXZRSNxgaBAmxm6OvjtTjhTm2NLCe8@public.gmane.org> wrote:> > Martin Bialasinski schrieb: > > The bugs is that this function changed its behaviour and is not usable > now without Ruby. > > For me as PHP developer this is more reason than I need to call this a > bug :-)I use PHP as well, but what IS the bug? I don''t see one. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Martin Bialasinski schrieb:> I use PHP as well, but what IS the bug? I don''t see one.I will do some more tests later today and try to track it down. -- "Laut einer Studie der deutschen Ärztevereinigung sterben immer mehr Rentner vor dem Computer. Sie drücken versehentlich die Tastenkombination Alt+Entfernen." http://www.landseer-stuttgart.de http://www.pn-cms.de --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 11/21/06, Frank Schummertz <frank.schummertz-wuHXZRSNxgaBAmxm6OvjtTjhTm2NLCe8@public.gmane.org> wrote:> > Martin Bialasinski schrieb: > > > I use PHP as well, but what IS the bug? I don''t see one. > > I will do some more tests later today and try to track it down. >Best thing would be, if you could put a page online with a simple example. Then one can observe, debug and fiddle around with firebug. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Concerning my problem...
It seems that the Ajax.Request is the problem, not the Form.serialize.
Sorry for the confusion.
Please find below the code I used. It is by no means secure or well
formed ;-).
Try it once with scriptaculous 1.6.4 and then with 1.6.5 and watch the
results from the test.php. You will notice that with 1.6.5 only the
third entry from the sortable gets through to the php file. The params
are the same in both cases.
Any help is welcome.
Frank
------snip #1-------
<?php
$sort = $_POST[''sort''];
$something = $_POST[''something''];
$out = "SOMETHING#" . implode(''#'', $something) .
"#SORT:" .implode(''#'',
$sort);
header(''HTTP/1.0 200 OK'');
echo utf8_encode($out);
?>
------snip #2-------
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="de_DE">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-15" />
<title>Test</title>
<script type="text/javascript"
src="ajax/prototype.js"></script>
<script type="text/javascript"
src="ajax/scriptaculous.js"></script>
<script type="text/javascript">
function send()
{
var pars = Form.serialize(''test'') +
''&'' + Sortable.serialize(''sort'');
alert(pars);
var myAjax = new Ajax.Request(
"test.php",
{
method: ''post'',
parameters: pars,
onComplete: receive
});
}
function receive(req)
{
alert(req.responseText);
return;
}
function init()
{
var sortable = Sortable.create(''sort'');
}
</script>
</head>
<body onload="init();">
<form id="test" name="test" action="test.php"
method="post">
<div>
<input type="hidden" name="something[a]"
value="a" />
<input type="hidden" name="something[b]"
value="b" />
<input type="input" name="something[c]"
value="cde" />
<ul id="sort">
<li id="sort_1">111111</li>
<li id="sort_2">222222</li>
<li id="sort_3">333333</li>
</ul>
<input type="submit" name="submit"
value="Submit"
onclick="send();return false;"/>
</div>
</form>
</body>
</html>
--
"Laut einer Studie der deutschen Ärztevereinigung sterben immer
mehr Rentner vor dem Computer. Sie drücken versehentlich die
Tastenkombination Alt+Entfernen."
http://www.landseer-stuttgart.de
http://www.pn-cms.de
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
On Nov 20, 11:29 pm, "Martin Bialasinski" <klingel...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 11/20/06, Tom Gregory <t...-PGZyUNKar/Q@public.gmane.org> wrote: > > Ajax.Request recently changed in the trunk. It now accepts hashes > > for parameters (good), but internally converts query strings to > > hashes, then back again (bad, IMHO). > > You mean it accepts both a String or an Object as the values to be > transmitted, but does the round-trip for strings? Seems unnecessary.The reason behind this was to reduce the number of string hacks (inspecting, appending) to add parameters internally in the framework. There is really no reason to toss the urlencoded string of parameters back and forth through the framework when such string is just transport. In PHP you handle parameters as associative arrays, in Ruby/Rails you handle them as hashes, and in Prototype we should move on from the dumb, flattened string of parameters to something better - Hash (and Array for multiple values). Only prior to making an actual HTTP request the parameters should be flattened and urlencoded. Not before that.> > "My idea behind this was to encourage handling query params as hashes > > throughout the whole framework > > Good idea.I''m glad you agree. And if anyone needs a safe hash (that can contain even reserved keys like "each", "map", etc.) I have a proposal for that: http://dev.rubyonrails.org/ticket/6649> > - my next ticket/patch will be about > > Form.serialize returning a hash (not a string) > > Uuh, changing the default return type of the function? Sounds like a bad idea.APIs change. Destruction is the form of creation. On the other hand, maybe the ticket will be rejected - who knows? But, it is my opinion that there is really no sense for Form to urlencode serialized data anymore - Ajax now handles that. Let HTTP stuff worry about HTTP encoding, let Form collect the data, let Hash and Array methods deal with adding, merging, editing and iterating over data. People pass the results of Form.serialize directly to Ajax.Request anyway. -- Mislav --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 11/24/06, Mislav <mislav.marohnic-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > On Nov 20, 11:29 pm, "Martin Bialasinski" <klingel...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > You mean it accepts both a String or an Object as the values to be > > transmitted, but does the round-trip for strings? Seems unnecessary. > > The reason behind this was to reduce the number of string hacks > (inspecting, appending) to add parameters internally in the framework.That makes sense.> > > - my next ticket/patch will be about > > > Form.serialize returning a hash (not a string) > > > > Uuh, changing the default return type of the function? Sounds like a bad idea. > > APIs change. Destruction is the form of creation. On the other hand, > maybe the ticket will be rejected - who knows? But, it is my opinion > that there is really no sense for Form to urlencode serialized data > anymore - Ajax now handles that.How about adding a new function that returns an Object. and change the Ajax functions to use this new function, ...> People pass the results of Form.serialize directly to Ajax.Request > anyway.... and document the new function as the preferred way from then on. This would not disrupt existing code. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 12/2/06, Martin Bialasinski <klingeling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > How about adding a new function that returns an Object. and change the > Ajax functions to use this new function, and document the new function as > the preferred way from then on. > This would not disrupt existing code.How about adding an optional parameter to the existing function? With it you could control the return type (hash or string). I had this idea for some time. I''m going to post the ticket soon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On 12/2/06, Mislav Marohnić <mislav.marohnic@gmail.com> wrote:> How about adding an optional parameter to the existing function? With it you > could control the return type (hash or string).Would work as well, when the default is "as string". That said, the parameter should be "string"|"hash" and not false|true to make it easier to understand when reading the code. And your fully functional hash proposal should really replace the current implementation which looks like its origins were a need for a simple fromQuery / toQuery mechanism. New bug report where the current implementation bites the users: http://dev.rubyonrails.org/ticket/6788 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs@googlegroups.com To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi, I know it is bold to ask on a RoR hosted list about a PHP Framework ;) But I found Symfony http://www.symfony-project.com/ which uses prototype and scriptaculous as javascript+effect libs. I wonder if it is mature enough to build mid size applications on it. I know askeet.com and I am currently doing the 24day tutorial, but I would like to see some more references if anyone has. Thanks! Fabian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Fabian Lange wrote:> Hi, > I know it is bold to ask on a RoR hosted list about a PHP Framework ;) > But I found Symfony http://www.symfony-project.com/ which uses prototype and > scriptaculous as javascript+effect libs. > I wonder if it is mature enough to build mid size applications on it. I know > askeet.com and I am currently doing the 24day tutorial, but I would like to > see some more references if anyone has. > > Thanks! > Fabian >We have used symfony for a few projects and really like it. We plan to use it on our next big project. I haven''t actually worked with RoR, but my impression is that symfony intends to be RoR for PHP. It has "pake" which is like "rake", CRUD scaffolding and several other agile-development aspects. It uses propel, creole, and jargon for database connection and object-to-database mapping. I imagine if you like RoR you would like symfony. Apparently Yahoo Bookmarks uses symfony so you might surmise that there is not a significant performance penalty over other PHP frameworks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On Dec 8, 2006, at 12:01 PM, Ken Snyder wrote:> > Fabian Lange wrote: >> Hi, >> I know it is bold to ask on a RoR hosted list about a PHP >> Framework ;) >> But I found Symfony http://www.symfony-project.com/ which uses >> prototype and >> scriptaculous as javascript+effect libs. >> I wonder if it is mature enough to build mid size applications on >> it. I know >> askeet.com and I am currently doing the 24day tutorial, but I >> would like to >> see some more references if anyone has. >> >> Thanks! >> Fabian >> > We have used symfony for a few projects and really like it. We > plan to > use it on our next big project. I haven''t actually worked with > RoR, but > my impression is that symfony intends to be RoR for PHP. It has > "pake" > which is like "rake", CRUD scaffolding and several other > agile-development aspects. It uses propel, creole, and jargon for > database connection and object-to-database mapping. I imagine if you > like RoR you would like symfony. Apparently Yahoo Bookmarks uses > symfony so you might surmise that there is not a significant > performance > penalty over other PHP frameworks. >I use symfony personally, and for work. I have a bit of RoR experience, but I am vastly more informed about PHP as a whole. The symfony project has it''s share of growing pains, much as any framework. I don''t think they intend to be a Rails clone, so much as trying to implement the inovations Rails has pioneered and PHP can support. Personally I think the CRUD (aka scaffolding) in both frameworks leaves way to much to be desired so I just don''t use it. As far as a "mid size" application, I wrote an application in symfony that has several hundred users, and a database size around 40mg. If you use solid design, and the advantages of your framework, you should end up with a good product. I would have to say most of the time applications fail, not based on the framework, but on the design of the application. Take that with a grain of salt of course. -Greg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
I haven''t ever worked with Symfony, but I can vouch for Code Igniter. Prototype and Scriptaculous don''t come "built-in", but I''m happily using them together. Fabian Lange <Fabian.Lange-S0/GAf8tV78@public.gmane.org> wrote: Hi, I know it is bold to ask on a RoR hosted list about a PHP Framework ;) But I found Symfony http://www.symfony-project.com/ which uses prototype and scriptaculous as javascript+effect libs. I wonder if it is mature enough to build mid size applications on it. I know askeet.com and I am currently doing the 24day tutorial, but I would like to see some more references if anyone has. Thanks! Fabian --------------------------------- Cheap Talk? Check out Yahoo! Messenger''s low PC-to-Phone call rates. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---