From ruby at monnet-usa.com Sun Nov 1 16:23:29 2009 From: ruby at monnet-usa.com (Philippe Monnet) Date: Sun, 01 Nov 2009 14:23:29 -0700 Subject: Using #rubycamping in Twitter posts Message-ID: <4AEDFC51.4090104@monnet-usa.com> To align with the idea of a rubycamping.com site I am now using the #rubycamping in my tweets! -------------- next part -------------- An HTML attachment was scrubbed... URL: From deveritt at innotts.co.uk Sun Nov 1 18:34:02 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Sun, 1 Nov 2009 23:34:02 +0000 Subject: free Camping cloud hosting?? In-Reply-To: References: <1F12648A-F296-4C92-AE9C-3026914CB8C3@innotts.co.uk> Message-ID: Jon: I added your guide to the links on the 'Miscellaneous Camping links' page. Please correct/amend/add anything else you think helps :-) Dave > Hi all, > > I've been lurking about for a while, but thought it's time I added > something! > > I had a go with Heroku (which I'm pretty impressed with - thanks > Dave). As a bit of a play with it I made the guide below on how to > use camping 2.0 on it. Let me know if you think it's handy (one for > the wiki perhaps) and I can update when 2.0 is released. > > http://radiant-sunset-95.heroku.com/how-to-run-camping-2-apps-on- > heroku > > Jon From blueberry at creativepony.com Sun Nov 1 19:18:49 2009 From: blueberry at creativepony.com (Jenna Fox) Date: Mon, 2 Nov 2009 11:18:49 +1100 Subject: Using #rubycamping in Twitter posts In-Reply-To: <4AEDFC51.4090104@monnet-usa.com> References: <4AEDFC51.4090104@monnet-usa.com> Message-ID: <4962241B-F5E5-4710-BD58-B1F7F9B14FBF@creativepony.com> I thought we settled on whywentcamping? On 02/11/2009, at 8:23 AM, Philippe Monnet wrote: > To align with the idea of a rubycamping.com site I am now using the > #rubycamping in my tweets! > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From deveritt at innotts.co.uk Sun Nov 1 19:22:16 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Mon, 2 Nov 2009 00:22:16 +0000 Subject: Camping book Message-ID: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> I added some basic material to the GitHub Camping Wiki (new pages): http://wiki.github.com/camping/camping ...because I'm starting with a vanilla OS X Leopard install (new MacBook) and - finally - Camping 1.9, and I thought it would be a good test run to go through the setup and tutorial process in the 'Camping book': http://stuff.judofyr.net/camping-docs/book/02_getting_started.html to find any gotchas. Only one (in my setup) - on 'Wrapping it up', in the Controllers: class Pages needs the explicit class Pages < R '/' to show the pages... anyone not have the same issue? Thinking about existing stuff, some time ago Magnus wrote: > As for the documentation ideas, I've already implemented the > templates in RDoc, so "rake docs" builds all the three parts (the > book is simply files in the book directory). I still need to make a > way to link book chapters from the reference, but at least it's > working. A Camping app can be useful when you want to edit it, so > you don't need to run the rake task all the time. The book dir on GitHub doesn't have all the current content found at: http://stuff.judofyr.net/camping-docs/book/ or in the Camping install (unless I'm daft, which is possible) so where can the current book files be obtained? > I guess we could also implement it as a wiki, which might be > better. Then we can't have it on camping.rubyforge.org (unless we > can change the DNS-settings) though since it only allows static > files. What do you think? I prefer having everything in files, and > I think those who really want to contribute to the book wouldn't > mind a "git clone"... I don't think there was a response at the time Magnus wrote this, so (given whywentcamping.com, which would be a separate exercise): ideas, opinions, anyone? Be really good to have camping.rubyforge.org updated, and I'm ready to pitch in, but how to start? Dave Everitt From deveritt at innotts.co.uk Mon Nov 2 03:20:16 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Mon, 2 Nov 2009 08:20:16 +0000 Subject: Using #rubycamping in Twitter posts In-Reply-To: <4962241B-F5E5-4710-BD58-B1F7F9B14FBF@creativepony.com> References: <4AEDFC51.4090104@monnet-usa.com> <4962241B-F5E5-4710-BD58-B1F7F9B14FBF@creativepony.com> Message-ID: <38BC88AA-F6D8-4046-9085-4F623045B3DB@innotts.co.uk> true, but I think Philippe is using 'rubycamping.com' as a generic term for 'the Camping website' - DaveE > I thought we settled on whywentcamping? From deveritt at innotts.co.uk Mon Nov 2 06:22:24 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Mon, 2 Nov 2009 11:22:24 +0000 Subject: Camping book Message-ID: <27A1D032-CB3F-452C-BF00-48598B589D53@innotts.co.uk> Very silly me. Forgot about 'Index': - class Pages < R '/' + class Index have corrected the Pastie: http://pastie.org/679826 Dave Everitt > Only one (in my setup) - on 'Wrapping it up', in the Controllers: > class Pages > needs the explicit > class Pages < R '/' From judofyr at gmail.com Mon Nov 2 10:13:37 2009 From: judofyr at gmail.com (Magnus Holm) Date: Mon, 2 Nov 2009 16:13:37 +0100 Subject: Camping sessions issue (and fix?) when mounting multiple apps In-Reply-To: References: <391a49da0910181331j1acc0d7cqc9c497af52228441@mail.gmail.com> Message-ID: <391a49da0911020713n65d04a93reaccb969f73ee5f1@mail.gmail.com> Okay, I think we're actually fine by setting :path => "/" by default. If you want anything different, you should use "use Rack::Session::Cookie" yourself. //Magnus Holm On Mon, Oct 19, 2009 at 19:14, Jonathan Hickford wrote: > Hi, > > I'd be inclined to agree with the middleware approach too, especially > if it's pre 2.0 release and that change can be made along side other > 1.5 -> 2.0 changes > > Jon > >> On Sun, Oct 18, 2009 at 9:31 PM, Magnus Holm wrote: >>> Wow, great catch! This is definitely a bug. I guess this should go to >>> GitHub issues, yes. >>> >>> This is actually an issue where Camping and Rack::Session::Cookie fight: >>> >>> At the first request, sessions.state is set in ::Cookie after Camping >>> has done its magic. >>> >>> At the second request, Camping loads @state from @env['rack.state'], >>> the app changes the session, but @cookie['sessions.state'] stays >>> intact. Camping's #to_a then sets the cookies again in the response: >>> >>> ? ? ?@cookies.each do |k, v| >>> ? ? ? ?v = {:value => v, :path => self / "/"} if String === v >>> ? ? ? ?r.set_cookie(k, v) >>> ? ? ?end >>> >>> Which means that it sets a sessions.state-cookie at /sessions/. Then >>> ::Cookies kicks in and figures out that the sessions have changed and >>> sets a new cookie, but this time at /. (This also has the effect that >>> Camping copies all the cookies at / into /sessions/) >>> >>> At the third request, Rack chooses cookies "such that those with more >>> specific Path attributes precede those with less specific", and the >>> cookie at /sessions/ wins. >>> >>> Your fix won't unfornately work because @root is only available inside >>> a request/controller. >>> >>> I think we need to do two things: >>> * Make sure Camping only sets cookies when they've changed. >>> * Figure out a way to set :path to SCRIPT_NAME. If so, this should >>> only be an option, as you might also want to mount two apps and have >>> them share the sessions (aka :path => '/'). >>> >>> I'm not quite sure how we should add that option, though. We could >>> switch Camping::Session to be a middleware, but this means all apps >>> will have to change "include Camping::Session" to "use >>> Camping::Session". It's maybe not such a big deal? We should at least >>> do these kind of changes *before* the release of 2.0. >>> >>> Some examples: >>> >>> # Middleware >>> use Camping::Session, :secret => "foo", :shared => true >>> >>> # Subclass >>> include Camping::Session::Shared >>> secret "foo" >>> >>> # New method >>> include Camping::Session >>> secret "foo" >>> shared_cookie! >>> >>> # Merge #secret and #shared_cookie! together >>> include Camping::Session >>> session_options :secret => "foo", :shared => true >>> >>> >>> I think I actually prefer the middleware-version. It's short and >>> concise and can be extended with more options if needed. >>> >>> What do you think? >>> >>> >>> //Magnus Holm >>> >>> >>> >>> On Sun, Oct 18, 2009 at 19:59, Jonathan Hickford >>> wrote: >>>> Hi all, >>>> >>>> Not sure where best to raise this (github issues?) but I'm seeing an >>>> issue with the cookie sessions in camping 2.0 using rack. ?If I mount >>>> an app such as the example blog or the sessions test app at any url >>>> that is not the root session information is lost in some cases. ?Same >>>> thing happens if I use the built in Camping server. >>>> >>>> For example if I mount the blog app using rackup at '/blog' I'm unable >>>> to log in. ?If I mount the sessions test app the information added on >>>> the second page is lost when it reaches page three. ?Looking at the >>>> cookies in the browser I can see two state cookies set with the paths >>>> '/' and '/blog/'. >>>> >>>> I'm guessing this is to do with Rack::Session::Cookie in session.rb, >>>> which will default to use :path => '/' in all cases. ?If I explicitly >>>> add :path => '/blog/' there it starts working as expected. ?Some more >>>> detailed outputs here (this will run from /test) >>>> http://pastebin.com/m6c13a4aa >>>> >>>> Is that me doing something crazy there (I'm not expert!) or is that a >>>> bug? ?If that's an issue I think the below change to session.rb fixes >>>> it, passing in the apps @root into the path Rack's session cookie >>>> middleware. ?I can push that somewhere if we reckon that's a fix? >>>> >>>> - app.use Rack::Session::Cookie, :key => key, :secret => secret >>>> + app.use Rack::Session::Cookie, :key => key, :secret => secret, :path => @root >>>> >>>> Regards, >>>> >>>> Jon >>>> _______________________________________________ >>>> Camping-list mailing list >>>> Camping-list at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/camping-list >>>> >>> _______________________________________________ >>> Camping-list mailing list >>> Camping-list at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/camping-list >> > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > From judofyr at gmail.com Mon Nov 2 10:52:29 2009 From: judofyr at gmail.com (Magnus Holm) Date: Mon, 2 Nov 2009 16:52:29 +0100 Subject: Camping book In-Reply-To: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> References: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> Message-ID: <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> Thanks for bringing this up again! I've pushed out what I have so far, but not your latest suggestions (you had some more in an earlier mail, right?) If you have a Github account I can give you (and anyone else who wants to contribute) push-access. I'm a little busy at the moment, but I'll try to fix it as soon as possible. //Magnus Holm On Mon, Nov 2, 2009 at 01:22, Dave Everitt wrote: > I added some basic material to the GitHub Camping Wiki (new pages): > ?http://wiki.github.com/camping/camping > > ...because I'm starting with a vanilla OS X Leopard install (new MacBook) > and - finally - Camping 1.9, and I thought it would be a good test run to go > through the setup and tutorial process in the 'Camping book': > ?http://stuff.judofyr.net/camping-docs/book/02_getting_started.html > to find any gotchas. > > Only one (in my setup) - on 'Wrapping it up', in the Controllers: > ?class Pages > needs the explicit > ?class Pages < R '/' > to show the pages... anyone not have the same issue? > > Thinking about existing stuff, some time ago Magnus wrote: > >> As for the documentation ideas, I've already implemented the templates in >> RDoc, so "rake docs" builds all the three parts (the book is simply files in >> the book directory). I still need to make a way to link book chapters from >> the reference, but at least it's working. A Camping app can be useful when >> you want to edit it, so you don't need to run the rake task all the time. > > The book dir on GitHub doesn't have all the current content found at: > ?http://stuff.judofyr.net/camping-docs/book/ > or in the Camping install (unless I'm daft, which is possible) so where can > the current book files be obtained? > >> I guess we could also implement it as a wiki, which might be better. Then >> we can't have it on camping.rubyforge.org (unless we can change the >> DNS-settings) though since it only allows static files. What do you think? I >> prefer having everything in files, and I think those who really want to >> contribute to the book wouldn't mind a "git clone"... > > > I don't think there was a response at the time Magnus wrote this, so (given > whywentcamping.com, which would be a separate exercise): ideas, opinions, > anyone? Be really good to have camping.rubyforge.org updated, and I'm ready > to pitch in, but how to start? > > Dave Everitt > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > From deveritt at innotts.co.uk Mon Nov 2 11:18:14 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Mon, 2 Nov 2009 16:18:14 +0000 Subject: Camping book In-Reply-To: <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> References: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> Message-ID: <88B9276A-88B6-4B37-A2EA-4A9CEFE88B9B@innotts.co.uk> Magnus - I did make some earlier suggestions/edits and would be happy to implement them. I'm a sad and rather newbie (still working through the O'Reilly Git book) GitHub lurker (with no repos yet: http:// github.com/DaveEveritt) so let me know when you're ready and I'll start work - Dave E. > Thanks for bringing this up again! I've pushed out what I have so > far, but not your latest suggestions (you had some more in an > earlier mail, right?) > > If you have a Github account I can give you (and anyone else who > wants to contribute) push-access. I'm a little busy at the moment, > but I'll try to fix it as soon as possible. > > //Magnus Holm > > >> On Mon, Nov 2, 2009 at 01:22, Dave Everitt >> wrote: >> I added some basic material to the GitHub Camping Wiki (new pages): >> http://wiki.github.com/camping/camping >> >> [SNIP] >> >> Thinking about existing stuff, some time ago Magnus wrote: >> >>> As for thedocumentation ideas, I've already implemented the >>> templates in RDoc, so "rake docs" builds all the three parts (the >>> book is simply files in the book directory). I still need to make >>> a way to link book chapters from the reference, but at least it's >>> working. A Camping app can be useful when you want to edit it, so >>> you don't need to run the rake task all the time. >> >> The book dir on GitHub doesn't have all the current content found at: >> http://stuff.judofyr.net/camping-docs/book/ >> or in the Camping install (unless I'm daft, which is possible) so >> where can the current book files be obtained? >> >>> I guesswe could also implement it as a wiki, which might be >>> better. Then we can't have it on camping.rubyforge.org (unless we >>> can change the DNS-settings) though since it only allows static >>> files. What do you think? I prefer having everything in files, >>> and I think those who really want to contribute to the book >>> wouldn't mind a "git clone"... >> >> >> I don't think there was a response at the time Magnus wrote this, >> so (given whywentcamping.com, which would be a separate exercise): >> ideas, opinions, anyone? Be really good to have >> camping.rubyforge.org updated, and I'm ready to pitch in, but how >> to start? >> >> Dave Everitt From dsusco at gmail.com Mon Nov 2 12:57:41 2009 From: dsusco at gmail.com (David Susco) Date: Mon, 2 Nov 2009 12:57:41 -0500 Subject: is there a way to configure line breaks in markaby output? Message-ID: <1bd79b4a0911020957s7ef7b427nd1e0b8e6b8c340bd@mail.gmail.com> Hi all, Instead of having the following: def index h1 'My Site' p 'Welcome to my site!' end output this:

My Site

Welcome to my site!

Is there anyway that I can configure Markaby to add line breaks between block elements so I'd get something like this:

My Site

Welcome to my site!

Obviously it makes no difference to the browser, it would just make it easier on me when debugging and testing. -- Dave From judofyr at gmail.com Mon Nov 2 13:16:07 2009 From: judofyr at gmail.com (Magnus Holm) Date: Mon, 2 Nov 2009 19:16:07 +0100 Subject: is there a way to configure line breaks in markaby output? In-Reply-To: <1bd79b4a0911020957s7ef7b427nd1e0b8e6b8c340bd@mail.gmail.com> References: <1bd79b4a0911020957s7ef7b427nd1e0b8e6b8c340bd@mail.gmail.com> Message-ID: <391a49da0911021016w6679eb76o21b8f17a11fcf529@mail.gmail.com> I think this should do it: Camping.goes :Nuts Nuts::Mab.set(:indent, 2) You should probably only use it in development, because I think it's pretty slow. //Magnus Holm On Mon, Nov 2, 2009 at 18:57, David Susco wrote: > Hi all, > > Instead of having the following: > > def index > ?h1 'My Site' > ?p 'Welcome to my site!' > end > > output this: > >

My Site

Welcome to my site!

> > Is there anyway that I can configure Markaby to add line breaks > between block elements so I'd get something like this: > >

My Site

> >

Welcome to my site!

> > Obviously it makes no difference to the browser, it would just make it > easier on me when debugging and testing. > > -- > Dave > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > From deveritt at innotts.co.uk Mon Nov 2 16:42:42 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Mon, 2 Nov 2009 21:42:42 +0000 Subject: is there a way to configure line breaks in markaby output? In-Reply-To: <1bd79b4a0911020957s7ef7b427nd1e0b8e6b8c340bd@mail.gmail.com> References: <1bd79b4a0911020957s7ef7b427nd1e0b8e6b8c340bd@mail.gmail.com> Message-ID: <646835CC-33AF-408F-9DA6-CC14578D5184@innotts.co.uk> Yes, it can be a bugbear. It's a bit 'non-lazy' but I just tend to add newlines with Markaby's 'text': def index h1 'My Site' text("\n\n") p 'Welcome to my site!' end - DaveE > Is there anyway that I can configure Markaby to add line breaks > between block elements so I'd get something like this: > >

My Site

> >

Welcome to my site!

From jonathan.hickford+camping at gmail.com Mon Nov 2 16:50:47 2009 From: jonathan.hickford+camping at gmail.com (Jonathan Hickford) Date: Mon, 2 Nov 2009 21:50:47 +0000 Subject: Camping sessions issue (and fix?) when mounting multiple apps In-Reply-To: <391a49da0911020713n65d04a93reaccb969f73ee5f1@mail.gmail.com> References: <391a49da0910181331j1acc0d7cqc9c497af52228441@mail.gmail.com> <391a49da0911020713n65d04a93reaccb969f73ee5f1@mail.gmail.com> Message-ID: Ace - cheers! On Mon, Nov 2, 2009 at 3:13 PM, Magnus Holm wrote: > Okay, I think we're actually fine by setting :path => "/" by default. > If you want anything different, you should use "use > Rack::Session::Cookie" yourself. > > //Magnus Holm > > > > On Mon, Oct 19, 2009 at 19:14, Jonathan Hickford > > > wrote: > > Hi, > > > > I'd be inclined to agree with the middleware approach too, especially > > if it's pre 2.0 release and that change can be made along side other > > 1.5 -> 2.0 changes > > > > Jon > > > >> On Sun, Oct 18, 2009 at 9:31 PM, Magnus Holm wrote: > >>> Wow, great catch! This is definitely a bug. I guess this should go to > >>> GitHub issues, yes. > >>> > >>> This is actually an issue where Camping and Rack::Session::Cookie > fight: > >>> > >>> At the first request, sessions.state is set in ::Cookie after Camping > >>> has done its magic. > >>> > >>> At the second request, Camping loads @state from @env['rack.state'], > >>> the app changes the session, but @cookie['sessions.state'] stays > >>> intact. Camping's #to_a then sets the cookies again in the response: > >>> > >>> @cookies.each do |k, v| > >>> v = {:value => v, :path => self / "/"} if String === v > >>> r.set_cookie(k, v) > >>> end > >>> > >>> Which means that it sets a sessions.state-cookie at /sessions/. Then > >>> ::Cookies kicks in and figures out that the sessions have changed and > >>> sets a new cookie, but this time at /. (This also has the effect that > >>> Camping copies all the cookies at / into /sessions/) > >>> > >>> At the third request, Rack chooses cookies "such that those with more > >>> specific Path attributes precede those with less specific", and the > >>> cookie at /sessions/ wins. > >>> > >>> Your fix won't unfornately work because @root is only available inside > >>> a request/controller. > >>> > >>> I think we need to do two things: > >>> * Make sure Camping only sets cookies when they've changed. > >>> * Figure out a way to set :path to SCRIPT_NAME. If so, this should > >>> only be an option, as you might also want to mount two apps and have > >>> them share the sessions (aka :path => '/'). > >>> > >>> I'm not quite sure how we should add that option, though. We could > >>> switch Camping::Session to be a middleware, but this means all apps > >>> will have to change "include Camping::Session" to "use > >>> Camping::Session". It's maybe not such a big deal? We should at least > >>> do these kind of changes *before* the release of 2.0. > >>> > >>> Some examples: > >>> > >>> # Middleware > >>> use Camping::Session, :secret => "foo", :shared => true > >>> > >>> # Subclass > >>> include Camping::Session::Shared > >>> secret "foo" > >>> > >>> # New method > >>> include Camping::Session > >>> secret "foo" > >>> shared_cookie! > >>> > >>> # Merge #secret and #shared_cookie! together > >>> include Camping::Session > >>> session_options :secret => "foo", :shared => true > >>> > >>> > >>> I think I actually prefer the middleware-version. It's short and > >>> concise and can be extended with more options if needed. > >>> > >>> What do you think? > >>> > >>> > >>> //Magnus Holm > >>> > >>> > >>> > >>> On Sun, Oct 18, 2009 at 19:59, Jonathan Hickford > >>> > > wrote: > >>>> Hi all, > >>>> > >>>> Not sure where best to raise this (github issues?) but I'm seeing an > >>>> issue with the cookie sessions in camping 2.0 using rack. If I mount > >>>> an app such as the example blog or the sessions test app at any url > >>>> that is not the root session information is lost in some cases. Same > >>>> thing happens if I use the built in Camping server. > >>>> > >>>> For example if I mount the blog app using rackup at '/blog' I'm unable > >>>> to log in. If I mount the sessions test app the information added on > >>>> the second page is lost when it reaches page three. Looking at the > >>>> cookies in the browser I can see two state cookies set with the paths > >>>> '/' and '/blog/'. > >>>> > >>>> I'm guessing this is to do with Rack::Session::Cookie in session.rb, > >>>> which will default to use :path => '/' in all cases. If I explicitly > >>>> add :path => '/blog/' there it starts working as expected. Some more > >>>> detailed outputs here (this will run from /test) > >>>> http://pastebin.com/m6c13a4aa > >>>> > >>>> Is that me doing something crazy there (I'm not expert!) or is that a > >>>> bug? If that's an issue I think the below change to session.rb fixes > >>>> it, passing in the apps @root into the path Rack's session cookie > >>>> middleware. I can push that somewhere if we reckon that's a fix? > >>>> > >>>> - app.use Rack::Session::Cookie, :key => key, :secret => secret > >>>> + app.use Rack::Session::Cookie, :key => key, :secret => secret, :path > => @root > >>>> > >>>> Regards, > >>>> > >>>> Jon > >>>> _______________________________________________ > >>>> Camping-list mailing list > >>>> Camping-list at rubyforge.org > >>>> http://rubyforge.org/mailman/listinfo/camping-list > >>>> > >>> _______________________________________________ > >>> Camping-list mailing list > >>> Camping-list at rubyforge.org > >>> http://rubyforge.org/mailman/listinfo/camping-list > >> > > _______________________________________________ > > Camping-list mailing list > > Camping-list at rubyforge.org > > http://rubyforge.org/mailman/listinfo/camping-list > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From deveritt at innotts.co.uk Tue Nov 3 07:37:47 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Tue, 3 Nov 2009 12:37:47 +0000 Subject: Camping on Wikipedia Message-ID: <69F5D550-7F7F-49A9-8779-2F26FECCC2D9@innotts.co.uk> Hi all I found the Camping page on Wikipedia in need of some serious TLC, so I updated it, added some newer links and removed the 'stub' status: http://en.wikipedia.org/wiki/Camping_%28microframework%29 I also pointed people to the Github repo for version 1.9. Please take a look and either make suggestions for further material for me to add (not too much... let's keep the text Camping-tiny :-), or make a contribution yourself. Magnus FYI: except for the introductory tutorial (http:// stuff.judofyr.net/camping-docs/book/02_getting_started.html) I refrained from adding any other links that point to your server/gem repo. Dave Everitt From deveritt at innotts.co.uk Tue Nov 3 07:59:21 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Tue, 3 Nov 2009 12:59:21 +0000 Subject: Camping on the Ruby Application Archive Message-ID: <856291CC-E09D-4D87-A4CC-283E0E2C932A@innotts.co.uk> Camping on the RAA is frozen at 1.4: http://raa.ruby-lang.org/project/ camping/ If no-one has access I could contact raa-admin at ruby-lang.org and send updated info, but (at present for the 'To install' part) that could mean sending out "source http://gems.judofyr.net" (Magnus?) - Dave Everitt From deveritt at innotts.co.uk Thu Nov 5 11:50:14 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Thu, 5 Nov 2009 16:50:14 +0000 Subject: Camping book In-Reply-To: <88B9276A-88B6-4B37-A2EA-4A9CEFE88B9B@innotts.co.uk> References: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> <88B9276A-88B6-4B37-A2EA-4A9CEFE88B9B@innotts.co.uk> Message-ID: Okay. After 3-4 intensive days I now know Git well enough to go. Today I cloned the camping repo and grepped for the issues I spotted before but it seems they're fixed. So only corrected a minor typo in README :-) Will push (with anything else I notice) when access granted - Dave E. > Magnus - I did make some earlier suggestions/edits and would be > happy to implement them. I'm a sad and rather newbie (still working > through the O'Reilly Git book) GitHub lurker (with no repos yet: > http://github.com/DaveEveritt) so let me know when you're ready and > I'll start work - Dave E. > >> Thanks for bringing this up again! I've pushed out what I have so >> far, but not your latest suggestions (you had some more in an >> earlier mail, right?) >> >> If you have a Github account I can give you (and anyone else who >> wants to contribute) push-access. I'm a little busy at the moment, >> but I'll try to fix it as soon as possible. From judofyr at gmail.com Thu Nov 5 15:15:49 2009 From: judofyr at gmail.com (Magnus Holm) Date: Thu, 5 Nov 2009 21:15:49 +0100 Subject: Camping book In-Reply-To: References: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> <88B9276A-88B6-4B37-A2EA-4A9CEFE88B9B@innotts.co.uk> Message-ID: <391a49da0911051215h3b366da6r23b716f6719a2bc9@mail.gmail.com> You're now added as a contributor. Feel free to push/commit at will, but if it involves any larger refactorings/changes, I think it's better if you fork off so we can discuss it a bit. If you're not quite sure where to push though, just push it to camping/camping. We can always revert it later if needed :-) //Magnus Holm On Thu, Nov 5, 2009 at 17:50, Dave Everitt wrote: > Okay. After 3-4 intensive days I now know Git well enough to go. Today I > cloned the camping repo and grepped for the issues I spotted before but it > seems they're fixed. So only corrected a minor typo in README :-) Will push > (with anything else I notice) when access granted - Dave E. > >> Magnus - I did make some earlier suggestions/edits and would be happy to >> implement them. I'm a sad and rather newbie (still working through the >> O'Reilly Git book) GitHub lurker (with no repos yet: >> http://github.com/DaveEveritt) so let me know when you're ready and I'll >> start work - Dave E. >> >>> Thanks for bringing this up again! I've pushed out what I have so far, >>> but not your latest suggestions (you had some more in an earlier mail, >>> right?) >>> >>> If you have a Github account I can give you (and anyone else who wants to >>> contribute) push-access. I'm a little busy at the moment, but I'll try to >>> fix it as soon as possible. > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > From judofyr at gmail.com Thu Nov 5 15:25:39 2009 From: judofyr at gmail.com (Magnus Holm) Date: Thu, 5 Nov 2009 21:25:39 +0100 Subject: Camping on the Ruby Application Archive In-Reply-To: <856291CC-E09D-4D87-A4CC-283E0E2C932A@innotts.co.uk> References: <856291CC-E09D-4D87-A4CC-283E0E2C932A@innotts.co.uk> Message-ID: <391a49da0911051225s6b6bb9dcxd79e983b7e444288@mail.gmail.com> Let's wait until 2.0 is released. If we clean up the documentation we have now, I'm totally in for releasing 2.0 as soon as possible. It would be a shame if it took more than four years to go from birth (17th, January 2006) to 2.0. This release has been delayed for way too long (sorry guys!) //Magnus Holm On Tue, Nov 3, 2009 at 13:59, Dave Everitt wrote: > Camping on the RAA is frozen at 1.4: > http://raa.ruby-lang.org/project/camping/ > > If no-one has access I could contact raa-admin at ruby-lang.org and send > updated info, but (at present for the 'To install' part) that could mean > sending out "source http://gems.judofyr.net" (Magnus?) > > - Dave Everitt > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > From ruby at monnet-usa.com Thu Nov 5 21:53:51 2009 From: ruby at monnet-usa.com (Philippe Monnet) Date: Thu, 05 Nov 2009 19:53:51 -0700 Subject: Camping on Wikipedia In-Reply-To: <69F5D550-7F7F-49A9-8779-2F26FECCC2D9@innotts.co.uk> References: <69F5D550-7F7F-49A9-8779-2F26FECCC2D9@innotts.co.uk> Message-ID: <4AF38FBF.7070101@monnet-usa.com> I also added the link to the Ruby On Rails podcast episode on Camping. Dave Everitt wrote: > Hi all > > I found the Camping page on Wikipedia in need of some serious TLC, so > I updated it, added some newer links and removed the 'stub' status: > > http://en.wikipedia.org/wiki/Camping_%28microframework%29 > > I also pointed people to the Github repo for version 1.9. > > Please take a look and either make suggestions for further material > for me to add (not too much... let's keep the text Camping-tiny :-), > or make a contribution yourself. > > Magnus FYI: except for the introductory tutorial > (http://stuff.judofyr.net/camping-docs/book/02_getting_started.html) I > refrained from adding any other links that point to your server/gem repo. > > Dave Everitt > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From deveritt at innotts.co.uk Fri Nov 6 08:36:59 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Fri, 6 Nov 2009 13:36:59 +0000 Subject: Camping book In-Reply-To: <391a49da0911051215h3b366da6r23b716f6719a2bc9@mail.gmail.com> References: <59DA14B8-70C9-4444-96D6-B36C65F7ADAD@innotts.co.uk> <391a49da0911020752p4cc44e55k16c3dd5eae37caa0@mail.gmail.com> <88B9276A-88B6-4B37-A2EA-4A9CEFE88B9B@innotts.co.uk> <391a49da0911051215h3b366da6r23b716f6719a2bc9@mail.gmail.com> Message-ID: Thanks Magnus - done. Will take care to confine changes to typos, bad links, 'getting started' etc. and fork for anything more complex (like the blog example, which is where this whole thing started for me :-) - DaveE > You're now added as a contributor. > > Feel free to push/commit at will, but if it involves any larger > refactorings/changes, I think it's better if you fork off so we can > discuss it a bit. If you're not quite sure where to push though, > just push it to camping/camping. We can always revert it later if > needed > :-) > > //Magnus Holm > > On Thu, Nov 5, 2009 at 17:50, Dave Everitt > wrote: >> Okay. After 3-4 intensive days I now know Git well enough to go. >> Today I cloned the camping repo and grepped for the issues I >> spotted before but it seems they're fixed. So only corrected a >> minor typo in README :-) Will push (with anything else I notice) >> when access granted - Dave E. From deveritt at innotts.co.uk Fri Nov 6 10:09:35 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Fri, 6 Nov 2009 15:09:35 +0000 Subject: Camping on Wikipedia In-Reply-To: <4AF38FBF.7070101@monnet-usa.com> References: <69F5D550-7F7F-49A9-8779-2F26FECCC2D9@innotts.co.uk> <4AF38FBF.7070101@monnet-usa.com> Message-ID: <7EF363C6-E7E3-49F8-98C8-9D9818CC89F3@innotts.co.uk> Hi Philippe - great! It's good to see what's out there gradually being updated - DaveE > I also added the link to the Ruby On Rails podcast episode on Camping. > > Dave Everitt wrote: >> >> Hi all >> >> I found the Camping page on Wikipedia in need of some serious TLC, >> so I updated it, added some newer links and removed the 'stub' >> status: >> >> http://en.wikipedia.org/wiki/Camping_%28microframework%29 From deveritt at innotts.co.uk Sat Nov 7 03:59:04 2009 From: deveritt at innotts.co.uk (Dave Everitt) Date: Sat, 7 Nov 2009 08:59:04 +0000 Subject: Camping on the Ruby Application Archive In-Reply-To: <391a49da0911051225s6b6bb9dcxd79e983b7e444288@mail.gmail.com> References: <856291CC-E09D-4D87-A4CC-283E0E2C932A@innotts.co.uk> <391a49da0911051225s6b6bb9dcxd79e983b7e444288@mail.gmail.com> Message-ID: Agreed about waiting until 2.0. And the ASAP. With this in mind, I've just gathered all the previous threads I can find discussing documentation, 'the book' etc. into a single text file to collate and re-post when I next have a few days. To save time looking, can anyone please point out any parts of the documentation that need cleaning up? - Dave Everitt > Let's wait until 2.0 is released. If we clean up the documentation > we have now, I'm totally in for releasing 2.0 as soon as possible > [SNIP] > > //Magnus Holm > >> Camping on the RAA is frozen at 1.4: >> http://raa.ruby-lang.org/project/camping/ >> >> [SNIP] >> >> - Dave Everitt