Todd,
Regarding the Mailer behavior/extension, I have the code at work, but
unfortunately our SVN is behind a firewall. I'll try to get it today,
but it may have to wait until Tuesday.
Sean
Todd McGrath wrote:
In my limited time here, I'm noticing many mailer behavior questions/problems.
Can we move things forward by producing a mailer extension? Sean, I think
you've mentioned writing one or I can give it shot and post it up for review.
Ruben, I think your intentions are good. Can you describe more about what you
need in:
* Print page to PDF/PS/CSV is not even completely supported by Rails.
* User roles
or point to the previous post(s) that describes it more detail?
Todd
Quoting Sean Cribbs <[EMAIL PROTECTED]>:
Ok, ok. My message wasn't entirely fair. At first I started writing a
Slashdot-ish rebuttal, but got tired of reading my own ugly words.
Still, Radiant doesn't claim to be what it's not -- don't use a wrench
to drive in nails. Too many CMSs try to be everything to everyone and
Radiant doesn't, which is why I love it.
Sean
Sean,
I love how you dismiss genuine claims. Am sure, because of posts in
this list that several other people feel the same way I do. But
whatever, it's your prerogative to keep thinking otherwise.
On 1/14/07, Sean Cribbs <[EMAIL PROTECTED]> wrote:
Flamebait. RadiantUsers wiki page. PDI. That is all.
Ruben D. Orduz wrote:
This is not intended as a flame or to cause controversy, please don't
take it as such.
I just recommended a customer to adopt Typo3 instead of Radiant CMS,
why?
* Mailer Behaviour is shaky at best.
* Print page to PDF/PS/CSV is not even completely supported by Rails.
* User roles.
Those were three of the most important things that they told me they
needed. They're a small-ish (~15 people) company and are not planning
in having huge traffic on their site or anything. However, I had to
recommend the adoption of a CMS that is probably an overkill for what
they need, but with Radiant and its extensions being in such a
"puerile" stage, it's too much risk telling them to adopt it.
The point I'm trying to drive home is that all of us that are in some
way or another involved in the development of Radiant (whether the
core, extensions, documentation, etc.) need to ramp up development of
Radiant if we really want to make it a production-grade CMS. I believe
for what I've read as of late that a whole lot of people is interested
in helping out and I sense the time is ripe for John and whoever else
leads Radiant to "manage" the momentum built up to help get this baby
out the door.
Sorry for soapboxing, but in closing I must echo the thoughts of a
list contributor who said something to the effect that if a project
stagnates for too long, it eventually fades away.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
