rubyonrailsin

I am not sure that we need a standard for all of those items.

I was leaning more towards a way to define the assumptions that the theme makes about the existence of such items. (Determining this without an explicit declaration would be even better.) Then when a theme is selected by a user, have the extension create any items that are required but missing, and then warning the user if existing assets are not going to be utilized. The warnings are probably best communicated by copy just above the editor for each affected item as well as a different icon in the list.

-----Original Message-----
From: "John Long" <johnwlong2000@gmail.com>
Sent: Thursday, March 11, 2010 9:35am
To: radiantcms-dev@googlegroups.com
Subject: Re: [Radiant-Dev] Solving the Radiant theme and template problem

On Thu, Mar 11, 2010 at 8:08 AM, rubybox <voorruby@gmail.com> wrote:
> So what Im interested in is any experienced developer interested in
> this? Am I the only one so frustrated by this, or can we get together and
> create a working extension for this?

I talked to Chris Rankin yesterday about his Site Theme yesterday
discussed some modifications to his extension that would make it more
flexible in the way that you describe.

http://ext.radiantcms.org/extensions/207-site-theme

To me there are two major areas of improvement needed:

1. Making destruction of layouts, pages, and snippets optional

2. Creating a standard template specification that templates can
conform to (or not) at the author's discretion

The idea behind a standard template specification is that the names of
pages, page parts, snippets, and layouts should be consistent across
most templates. This would allow a high degree of reusability and make
theming much more flexible.

Chris was excited about both ideas but could probably use some help
with the implementation. Also I think it would be good to get a
consensus from the community on what the standard template
specification should be.

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/