Sure, you're the boss. Camping is ready when you are ready!
Well, I don't have any new ideas. We just need to clean up the documentation!
On Mon, Jul 7, 2008 at 6:46 PM, _why <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 03, 2008 at 02:52:41AM +0200, Magnus Holm wrote:
>> Come on, you lazy interrogati
On Thu, Jul 03, 2008 at 02:52:41AM +0200, Magnus Holm wrote:
> Come on, you lazy interrogative! Are your shoes too heavy? :-(
Bzzt! (Drawing on backup camping power grids...) Very sorry to be
bad about this. Yeah, lots of Shoes stuff going on this week as
we're shooting for a July 31st release
On Tue, Jun 24, 2008 at 5:07 PM, _why <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 24, 2008 at 01:05:54PM +0200, Magnus Holm wrote:
> > Man, that's way better than removing 135 bytes! I *love* the
> implementation!
>
> I have always wanted to use Method#to_proc in Camping.
>
> > Alright! What about re
On Jun 25, 2008, at 3:18 PM, zimbatm wrote:
One contra argument is that markaby is pretty old. Last time I checked
the trunk it was in a weird state. If I remember well,
it has been made Camping incompatible in favor of some Rails (!)
goodness.
Yeah, I removed Markaby from one of our Rails p
2008/6/24 _why <[EMAIL PROTECTED]>:
> I need to figure out if I want to merge zimbatm's Markaby patch.
These are the reasons behind the patch :
* Historically Markaby was expurged to attain the 0 dependencies
walhalla. Rack has changed it all
* Camping apps are really nice in a 1 file setup. Marka
Nice! You should also go through the documentation, it's pretty bad at
the moment...
On Tue, Jun 24, 2008 at 5:07 PM, _why <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 24, 2008 at 01:05:54PM +0200, Magnus Holm wrote:
>> Man, that's way better than removing 135 bytes! I *love* the implementation!
>
> I
On Tue, Jun 24, 2008 at 01:05:54PM +0200, Magnus Holm wrote:
> Man, that's way better than removing 135 bytes! I *love* the implementation!
I have always wanted to use Method#to_proc in Camping.
> Alright! What about releasing 2.0? I've closed a lot of tickets on the
> tracker, and I don't think
Then I'm +1.
Can't wait to see my tests fail with 2.0 (I will obviously have to
update Mosquito for the new version, although if we still have .run
it should
work unmodified).
On Jun 24, 2008, at 3:14 PM, Magnus Holm wrote:
R isn't gone! Feel free to use both (and if you use R, it would no
R isn't gone! Feel free to use both (and if you use R, it would not
add more routes:
module Camping::Controllers
class Index;end
class Advanced < R '/(some regex';end
# /advanced will NOT route to Advanced
end
On Tue, Jun 24, 2008 at 3:09 PM, Julik Tarkhanov
<[EMAIL PROTECTED]> wrote:
> Doe
Does that mean we are losing the possinility for multiple routes per
controller and such?
Or should I return something magic from self.urls to make controllers
function the pre-2.0 way?
On Jun 24, 2008, at 1:05 PM, Magnus Holm wrote:
Alright! What about releasing 2.0? I've closed a lot of t
Man, that's way better than removing 135 bytes! I *love* the implementation!
Alright! What about releasing 2.0? I've closed a lot of tickets on the
tracker, and I don't think we need more for a 2.0. There is no point
of waiting anymore, IMO!
On Tue, Jun 24, 2008 at 12:14 AM, _why <[EMAIL PROTECTE
On Mon, Jun 23, 2008 at 12:16:35AM +0200, Magnus Holm wrote:
> The route maker's job is basically two things:
> - Make sure that all controllers includes the right mixins
> - If any controllers doesn't respond to "urls" (aka. haven't been inherited
> from R) define "urls" as ClassName.downcase
>
Yeah, I had to move the internal controller to the bottom, so it would include
Models too. I've never liked the route maker, and if we can do almost the same
without (and 135 bytes) it I would be happy.
Do you have any plans on making Equipment Camping 2.0 ready? Is there much to
do? Perhaps you c
Hey, why not. I'd much prefer to at least allow a "class Name < R;
end" construct
Longer answer :
The constants problem can also be avoided by checking it's type. I
never encountered that problem because that Controllers module is
exactly there to separate the code logic. Other constants must go
The route maker's job is basically two things:
- Make sure that all controllers includes the right mixins
- If any controllers doesn't respond to "urls" (aka. haven't been inherited
from R) define "urls" as ClassName.downcase
The first point can be accomplished within R, but not the latter. But
15 matches
Mail list logo
