Sorry that link should be: http://gist.github.com/341555#file_reststop2.rb
On Tue, Mar 23, 2010 at 3:49 PM, Matt Zukowski wrote:
> Alright I spent a few hours trying to see if I can make things work with
> 2.0.
>
> I was able to make some progress (mostly thanks to Magnus' help!) but ran
> out o
Alright I spent a few hours trying to see if I can make things work with
2.0.
I was able to make some progress (mostly thanks to Magnus' help!) but ran
out of time before I could get things runnings.
Here's the result:
http://gist.github.com/341555
I'm not sure when I will get a chance in the n
code = %q{
# This Ruby code will be called everytime Camping.goes is called.
# And "Camping" is replaced with the app module, so you can do stuff like:
def Camping.foo
puts "Hello World!"
end
# You probably just want to do:
module Camping
include MyExtension
end
}
# For Camping.goes
Camping::
Okay got it... but as I look at this a bit more, the ridiculous things I had
to do to make Reststop work (for Camping 1.0) are all coming back to me.
As I recall, the root of all evil was Camping#goes. I had to override it in
order to inject the Reststop code into Camping. Camping#qsp was the seco
@env['REQUEST_METHOD'] is the HTTP method send by the client, @method is the
method (in lowercase) Camping is going to run ("r404" for 404 etc.)
// Magnus Holm
On Tue, Mar 23, 2010 at 17:01, Matt Zukowski wrote:
> Hey Magnus, while we have your attention, in 2.0 how do I get access to
> e['REQ
Hey Magnus, while we have your attention, in 2.0 how do I get access to
e['REQUEST_METHOD'] inside the 'service' method? Trying to figure this out
as we speak...
On Tue, Mar 23, 2010 at 11:50 AM, Magnus Holm wrote:
> I find extending Camping apps to be quite easy, since it's all classes and
> mo
Indeed, but for now I think http://stuff.judofyr.net/camping-docs/ (or, the
URL would actually be camping.rubyforge.org when released) would be enough.
I think we're pretty much ready for a release. If you'd like, I could mark
HEAD as 2.0.rc1 and push it out to Gemcutter. Then you guys who have 2.
I find extending Camping apps to be quite easy, since it's all classes and
modules, but I can understand that extending Camping itself can be
difficult/weird. That said, I think a lot can be solved by defining
#included and #extended. It would be great if you could tell us a bit
exactly the problem
I actually have a reststop app up and running fine with Camping 2.0 (check
out Taskr at http://github.com/zuk/taskr). Tthe catch is that it's a version
of 2.0 that I forked about this time last year, and looking at the github
graph, Magnus has committed a whole slew of changes since then. So whatev
9 matches
Mail list logo