Re: Rack, Camping 2.0++
I don't want to be the leader. I just want to contribute to one of the sweetest framework that exists in the Rubyverse! I'm going to contribute with what I can, and I suck at writing documentation and I have no intention to learn RDoc (ATM, maybe another day). (I still think that _why is the true leader of Camping.) On Sat, May 24, 2008 at 1:28 AM, zimbatm [EMAIL PROTECTED] wrote: 2008/5/23 Magnus Holm [EMAIL PROTECTED]: So should I just merge/rebase everything to my master, so _why can merge it into his? Some more notes: * camping/db.rb - camping/ar.rb * camping/session.rb - camping/ar/session.rb * CookieSession - camping/session.rb The documentation and the names (Camping::Session, Camping::ARSession?) needs some fixing. I'll let the leader decide :-) You are the leader now :) If I where you, I'd take some time checking the documentation generates well. Last time I checked, it was a mess. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
If you can point to areas to document or changes you are making that need documentation, I'd be happy to write it for you. --Jeremy On Sat, May 24, 2008 at 12:51 PM, Magnus Holm [EMAIL PROTECTED] wrote: I don't want to be the leader. I just want to contribute to one of the sweetest framework that exists in the Rubyverse! I'm going to contribute with what I can, and I suck at writing documentation and I have no intention to learn RDoc (ATM, maybe another day). (I still think that _why is the true leader of Camping.) On Sat, May 24, 2008 at 1:28 AM, zimbatm [EMAIL PROTECTED] wrote: 2008/5/23 Magnus Holm [EMAIL PROTECTED]: So should I just merge/rebase everything to my master, so _why can merge it into his? Some more notes: * camping/db.rb - camping/ar.rb * camping/session.rb - camping/ar/session.rb * CookieSession - camping/session.rb The documentation and the names (Camping::Session, Camping::ARSession?) needs some fixing. I'll let the leader decide :-) You are the leader now :) If I where you, I'd take some time checking the documentation generates well. Last time I checked, it was a mess. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- http://jeremymcanally.com/ http://entp.com Read my books: Ruby in Practice (http://manning.com/mcanally/) My free Ruby e-book (http://humblelittlerubybook.com/) Or, my blogs: http://mrneighborly.com http://rubyinpractice.com ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: obfuscation Re: Rack, Camping 2.0++
The problem is that almost all app require 'camping' and when bin/camping require 'camping-unabridged' things gets pretty messy. Right, didn't thought about that.. well then we have to come up with a Ruby2Ruby version, isn't it ? ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: obfuscation Re: Rack, Camping 2.0++
How is camping.rb created from camping-unabridged.rb? By hand? Err.. yes. This is a kind of art you know ? ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
So should I just merge/rebase everything to my master, so _why can merge it into his? Some more notes: * camping/db.rb - camping/ar.rb * camping/session.rb - camping/ar/session.rb * CookieSession - camping/session.rb The documentation and the names (Camping::Session, Camping::ARSession?) needs some fixing. I'll let the leader decide :-) On Fri, May 23, 2008 at 11:18 PM, zimbatm [EMAIL PROTECTED] wrote: 2008/5/22 _why [EMAIL PROTECTED]: Splendid! If we can say Camping, the 3K Microframework, then I think we will really have a reason to bump the big number. I'll wait for a reaction from zimbatm, but I am euphoric about these changes. Wasn't the one who codes who leads ? :) ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
2008/5/23 Magnus Holm [EMAIL PROTECTED]: So should I just merge/rebase everything to my master, so _why can merge it into his? Some more notes: * camping/db.rb - camping/ar.rb * camping/session.rb - camping/ar/session.rb * CookieSession - camping/session.rb The documentation and the names (Camping::Session, Camping::ARSession?) needs some fixing. I'll let the leader decide :-) You are the leader now :) If I where you, I'd take some time checking the documentation generates well. Last time I checked, it was a mess. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
Camping.goes :Forward ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
On Fri, May 23, 2008 at 07:27:18AM +1930, Aníbal Rojas wrote: === 4. Renaming camping-unabridged.rb to camping.rb? === I haven't touched camping.rb at all, do we really need to prove that it's a micro-framework? It just makes development/releasing harder. Let's just forget about the abridged version and rename camping-unabridged.rb to camping.rb! Keeping Camping away from the bloat goes far beyond an arbitrary weight limit. It is a nice way to promote Camping. It is catchy saying In Less then 4K, period. Instead of saying the obfuscation just makes development/releasing harder, try saying obfuscation just makes flippancy/esotericism easier. _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Rack, Camping 2.0++
On May 22, 2008, at 12:38 AM, _why wrote: On Wed, May 21, 2008 at 09:26:52PM +0200, Magnus Holm wrote: I've just finished rewriting Camping to use Rack in the core. I got rid of (a little less) than 1kB in camping.rb and removed lots of un- necessary files (lib/server/*.rb, fastcgi.rb mongrel.rb). Splendid! If we can say Camping, the 3K Microframework, then I think we will really have a reason to bump the big number. I'll wait for a reaction from zimbatm, but I am euphoric about these changes. Oh, that's wonderful! I really like it! Aria Stewart [EMAIL PROTECTED] ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
obfuscation Re: Rack, Camping 2.0++
Hi Magnus, On May 22, 2008, at 11:01 AM, Magnus Holm wrote: I must agree that the obfuscation is really impressive (specially in a presentation where you can include the full source on one slide). I just don't like to touch it. And unfortunately it doesn't evolve by itself. I'm just tired of renaming camping-unabridged.rb to camping.rb in order to test the apps, and then back again when I commit stuff. I'll be perfectly fine if someone else creates the obfuscated version :-) So, it sounds like there's a few options: a) Automate the creation of the obfuscated version from the unabridged version b) Tweak the system to run from camping-unabridged.rb (or a short name thereof, e.g. campsrc) c) Make the obfusc version camping4k, and make camping-unabridged.rb the default camping.rb Any of those seem viable? -- Ernie P. On Thu, May 22, 2008 at 5:50 PM, _why [EMAIL PROTECTED] wrote: On Fri, May 23, 2008 at 07:27:18AM +1930, Aníbal Rojas wrote: === 4. Renaming camping-unabridged.rb to camping.rb? === I haven't touched camping.rb at all, do we really need to prove that it's a micro-framework? It just makes development/releasing harder. Let's just forget about the abridged version and rename camping-unabridged.rb to camping.rb! Keeping Camping away from the bloat goes far beyond an arbitrary weight limit. It is a nice way to promote Camping. It is catchy saying In Less then 4K, period. Instead of saying the obfuscation just makes development/releasing harder, try saying obfuscation just makes flippancy/esotericism easier. _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
