rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Magnus Holm <judofyr@gmail.com>
To: camping-list@rubyforge.org, Ruby-talk <ruby-talk@ruby-lang.org>,
	 rack-devel@googlegroups.com
Subject: [ANN] Camping 2.1 - ERB, Haml, 1.9, bug fixes, new website!
Date: Fri, 20 Aug 2010 01:25:26 +0200	[thread overview]
Message-ID: <AANLkTi=srYB_z3npwcP7k-5CkNqciLODCSuOYO8+yxtB@mail.gmail.com> (raw)

        {}
        ||
        ||
  ~~~~~~~~~~~~~~~           <=   _whycake
  ~ Camping 2.1 ~
  ~~~~~~~~~~~~~~~

I'm pleased to announce another release of Camping, the microframework. This
time we've focused on improving the 1.9 support, adding (builtin) support for
more template engines, refreshing the homepage and just general bug fixes.

  gem install camping

Home: http://camping.rubyforge.org/
Code: http://github.com/camping/camping
Bugs: http://github.com/camping/camping/issues
List: http://rubyforge.org/mailman/listinfo/camping-list

Let's have a look:

~> ERB and Haml

Camping now includes support for Tilt (http://github.com/rtomayko/tilt) which
means that you'll get simple, effortless ERB and Haml support:

  module App
    # Path to where you want to store the templates
    set :views, File.dirname(__FILE__) + '/views'
  end

  module App::Controllers
    class Index
      def get
        render :index
      end
    end
  end

Now you just need to add a views/index.haml or views/index.erb and it'll
render that instead of using Markaby. You can still use Markaby of course!

If you want to change any options for either ERB or Haml, you can use #set:

  module App
    set :haml, { :escape_html => true }
    set :erb,  { :trim => "%" }
  end

~> New homepage

Bluebie has designed an excellent new homepage for Camping:

  http://camping.rubyforge.org/

It should have links to pretty much everything you need to know about
Camping. As soon as possible we'll also try to integrate it with the GitHub
wiki and make everything more easily editable, so you can add your own links
too!

We've also started a blog at http://campingrb.tumblr.com/, where we'll keep
you up-to-date on the Camping development and community.

~> _whyday!

It's the 19th August today, so that means it's Whyday: http://whyday.org/

Camping 2.1 is our little contribution :-)

I should mention that many of these changes has been available for a *looong*
time in the source, but we felt that Whyday was a perfect occasion for
finally releasing 2.1.

I'd actually recommend to try out the experimental version if there's been a
while since the latest release. See the installation page in the wiki for
information, and subscribe to http://campingrb.tumblr.com/ to get a sneak
preview of the latest changes in Camping!

Have fun and enjoy both Whyday and Camping!

             reply	other threads:[~2010-08-19 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 23:25 Magnus Holm [this message]
2010-09-25 16:38 ` Camping 2.1 - ERB, Haml, 1.9, bug fixes, new website! trans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=srYB_z3npwcP7k-5CkNqciLODCSuOYO8+yxtB@mail.gmail.com' \
    --to=rack-devel@googlegroups.com \
    --cc=camping-list@rubyforge.org \
    --cc=ruby-talk@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).