[Radiant] Re: Radiant Browser Support -- Drop IE6?
Chris Parrish wrote: Would anyone be left out if Radiant failed to support IE 6? I vote against dropping IE6 support. My rationale is a sad one: many enterprise clients in the Netherlands (think governments, education institutes, healthcare, and the like) typically have a locked-down and out-of-date workstation. Though they aren't likely to run Radiant for their main web presence, many smaller internal groups can benefit from Radiant. Only recently did one of my government clients upgrade from Windows 2000 and IE6 to Windows Vista and IE7. Many more will follow suit, but for now I would suggest keeping IE6 support around for one more major release. Keeping it around for one more major release also provides room for giving a deprecation announcement so developers can phase it out. And who knows, somebody might actually pick up maintainership if he feels a pressing need... -- Roderick van Domburg http://www.nedforce.nl -- 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] [ANN] Ray extension
Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ 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
aha, that did it! thanks On Sun, Jul 20, 2008 at 10:01 AM, Sean Cribbs [EMAIL PROTECTED] wrote: 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 -- Aleks Clark 941-961-9713 http://built-it.net ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Radiant Browser Support -- Drop IE6?
Before there is more discussion on this, would it be possible for us to get a list of problems that have arisen due to support for IE6? I don't really have a frame of reference for how much work it is to maintain support. I personally think the best course of action would be to extract any IE6-specific support in an extension that way those that need it can have it with future versions of Radiant and help maintain it themselves. Regards, Josh On Jul 21, 2008, at 4:18 AM, Roderick van Domburg wrote: Chris Parrish wrote: Would anyone be left out if Radiant failed to support IE 6? I vote against dropping IE6 support. My rationale is a sad one: many enterprise clients in the Netherlands (think governments, education institutes, healthcare, and the like) typically have a locked-down and out-of-date workstation. Though they aren't likely to run Radiant for their main web presence, many smaller internal groups can benefit from Radiant. Only recently did one of my government clients upgrade from Windows 2000 and IE6 to Windows Vista and IE7. Many more will follow suit, but for now I would suggest keeping IE6 support around for one more major release. Keeping it around for one more major release also provides room for giving a deprecation announcement so developers can phase it out. And who knows, somebody might actually pick up maintainership if he feels a pressing need... -- Roderick van Domburg http://www.nedforce.nl -- 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Browser Support -- Drop IE6?
For now I think it is appropriate to drop support for IE6. We can certainly accept a patch back to add it in latter, but I think it is more important to get the new interface implemented than to quibble over the details. Thanks for being willing to work on this Chris. -- John Long http://wiseheartdesign.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] Summer Reboot Update
On Jul 17, 2008, at 1:52 PM, Jim Gay wrote: On Jul 17, 2008, at 1:32 PM, Oli Studholme wrote: Im happy to flesh out the tag documentation and add examples, but someone else will need to write the script to automatically generate/update wiki pages using the available tags text. If such a script is impractical Ill start doing it manually if a tag reference header page is created. The Help extension does this for you when you install it. Even better, it gives you documentation for all installed tags and to which page types they apply. http://github.com/saturnflyer/radiant-help-extension/tree/master It does not, however, provide examples beyond what comes with the tag descriptions. I just added http://github.com/saturnflyer/radiant-help_use_cases-extension/tree/master So your extra documentation could be added in as an option (although this still isn't as non-technical as editing a wiki) It has almost nothing in it, but I added the ability to extend the docs for the installed tags in Help http://github.com/saturnflyer/radiant-help-extension/commit/d9a4634724465ca115bd0f246b4665917efbe724 (thanks Sean) This will allow extension developers to add help use cases to their tags outside of the description in the model. My priority is to flesh out the features and documentation of Help, but I'll be adding more info to Help Use Cases as time goes on. If you are interested in writing docs for each tag, I'll gladly grab it and put it into Help Use Cases. -Jim Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] restful_authentication or other front end authentication
Hi, I've been searching through the archives to see if this had been done, but I haven't found much. Radiant is a good fit for a project am working on, and the extension system looks for my content needs that are non-standard. 2 questions: My first question is regarding front end authentication. There is some content that I need to display based on logged_in? and group. Has anyone done something like this before. On standard rails apps I have been using restful_authentication but I am getting errors when installing the plugin. I have tried using it without migrations - as a user and sessions table already exist. Second this functionality will obviously require a non-cached mode. I read about a config option to run in this mode, I am wondering how well this is working in production. Any help is appreciated. 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] Radiant Browser Support -- Drop IE6?
Hello all. Thanks for the input. As John mentioned, I am beginning work on the new Radiant UI, and my main goals are: 1. It needs to function correctly 2. I want the CSS/Markup to be as simple (understandable) as possible as this is open source 3. I want to produce something that won't inadvertently break (maintainer removes one line to change something only to learn that that line was necessary as a browser hack) Browser limitations/variations work against all of these (I'm currently fighting with Firefox). I'm trying to find a happy (read: sane)-medium and I wanted people's take on things. The consensus seems to be: * Most could live without IE6 (no current users requiring it) * Many/some could foresee a case where IE6 might be needed So, I agree with John Jim that we should shoot for IE 7+ support with the ability to add in IE 6 as an extension. Besides, I'm working on some of the harder parts now and it's looking like PNG support may be the only limitation (I had other ones in mind when I asked this question but I think those may be working themselves out). Jim Gay wrote: Chris, I'm trying to clear up my schedule to get more involved in the new UI. Have you forked radiant-prototype or do you gave a public location for ideas that you're working on? It didn't make sense to fork John's Radiant Prototype as that is really a complete prototype of the existing UI. I have made a copy of it and will be hosting it on GitHub here shortly (I'm trying to get the _layout.haml file working so that the nav will be nailed down before releasing). Time permitting, I'll have it up by Wednesday. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Browser Support -- Drop IE6?
On Jul 21, 2008, at 10:38 AM, Chris Parrish wrote: Time permitting, I'll have it up by Wednesday. Great! Send a message when you do, I'm eager to help. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Radiant Browser Support -- Drop IE6?
Chris Parrish wrote: Would anyone be left out if Radiant failed to support IE 6? I vote to drop IE6 to coincide with the new Radiant UI release and move IE6 support to an extension. - Dave -- 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] [ANN] Ray extension
It is possible. I'm just not sure the best way to do it. When I started both options were considered and I guessed (possibly wrongly) most people aren't “scm'ing” their Radiant app. So instead of going around git init'ing everyone's RADIANT_ROOT for them I figured clones were less fuss, less muss. So would you change the default to pull-in a submodule? Or add another option to switch from clone to submodule mode (i.e. `use=submodule`)? On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Sean john muhl wrote: It is possible. I'm just not sure the best way to do it. When I started both options were considered and I guessed (possibly wrongly) most people aren't “scm'ing” their Radiant app. So instead of going around git init'ing everyone's RADIANT_ROOT for them I figured clones were less fuss, less muss. So would you change the default to pull-in a submodule? Or add another option to switch from clone to submodule mode (i.e. `use=submodule`)? On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
You mean RAILS_ROOT, but yes, that would be reasonable. Sean john muhl wrote: On 2008/07/21, at 10:39, Sean Cribbs wrote: In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Now I'm thinking that it might be simplest to just look for RADIANT_ROOT/.git and if it's found switch into submodule mode, otherwise a clone is done. My thinking is that if you have a .git directory at RADIANT_ROOT you've either decided to scm your install or someone put it there for you because they wanted to scm your install. In either case the best option is be a submodule. On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Does the above scenario sound like the behavior you were after? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
On Mon, Jul 21, 2008 at 2:25 PM, john muhl [EMAIL PROTECTED] wrote: On 2008/07/21, at 10:39, Sean Cribbs wrote: In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Now I'm thinking that it might be simplest to just look for RADIANT_ROOT/.git and if it's found switch into submodule mode, otherwise a clone is done. My thinking is that if you have a .git directory at RADIANT_ROOT you've either decided to scm your install or someone put it there for you because they wanted to scm your install. In either case the best option is be a submodule. I just passed over the Ray extension because I just saw deploy with Capistrano and thought deploying with git is easy enough. But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. How easily does this fold into an existing Radiant install? Will it detect the submodules that are there already? -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Radiant Browser Support -- Drop IE6?
On Mon, Jul 21, 2008 at 12:04 PM, David Piehler [EMAIL PROTECTED] wrote: Chris Parrish wrote: Would anyone be left out if Radiant failed to support IE 6? I vote to drop IE6 to coincide with the new Radiant UI release and move IE6 support to an extension. I vote the same. And where can I register my extreme disgust for IE's (lack of) CSS support, anyway? -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Radiant Browser Support -- Drop IE6?
On 21-Jul-08, at 12:42 PM, Tim Gossett wrote: On Mon, Jul 21, 2008 at 12:04 PM, David Piehler [EMAIL PROTECTED] wrote: Chris Parrish wrote: Would anyone be left out if Radiant failed to support IE 6? I vote to drop IE6 to coincide with the new Radiant UI release and move IE6 support to an extension. I vote the same. And where can I register my extreme disgust for IE's (lack of) CSS support, anyway? You could try the IE blog but /dev/null will be more effective. Actually I suspect that when IE8 comes out the won't be nearly as craptacular as its ancestors and almost reach respectability. Passing ACID 2 goes a long way in my books (by comparison to IE6). -- Tim Gossett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
On 2008/07/21, at 12:30, Sean Cribbs wrote: You mean RAILS_ROOT Whoops, you're right. I must have had Radiant on the brain. On 2008/07/21, at 13:37, Tim Gossett wrote: I just passed over the Ray extension because I just saw deploy with Capistrano and thought deploying with git is easy enough. and that part hasn't even been started yet :) I just removed those words from the github description, sorry about the confusion. But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. It doesn't do that yet, but it looks like where I'll be taking it the next time I have a few minutes to work on it. It's actually the presence of a working `git` command in your PATH that determines git or http mode. How easily does this fold into an existing Radiant install? Will it detect the submodules that are there already? If you've already installed extensions as submodules and then install Ray you'll be able to add more extensions as submodules (they'll be global to your project just like the others you added), except you can roll it all up in to one handy command, i.e. rake ray:extension:install name=mailer restart=passsenger – of course it won't do that today but within the next day it should be working that way. Pretty soon after that I'll be adding ray:update, ray:extension:update:all and ray:extension:update name=mailer commands and I'll make sure these work off submodules if you've got your extensions (even ray) installed that way. Thanks for the feedback. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Radiant Browser Support -- Drop IE6?
On Mon, Jul 21, 2008 at 2:42 PM, Tim Gossett [EMAIL PROTECTED] wrote: And where can I register my extreme disgust for IE's (lack of) CSS support, anyway? If you are talking about IE6 then you have no place. And as for IE7 you need to know that the current Internet Explorer team is completely new as Microsoft disbanded the IE team when it looked like they won The Great Browser War. There are no IE6 team members on the current IE team, so things will only get better from here. I think once IE 8 is released into the wild we (designers/developers) can finally start abandoning IE 6 in earnest. Be thankful we don't need to support 5.5 any more. ;^) ~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] Radiant Browser Support -- Drop IE6?
I can get PNGs to work just fine with IE 6 via pngfix.js or just using IE's proprietary filters in the CSS. But you can't do any fancy positioning -- just left/top aligned images for backgrounds. There are other ways to skin that cat, so there should be a solution there somewhere. I just don't want to have to support or maintain it. There will be other issues that crop up before we're done, I'm sure. -Chris Nate Turnage wrote: On Mon, Jul 21, 2008 at 9:38 AM, Chris Parrish [EMAIL PROTECTED] wrote: So, I agree with John Jim that we should shoot for IE 7+ support with the ability to add in IE 6 as an extension. Besides, I'm working on some of the harder parts now and it's looking like PNG support may be the only limitation (I had other ones in mind when I asked this I always use pngfix.js to get IE6 to work with transparent png files and it works like a charm. Find it here: http://homepage.ntlworld.com/bobosola/index.htm ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Browser Support -- Drop IE6?
You might want to try this: http://ajaxian.com/archives/iepngfix-2-now-supports-css-background-position-and-repeat I haven't tried it but it looks promising. Adam On 21-Jul-08, at 1:35 PM, Chris Parrish wrote: I can get PNGs to work just fine with IE 6 via pngfix.js or just using IE's proprietary filters in the CSS. But you can't do any fancy positioning -- just left/top aligned images for backgrounds. There are other ways to skin that cat, so there should be a solution there somewhere. I just don't want to have to support or maintain it. There will be other issues that crop up before we're done, I'm sure. -Chris Nate Turnage wrote: On Mon, Jul 21, 2008 at 9:38 AM, Chris Parrish [EMAIL PROTECTED] wrote: So, I agree with John Jim that we should shoot for IE 7+ support with the ability to add in IE 6 as an extension. Besides, I'm working on some of the harder parts now and it's looking like PNG support may be the only limitation (I had other ones in mind when I asked this I always use pngfix.js to get IE6 to work with transparent png files and it works like a charm. Find it here: http://homepage.ntlworld.com/bobosola/index.htm ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Browser Support -- Drop IE6?
Oh dear. Is cat skinning a requested feature of Radiant? Surely that can be moved to an extension, along with pelting, flaying, and tanning. You know, for the sake of the children and vegetarians. On Mon, Jul 21, 2008 at 4:35 PM, Chris Parrish [EMAIL PROTECTED] wrote: I can get PNGs to work just fine with IE 6 via pngfix.js or just using IE's proprietary filters in the CSS. But you can't do any fancy positioning -- just left/top aligned images for backgrounds. There are other ways to skin that cat, so there should be a solution there somewhere. I just don't want to have to support or maintain it. There will be other issues that crop up before we're done, I'm sure. -Chris Nate Turnage wrote: On Mon, Jul 21, 2008 at 9:38 AM, Chris Parrish [EMAIL PROTECTED] wrote: So, I agree with John Jim that we should shoot for IE 7+ support with the ability to add in IE 6 as an extension. Besides, I'm working on some of the harder parts now and it's looking like PNG support may be the only limitation (I had other ones in mind when I asked this I always use pngfix.js to get IE6 to work with transparent png files and it works like a charm. Find it here: http://homepage.ntlworld.com/bobosola/index.htm ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
