Josh French -- please fill us in on what you and your group did on
Saturday; I missed a lot of that.
Andrew O'Brien, Mike Hale, Luke whose last name I am blanking on
(apologies), and myself started work on extending the page class to
accept arbitrary attributes -- booleans, integers,
Sean Cribbs said the following on 10/28/2008 12:53 AM:
[...]. Many bugs were squashed and edge cases discovered
thanks to them, including an esoteric bug involving an extension that
only gets loaded in test mode. We'll be reducing the number of
controller unit/functional specs and relying
This is a brilliant idea. I know because I thought of it first ;). In
our J2EE application we have a similar concept where any page can have
an arbitrary collection of named attributes and we have code that can
work with that code. We have a Tag Library that will write out a value
of a
On Tue, Oct 28, 2008 at 3:46 PM, Adam van den Hoven
[EMAIL PROTECTED] wrote:
The benefit is being able to sparsely populate data. Where the content
author is the person doing the technical admin, its not an issue. but if you
have many non-technical authors (a good reason for using a CMS)
Thanks for the poke, Nate. Working on a blog post...
Sean
Nate Turnage wrote:
Is everybody still asleep after the long weekend? I am dying to hear how
things went with the sprint. Sean? John? Anyone?
~Nate
___
Radiant mailing list
Post:
On Oct 27, 2008, at 8:59 PM, Nate Turnage wrote:
Is everybody still asleep after the long weekend? I am dying to hear
how
things went with the sprint. Sean? John? Anyone?
It was a great weekend Nate. Sean headed up the work on the code and I
worked with people who were interested in
Since John passed the ball to me, it'll probably be easier to write an
email first than a blog post.
The primary goal I had for this weekend was to make headway on a
refactoring of the admin interface toward a conventional RESTful
design. These changes will be rolled into the 0.6.10 release
