Right... I totally understand that, and I feel your pain. Maybe what we should have said was PDI (Please Do Investigate), There are a lot of things that we just can't do in a general way to be used by everyone. The best way is to do it yourself, then extract -- just the way Rails was developed.
Sean On 5/20/07, Adam Williams <[EMAIL PROTECTED]> wrote: > On May 20, 2007, at 3:34 PM, Mario T. Lanza wrote: > > > Yes, Radiant is a CMS for static sites and that's what I'm using it > > for. > > However, if any one thing met my every need that'd be fortuitous. In > > the end, Radiant meets 90% of my need. Yet, there remains that 10% > > unmet need that I simply cannot abandon. So do I chuck Radiant simply > > because it only gets me 90% of the way? I don't think so. I just > > start > > brainstorming for ways to squeeze out the 10%, if not from Radiant, > > then > > from Rails. > > Mario, all of this was well said. I particularly empathize with the > above. > > aiwilliams > > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
