Re: Backwards compatibility broken with URL()... for the better?

2008-07-22 Thread Magnus Holm
Yes and no. The gems are based on my tree, but I'll always try to keep my tree equal to _why's. If there's some commits I'm not sure if he will merge, I put them in a branch (so I don't mess up the master). On Tue, Jul 22, 2008 at 4:33 AM, Bluebie, Jenna [EMAIL PROTECTED] wrote: I thought your

Re: Backwards compatibility broken with URL()... for the better?

2008-07-21 Thread Magnus Holm
I have no problem with breaking backwards compatibility. After all, Camping 2.0 is a major upgrade. About session.rb, even though it was I who wrote the code, _why merged it (despite your warnings) and he's the to remove it :-) On Mon, Jul 21, 2008 at 2:46 AM, Bluebie, Jenna [EMAIL PROTECTED]

Re: Backwards compatibility broken with URL()... for the better?

2008-07-21 Thread Bluebie, Jenna
I thought your gems were based on your tree, not _why's? My mistake? ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list

Backwards compatibility broken with URL()... for the better?

2008-07-20 Thread Bluebie, Jenna
In 1.5, to get a full url to ones camping app, you had to do: this_url = 'http:' + URL('/some_action').to_s Useful, for instance, in my openid consumer sample code, to give the openid doodad a return address But in camping 1.9 off jud's gems, URL now returns actual url's with http: and