rubyonrailsin

A Ruby and Rails talk

Thursday, March 18, 2010


Re: [Radiant-Dev] Old Extensions and Tabs

by rubyonrailsin 0 comments

Tag


Share this post:
Design Float
StumbleUpon
Reddit

it would suggest to the possibly lazier extension developers that all they need to do is update their tabs and call it a day

Hence my suggestion to mark it as deprecated.

On Mar 18, 2010, at 12:58 PM, Alex Wallace wrote:

Apologies for my gmail-lagged empty message prior to this one.

I don't think an "old" menu is a good move - it would suggest to the possibly lazier extension developers that all they need to do is update their tabs and call it a day. Seems like it would open the door for a lot of 0.8 extensions masquerading as 0.9 compatible. An "old/deprecated" menu would definitely have some code smell.

On Thu, Mar 18, 2010 at 12:56 PM, Alex Wallace <alexmlwallace@gmail.com> wrote:


On Thu, Mar 18, 2010 at 12:39 PM, Josh French <josh@digitalpulp.com> wrote:
If the only difference between 0.8-compatible extensions and 0.9-compatible extensions were the Tab API, I'd agree with you. But as it stands, Radiant 0.8 -> 0.9 isn't a simple drop-in update for most extensions. So if updating extensions has to happen anyway, I think the intent here is to prod developers to adopt the new tab categories along the way.

On Mar 18, 2010, at 12:22 PM, Mislav Marohnić wrote:

On Thu, Mar 18, 2010 at 03:21, John W. Long <me@johnwlong.com> wrote:

I'd like to suggest that extensions
the old tab API get added to an "Old" top-level tab that would appear
only when the old API is invoked.

That won't do much to encourage extension authors to update their extensions, but will certainly keep Radiant users from updating to 0.9.

I mean, a new tab named "Old" or "Legacy"? How to explain that to people who are merely using Radiant for managing content? I'd rather stick to 0.8 than have to explain my users why is some important stuff now under a strangely-named tab.

--
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/

No comments:

Post a Comment

Subscribe feeds via e-mail

Blog Archive