For me, this also depends on what Magnus - as the main Camper ninja -
thinks - DaveE
I agree, I'd like to see the way Camping works to grow in to
something much more usable. Perhaps a fork is a good idea because
the legacy would remain and all. But then in the fork we could deal
with things that might be kind of annoying at times. And grow it
with a steady pace.
If we'd fork camping I think we should still stay as minimalistic as
possible. Only adding the best things. And work on making it easy to
extend.
Cheers!
Isak Andersson
Dave Everitt <dever...@innotts.co.uk> skrev:
There's a crucial point here... if 3k (the old 4k) is a 'proof of
concept' and a great exercise in programming skill, it isn't
something that most users will really worry about. If the 3k limit
has to be broken back up to 4 or even 5k to get some added/altered/
optional functionality that would help usability for the rest of us,
it's not an issue for me - DaveE
3kb is great and all, but it seems kind of dishonest if the
framework isn't even really usable without a bunch of other gems
and files and stuff. The conflict between 3/4kb and having robust
well designed features often seems to haunt this project. Maybe
time for a forking? I have next to no interest in 3kb as a real
feature.
_______________________________________________
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
