Re: [Radiant] Radiant Browser Support -- Drop IE6?
On Sat, 2008-07-19 at 20:35 -0600, Marty Haught wrote: I vote we drop IE6 for the admin side. I agree with the hatred for IE, but I for one promise my clients to support the current version of a browser and one version previous. Currently, that means IE 6 and 7. In many corporate environments IE 6 is still the only browser allowed in the office. I know it's asinine, but it's true. While I certainly don't want to try and mandate which versions of browsers that an open source project supports, I would like to suggest that IE 6 not be dropped until version 8 is official. If you do kill support for IE 6 could you please make an entry in the wiki describing some of problems you were having with IE and mention where/how it might be a problem even if you don't make the fix. That way those of use that still need to support v6 can do so without any further involvement from the core group. Of course that's just my $0.02. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] phusion passenger error
When you get that 'x.rb was expected to define X' error, it usually means one of three things: * There's a syntax error in the file * One of the dependent libraries that the file requires is missing * The original file is missing (least likely) My guess is that you have an incomplete version of the sources. It looks like you are trying to install Radiant in application mode. While this is ok, it's recommended that you install it in project mode -- this is where you install the Radiant gem, run the `radiant` command from the terminal, and then either use the gem for the Radiant source (i.e. do nothing extra), or use `rake radiant:freeze:edge` and put the source in vendor/radiant. Sean Aleks Clark wrote: I've got a passenger host that works fine with other rails apps (see: http://built-it.net and sstracker.built-it.net for functional apps), but barfs on radiant. another fun thing is that the radiant app only fails with passenger! mongrel and webrick work fine! You can check out the error page at http://ssresource.built-it.net/ /home/sweeper/www/ssresource.built-it.net/app/models/standard_tags.rbexists, and is readable, and contains the definition of the StandardTags module. I have tried this with a fresh svn checkout of 0.6.7 as well as a fresh checkout of trunk (in addition to the already developed app, which includes some extensions), and all produce identical results. any ideas? thanks, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Settings Extension for easy access to configuration
Jim Gay wrote: We don't have plans to try to takeover this extension since Alex is doing a great job with it. Our fork provides the ability to add your own settings because we have at least one server where ruby-inline is not installed so we can't do script/console and having the ability to add new settings was crucial for setting up 'dev.host' I don't recall any SettingsExtension.root problem, so it may just be a fluke that it works in our fork. For the most part, we only forked to help with improving it and writing specs, so keep your eye on the Squeegy repository. -Jim Thanks for the contributions guys. After a busy few weeks I am back on this stuff. All code has been rolled in and updated. Great work. Being part of this small yet productive radiant communinty is a pretty damn cool thing. Thanks guys! -Alex http://beautifulpixel.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Styles n Scripts feature request
On Jul 15, 2008, at 12:28 PM, Tim Gossett wrote: That said, I think I like Sass much more than both Haml and regular CSS (I still haven't used it enough to have a firm conclusion). It's much simpler than Haml and doesn't have to handle things like running ruby in the middle of your template. And it encourages some very good CSS behaviors. Worth trying for sure. Here, here. SASS actually provides more control than plain old CSS. Here's something I did with SASS when on a golden-ratio trip: SASS really is better than regular CSS in absolutely every way. Really. You don't give up any control at all, and you gain so much. The constants and math stuff is just icing on the cake. The real meat is the nesting of selectors. This is how CSS should have worked. Once you get used to SASS, there is no possible way you can tolerate working with plain CSS for any large layout job ever again. SASS for president! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Setting r:title from a custom extension
Hi everyone. I have been using Radiant for a while, and have finally made an extension for a customer, but I have question for you all to help me put the final polish on it. Basically I want to know how to set r:title from my controller, or view? I noticed the summer reboot documentation effort is producing some good reference material, and I must thank all the contributors for that. I noticed that Sean is still in the progress of completing the section I would be after on this page http://wiki.radiantcms.org/Creating_an_extension_VI. Which was very helpful by the way. Thanks, Carl Pattie. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Setting r:title from a custom extension
You can set the @title instance variable somewhere in your controller or template or create a content_for block in your template named :title: % content_for :title do %4-Minute Sweet Harmonious Biscuits% end % Sean Carl Pattie wrote: Hi everyone. I have been using Radiant for a while, and have finally made an extension for a customer, but I have question for you all to help me put the final polish on it. Basically I want to know how to set r:title from my controller, or view? I noticed the summer reboot documentation effort is producing some good reference material, and I must thank all the contributors for that. I noticed that Sean is still in the progress of completing the section I would be after on this page http://wiki.radiantcms.org/Creating_an_extension_VI. Which was very helpful by the way. Thanks, Carl Pattie. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Setting r:title from a custom extension
Sean Cribbs wrote: You can set the @title instance variable somewhere in your controller or template or create a content_for block in your template named :title: % content_for :title do %4-Minute Sweet Harmonious Biscuits% end % Sean Thanks Sean, That worked a treat. My extension has that final polish I was looking for. Carl -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
