Re: framework size, forking etc.

2012-04-25 Thread Anthony Durity
Hi, The reason I got into camping was because it was written by _why , because liked the way _why looked at things and approached things. Camping contains the spirit of _why , if you alter it too much it ceases to be Camping. Part of the attraction is the tiny size, the 3k/4k limit or whatever it

Re: framework size, forking etc.

2012-04-18 Thread Daniel Bryan
Thought I'd weigh in for what it's worth, My naive first impression of Camping basically took no notice of the whole 3/4k thing. I appreciate that it's a cool programming feat, and I love the attitude that lead to it, but at the time my focus was on trying to figure out what all these hidden

Re: framework size, forking etc.

2012-04-18 Thread Dave Everitt
Daniel - that's a great reply and echoes much of my own experience (although my Camping is much more on the tinkering side). The point about Camping being an educational tool is a good one, which I've even tried to apply to students (unsuccessfully - but that's my problem), and it would be

Re: framework size, forking etc.

2012-04-18 Thread Magnus Holm
On Wed, Apr 18, 2012 at 15:07, Daniel Bryan danbr...@gmail.com wrote: Thought I'd weigh in for what it's worth, Thanks, I find it very interesting. My naive first impression of Camping basically took no notice of the whole 3/4k thing. I appreciate that it's a cool programming feat, and I love

Re: framework size, forking etc.

2012-04-18 Thread Jenna Fox
I think the trouble with streaming over the rack interface is that it's confusing. I'm fairly good at ruby, but I'm not entirely sure how it would even work. I guess I need to run my app in a threaded web server, running every request in it's own thread? Then inside the each iterator in the

Re: framework size, forking etc.

2012-04-18 Thread Dave Everitt
Not to forget Perl (who would have thought that?) which currently has the best web framework I've ever seen: http://mojolicio.us/ I would have thought it - my sometimes co-developer opened my eyes to Titanium: http://mark.stosberg.com/blog/2008/12/titanium-a-new-release-and-more.html and

Re: framework size, forking etc.

2012-04-18 Thread Magnus Holm
On Wed, Apr 18, 2012 at 17:49, Jenna Fox a...@creativepony.com wrote: I think the trouble with streaming over the rack interface is that it's confusing. I'm fairly good at ruby, but I'm not entirely sure how it would even work. I guess I need to run my app in a threaded web server, running

Re: framework size, forking etc.

2012-04-17 Thread Isak Andersson
To be honest I don't care if we leave the 4k stuff behind or not. I just want Camping to be easy to extend and customize. Don't get me wrong, Camping is crazy customizable. The fact that you can set it up to be a huge application with the rackup file in an extremely cool way is definitely

Re: framework size, forking etc.

2012-04-17 Thread Dave Everitt
If you want to use something like SASS for CSS, there are gems for that (or use LESS), but I'd never expect such functionality to be built into in Camping - that's one of the things I *like* about it: a small functional default set that works, with options for other ways left to me. BTW

Re: framework size, forking etc.

2012-04-17 Thread Dave Everitt
+1 to all that David Costa wrote in response. Magnus *has and does* kept things solid and on track in a way that suits Camping. We're never going to go head-to-head in the framework competition stakes (bit late for that anyway, with frameworks swerving all over client- side dev). As for

Re: framework size, forking etc.

2012-04-17 Thread Isak Andersson
I thought about that, but I want to stay up to date with things like Mab and all that. There are small differences. But I guess I could omit the use of anything that differs. But still, we want the information to be fresh, no? Cheers! Isak Andersson david costa gurugeek...@gmail.com skrev:

Re: framework size, forking etc.

2012-04-17 Thread david costa
Well Sqlite works fine with the current camping so I don't see any reason to use something not yet released for the screencasts. so in short use the official camping-omnibus for the screencasts. I checked your issue on github but I don't think is the fault of the new version but that's not the

Re: framework size, forking etc.

2012-04-17 Thread Isak Andersson
Yeah I was going to suggest that we do a screencasts going over New features. Let's go with that instead! Cheers! Isak Andersson david costa gurugeek...@gmail.com skrev: Well Sqlite works fine with the current camping so I don't see any reason to use something not yet released for the

Re: framework size, forking etc.

2012-04-17 Thread Jenna Fox
Those are all great points - the eventstream support is a particular sticking point to me. It feels like a standard which aught to be easily implemented - even through rack! but I've yet to see any web frameworks where eventstream doesn't seem like a total hack - except perhaps for Node.JS

Re: framework size, forking etc.

2012-04-16 Thread Dave Everitt
I'm not too bothered about 3k. But I think what Nokan's saying is that he'd like Camping to remain functioning as it is so he can continue to run his apps as they're set up now, but that extra features could be added with an optional `require 'camping/new_extra_stuff`... - Nokan, is this

Re: framework size, forking etc.

2012-04-16 Thread Nokan Emiro
On Mon, Apr 16, 2012 at 5:40 PM, Dave Everitt dever...@innotts.co.ukwrote: I'm not too bothered about 3k. But I think what Nokan's saying is that he'd like Camping to remain functioning as it is so he can continue to run his apps as they're set up now, but that extra features could be added

Re: framework size, forking etc.

2012-04-16 Thread Nokan Emiro
I would leave the name camping for the original gem, and would choose another one for the fork. But exactly what are those features that you (all) would like to add to camping? - before/after methods of controllers, - something around serving static files and R(), - ??? Actually I think it's

Re: framework size, forking etc.

2012-04-16 Thread Bartosz Dziewoński
W dniu 16 kwietnia 2012 20:50 użytkownik Nokan Emiro uzleep...@gmail.com napisał: Actually I think it's not logical that you can build HTML by default using Markaby, but you can't build CSS in the same way. You never need to insert any variables into your CSS code. (If you do, you're doing it

Re: framework size, forking etc.

2012-04-16 Thread Paul van Tilburg
On Mon, Apr 16, 2012 at 09:20:18PM +0200, Bartosz Dziewoński wrote: W dniu 16 kwietnia 2012 20:50 użytkownik Nokan Emiro uzleep...@gmail.com napisał: Actually I think it's not logical that you can build HTML by default using Markaby, but you can't build CSS in the same way. You never need

Re: framework size, forking etc.

2012-04-16 Thread Magnus Holm
On Mon, Apr 16, 2012 at 22:14, Nokan Emiro uzleep...@gmail.com wrote: 2012/4/16 Bartosz Dziewoński matma@gmail.com W dniu 16 kwietnia 2012 20:50 użytkownik Nokan Emiro uzleep...@gmail.com napisał: Actually I think it's not logical that you can build HTML by default using Markaby, but

Re: framework size, forking etc.

2012-04-16 Thread Nokan Emiro
Shit! If you told me about it a few hours ago, I wouldn't bother myself writing a RobotsTxt Controller... __END__ @@ /style.css * { margin: 0; padding: 0 } And Camping will serve it for you. See also: https://github.com/camping/camping/blob/master/test/app_file.rb

Re: framework size, forking etc.

2012-04-16 Thread david costa
For now I'm feeling like a pretty bad maintainer. I'm not using Camping enough to see where things need to be fixed, I'm crappy at actually shipping stuff, and I'm not sure if I believe that Camping is a correct starting point for a new framework Hey Magnus! I think that you are a great

Re: framework size, forking etc.

2012-04-14 Thread david costa
Hi all :) I have been playing with Sinatra a lot lately and perhaps *some* things are done easily there (URL mapping, static files) but being a DSL and not a framework it is a bit different. For many things camping does the job very well and overall I find it a more comprehensive solution than