Todd McGrath said the following on 01/26/2007 09:18 AM:
> +1 on ordering.  

What?  only "1"?

> More about my need:
> Creating a product catalog site.  Using f:find, r:children:each throughout the
> site to produce HTML and XML pages.  Client really particular about ordering 
> of
> the Product pages.  Unfortunately, product pages cannot use existing fields 
> for
> ordering, e.g. alphabetical on any field or date.  Sure, I can add a position
> field (which I believe acts_as_list does) and update by hand to create the
> ordering they want, but this feels like a hack.  I want them to be able to
> reorder without calling me.

Same but different here.

> What I'm trying to do about it:
> I've attempted to implement patch files from ticket 199 into mental.  I've got
> it to work, but it's really slow.  Haven't had a chance to diagnose in more
> detail yet.  Also, that ticket's patch files moves administration page display
> to <ul><li> based rather than current table based, so it's really off the path
> of Mental (as I understand it).  Not too keen on moving far off the path.

I'm not keen on it either - arbitrary patches, even if I had the time to
learn Ruby, Rails.  (Not that I don't intend to, but its a matter of
priorities.  Only so much time.)  Like you, Todd, I have to deal with the
content and structure and presentation rather than the code.  That's why I'm
using  CMS.  The client baulked - rightly so - at the complexity of Joomla
and Drupal.  Rightly so.  TWiki was almost there, but its a huge footprint
and as it has bloated it has slowed down.  The content model of Radiant is
nice and clear.  The "programming" of the structure with the tags isn't
difficult.  Textile scared them at first since they'd never heard of it, but
once they say how much easier it was than HTML they were relieved.  "Its
almost like you'd write in e-mail".  Indeed.

I appreciate that Radiant is just at 0.5.x  But the reality is that a lot of
software at 2.x or 3.x still has problems.  Its ALWAYS "work in progress".
As are out client sites :-(

/a
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to