[ANN] Radiant On Crack

Radiant on Crack is my experimental branch of the Radiant CMS project.

http://soxbox.no-ip.org/radiant/

I’ve been making experimenting with a few things that need some fairly
fundamental changes to the underlying codebase of radiant, and my
immediate needs are somewhat different to those of the core developers.
The primary goal of what I’m doing here is to make Radiant powerful
enough to run The Groggy Squirrel http://www.thegroggysquirrel.com ,
which is currently powered by a hand-rolled and very unfriendly cms-like
system.

I’m hoping to have implemented within the couple of weeks: Images,
Attachments, Comments and some other goodies.

Before you ask, this is not a political fork of the project, it’s a
practical one. I’m extending the capabilities of Radiant in ways that
are going to break things, but in ways that I need it to change. I need
to track my changes anyway, so I might as well do it publicly rather
than turn up in 2 months time with a pile of patches.

I look forward to most of my changes working their way into core in some
way, shape or form - probably with a better implementation than I can
come up with. I’m happy for others to cherry-pick changes from R.O.C.
and patch them into core, or to ask for my help to do so.


  • I Do Not Recommend Running Radiant On Crack on your live site *

I’ve given it a stupid name for a good reason. I don’t want anybody
basing their livelihood on it. I will have no qualms about ripping out
implementations and completely reworking things in a possibly backward
incompatibly manner. Unless you’re willing and able to dive into both
ruby and sql to hack it about to fix it and make it work, don’t use it.
Consider yourself warned.

Hi Daniel,

that sounds great, will be watching.

Radiant on Crack is my experimental branch of the Radiant CMS project.

http://soxbox.no-ip.org/radiant/

I’m hoping to have implemented within the couple of weeks: Images,
Attachments, Comments and some other goodies.

Yeah, these seem very important. At least images and attachments. I
can’t
use Radiant without those + a WYSIWYG editor like FCKEditor. I want to
use
it for my customers so Textile/Markdown is a nono. Once it has those
three
things I would / could use it. Maybe one of the cores can comment on if
this is acceptable to the plan?

I don’t know about comments though. Once Radiant has comments it
effectively becomes a blogging system. Maybe as a plugin?

I look forward to most of my changes working their way into core in some
way, shape or form - probably with a better implementation than I can
come up with. I’m happy for others to cherry-pick changes from R.O.C.
and patch them into core, or to ask for my help to do so.

That would be great.

-Sascha E.

Hi Sascha,

I agree with you. Right now I’m working on getting TinyMCE integrated
as Filter option. Once I have it working I’ll see what I can do about
packaging it up as a plugin of some sorts.

Chris-

On Jun 28, 2006, at 12:22 AM, Sascha E. wrote:

Attachments, Comments and some other goodies.

-Sascha E.


Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant

Chris Corriveau: CTO of Genevate - P.O. Box 1829, North Falmouth, MA
02556
contact | [email protected] - 508.564.5676 ext. 202 | toll free -
866.GENEVATE
Visit: GenevateStore sell your products online, it’s quick and easy.

I don’t know about comments though. Once Radiant has comments it
effectively becomes a blogging system. Maybe as a plugin?

It’s more about the capability of comments than comments themselves. I’m
implementing it as a demonstration of the capabilities opened up to
behaviors by what I’m doing - the other ways in which I’m wanting pages
to interact with extra tables are probably going to remain tucked away.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs