Jenna Fox | 1 Oct 02:37 2011

Since we're talking about couch

Here's mine: https://github.com/Bluebie/chill

Fairly short and simple, like couchdb.

Jenna

_______________________________________________
Camping-list mailing list
Camping-list@...
http://rubyforge.org/mailman/listinfo/camping-list
Daniel Bryan | 1 Oct 03:45 2011
Picon

Re: Since we're talking about couch

i like it

your library is nice n' neat

On Saturday, 1 October 2011 at 10:37 AM, Jenna Fox wrote:

Here's mine: https://github.com/Bluebie/chill

Fairly short and simple, like couchdb.

Jenna

_______________________________________________
Camping-list mailing list
Camping-list <at> rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list

_______________________________________________
Camping-list mailing list
Camping-list@...
http://rubyforge.org/mailman/listinfo/camping-list
Magnus Holm | 2 Oct 13:19 2011
Picon

Re: Feature: Simple controllers?

2011/9/24 Bartosz Dziewoński <matma.rex <at> gmail.com>:
> So, are we reverting it? It's still in the latest GitHub commit.

I've reverted it.
_______________________________________________
Camping-list mailing list
Camping-list <at> rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Magnus Holm | 2 Oct 13:43 2011
Picon

Maintenance release of 2.1

I'm thinking of releasing 2.1.458 which includes a few more features
(better cookie support, inline templates etc), but mainly to fix some
incompatibility issues with Rack. I'm not going to document the new
features yet, so consider them experimental in this patch-release.

As for the version, it's currently MAJOR.MINOR.REV where REV = number
of commits since the beginning. It works pretty well to use REV as a
part of the version number because I can then easily throw out
experimental releases to my gem server without screwing up the version
number. However, from 2.2 I'm thinking of changing REV to "number of
commits since previous release", simply to avoid some high revision
numbers.

Thoughts? Okay with a little maintenance release? Okay with some
undocumented experimental features? Okay with REV? Okay with
decreasing REV a bit=

// Magnus Holm
Magnus Holm | 2 Oct 13:28 2011
Picon

Re: Feature: Inline templates?

2011/9/24 Bartosz Dziewoński <matma.rex <at> gmail.com>:
> A comment after some time: I'd appreciate it more if I could just have
> one "external" file with all the templates, and one with the Camping
> code, and I could "link in" the templates to parse using this
> mechanism.

This works, although it's kinda hacky:
  eval('Camping.goes :Foo', nil, 'templates.rb')

On Fri, Aug 26, 2011 at 16:14, Dave Everitt <deveritt <at> innotts.co.uk> wrote:
> Since no-one has replied, for what it's worth (as a very amateur camper),
> I've always been happy with simple regular Markaby views and the v2.1
> options for external templates. Also, my modest one-file apps have their CSS
> after __END__. In any sizeable app, you'd probably want to have separate
> templates for easier maintenance (since - if inline - their code is going to
> add more than a few lines and break the one-file advantages), so the
> question is: will anyone use/want inline templates? - DaveE

I've committed another patch (8b6fee67). Now you can serve static "files" too:

  __END__
   <at>  <at>  /style.css
  * { margin: 0; padding: 0; }

It also sets the correct MIME type.

The only thing I worry about now is that it's taken a lot of bytes.
We're currently at 3976 (97%) bytes.
_______________________________________________
Camping-list mailing list
Camping-list <at> rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Jenna Fox | 2 Oct 14:26 2011

Re: Maintenance release of 2.1

I wouldn't bother with reducing the revision number. If anything
having weirdly high ones makes the project seem more alive and active.
Is the minor number even functionally useful here? Maybe we should
ditch that and just keep major as a "look! An increment! Heaps cool
stuff must have happened!" unless google chrome has ruined new major
numbers for everyone anyway.

—
Jenna

On 02/10/2011, at 10:43 PM, Magnus Holm <judofyr@...> wrote:

> I'm thinking of releasing 2.1.458 which includes a few more features
> (better cookie support, inline templates etc), but mainly to fix some
> incompatibility issues with Rack. I'm not going to document the new
> features yet, so consider them experimental in this patch-release.
>
> As for the version, it's currently MAJOR.MINOR.REV where REV = number
> of commits since the beginning. It works pretty well to use REV as a
> part of the version number because I can then easily throw out
> experimental releases to my gem server without screwing up the version
> number. However, from 2.2 I'm thinking of changing REV to "number of
> commits since previous release", simply to avoid some high revision
> numbers.
>
> Thoughts? Okay with a little maintenance release? Okay with some
> undocumented experimental features? Okay with REV? Okay with
> decreasing REV a bit=
>
> // Magnus Holm
> _______________________________________________
> Camping-list mailing list
> Camping-list@...
> http://rubyforge.org/mailman/listinfo/camping-list
Paul van Tilburg | 2 Oct 21:06 2011
Picon

Re: failing test

On Sat, Sep 24, 2011 at 11:01:42PM +0200, Magnus Holm wrote:
> Pretty sure this is related to incompatability with the latest Rack
> (which suddenly slightly "broke" the Session-API). It's fixed in
> latest master. Maybe we should just do a release soon.

Alright.  I will follow with packaging once that is out.  I already
suspected the interplay with Rack.

Cheers!
Paul

--

-- 
PhD Student  <at>  Eindhoven                     | email: paul@...
University of Technology, The Netherlands   | JID: paul@...
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
Magnus Holm | 3 Oct 11:47 2011
Picon

Re: Maintenance release of 2.1

On Sun, Oct 2, 2011 at 14:26, Jenna Fox <a <at> creativepony.com> wrote:
> I wouldn't bother with reducing the revision number. If anything
> having weirdly high ones makes the project seem more alive and active.
> Is the minor number even functionally useful here? Maybe we should
> ditch that and just keep major as a "look! An increment! Heaps cool
> stuff must have happened!" unless google chrome has ruined new major
> numbers for everyone anyway.

Well, it's useful for computability reasons. Every app created on 2.x
should work on 2.x+n with minimal required changes.
Jenna Fox | 3 Oct 12:29 2011

Re: Maintenance release of 2.1

True that.

Meanwhile, have you guys seen <http://twitter.github.com/bootstrap/> ? It looks pretty nice, and I imagine something like that could be pretty powerful if deeply integrated with a version of markaby, as a 'ui toolkit for the web' sort of thing - a nice sensible clean default style for quickly prototyping ideas, and teaching beginners the concepts of the web.

Jenna

On 03/10/2011, at 8:47 PM, Magnus Holm wrote:

On Sun, Oct 2, 2011 at 14:26, Jenna Fox <a <at> creativepony.com> wrote:
I wouldn't bother with reducing the revision number. If anything
having weirdly high ones makes the project seem more alive and active.
Is the minor number even functionally useful here? Maybe we should
ditch that and just keep major as a "look! An increment! Heaps cool
stuff must have happened!" unless google chrome has ruined new major
numbers for everyone anyway.

Well, it's useful for computability reasons. Every app created on 2.x
should work on 2.x+n with minimal required changes.
_______________________________________________
Camping-list mailing list
Camping-list-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/camping-list

_______________________________________________
Camping-list mailing list
Camping-list@...
http://rubyforge.org/mailman/listinfo/camping-list
Bartosz Dziewoński | 3 Oct 17:31 2011
Picon

Re: Maintenance release of 2.1

Personally I hate it. It's like <table border=2> and <font size=7>
once again, except this time camouflaged as CSS classes. The only good
things in there are either styled pretty much the same way by default
(like, say, headers), or require a line of code ( <at> basefont, layouts).

-- Matma Rex

2011/10/3 Jenna Fox <a <at> creativepony.com>:
> Meanwhile, have you guys seen <http://twitter.github.com/bootstrap/> ? It
> looks pretty nice, and I imagine something like that could be pretty
> powerful if deeply integrated with a version of markaby, as a 'ui toolkit
> for the web' sort of thing - a nice sensible clean default style for quickly
> prototyping ideas, and teaching beginners the concepts of the web.
>

Gmane