On 12/06/07 05:01 PM, www-data was heard to say: > Do you have a public svn for your blog source?
The code base of the blog is what is in the Shiny SVN (http://hytek.org/shiny/svn/shiny/trunk/). The relevant Radius code is the same as for any stock Radiant version and the additions are straight forward. > What's your eventual direction for Shiny? Could this eventually be made > to be an extension of Radiant? I don't want to interfere too much with the Radiant development, though I am still optimistic that some of the ideas will eventually make it into Radiant. A problem with that is that I am a slacker and too lazy to write proper unit tests. At the moment I don't consider Shiny as a fork but more as a branch of Radiant. However, I am also not planning to turn Shiny into an extension for Radiant. At least not at the moment. Radiant development is not very fast, such that I can keep up with merging changes into Shiny. I have thought before about turning it into an extension, but it goes fairly deep into the internals of Radiant, such that an extension would in fact turn around most of the Radiant code and change Radiant's default database schema. This, I think, would not be a good idea. Alternatively, it could be turned into an extension parallel to Radiant's default content model. That way it would setup it's own tables etc. and attempt to disable Radiant's page implementation. > When I started looking for Rails CMSs, I was hoping to find something > like Drupal. Maybe your CMS will help bridge the gap. Maybe, though I get the shivers hearing that (for various reasons). Cheers, Oliver
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
