[Radiant] Virtual Pages and Permissions
Would anyone have any objection to hiding virtual pages from anyone who is not an Admin or Designer in 0.9? It strikes me that virtual pages are mostly used for system specific stuff like FileNotFound pages or ArchiveIndex pages. If we went this route, we would also hide virtual pages from normal users in the PageType dropdown. -- John Long http://wiseheartdesign.com http://recursivecreative.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Design Help Needed! A Call To Action
Howdy folks, Just wanted wanted to issue a public call to action for those of you who may be interested in helping out on Radiant's design: http://wiseheartdesign.com/articles/2010/02/17/open-source-design-help-needed/ I'm looking for a few good men. Or women whatever the case may be. :) Seriously, if you'd like to help, that's a roadmap how-to article on how to get started. Please, please send this around to all of your designer friends. I would love to see if we can make this work and have been disappointed we don't have more people contributing to the design effort. -- John Long http://wiseheartdesign.com http://recursivecreative.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Volunteers Needed! Extension Registry Maintainers
Howdy folks, I just deployed a change this evening that will allow me to give admin rights to users of the extension registry. Users with admin rights have the ability to edit or delete any extension. If you would be interested in helping maintain the extension registry please contact me directly. I am looking for a couple of people who can make sure that extensions added to the registry have good descriptions, accurate URLs, screenshots, etc... who are willing to make a commitment to spend an hour or two every few weeks looking over entries for new extensions and maintaining the old entries. You need should have experience installing extensions and enjoy writing and editing. If you are looking for a way to give back to the community this is a fantastic way to get involved! Special thanks to Michael Hale for helping me implement this feature. -- John Long http://wiseheartdesign.com http://recursivecreative.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] [ANN] Radiant 0.9.0 RC1
On Oct 10, 2009, at 3:01 PM, Mamed Mamedov wrote: But, I have question: where can I find API Documentation for Radiant CMS? For example, I'am developing some extension for my radiant project (to complete my purposes) and all can I find - it is a wiki.github.com/radiant. There are only articles, but there are no any API documentation on built-in Radiant classes which is mostly used by extensions. The closest thing that we would have to that is this: http://wiki.github.com/radiant/radiant/creating-extensions Also it's highly recommended that you browse the source when you have questions about how stuff works. Radiant is a standard Ruby on Rails application, so have a look at a couple of the Rails tutorials first if you are not familiar with Rails. -- John Long http://wiseheartdesign.com http://recursivecreative.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] Bespin Editor Extension
On Oct 9, 2009, at 2:01 AM, Mamed Mamedov wrote: Is anyone tested it on 0.7.1 version of Radiant? It will not work with 0.7.1 because it relies on new javascript that is only included in edge (notably lowpro.js). It shouldn't be too hard to backport, but it would require modifications to bespin_codearea.js. -- John Long http://wiseheartdesign.com http://recursivecreative.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Radiant 0.9.0 RC1
Hello! I am pleased to announce the first release candidate of Radiant 0.9.0. The big news in this release is that we have updated the interface to make it more stylish and compact. If you are a long time Radiant user you will appreciate the small refinements that have been made to make Radiant easier for both power users and normal folks. Apart from the stylistic changes, there are a couple of changes that ware worth mentioning: * There are now two levels of tabs. The intent here is provide more organization for folks that have a lot of extensions installed. The primary top level tabs are now “Content”, “Design”, and “Settings”. * We’ve added hot-keys for saving. You can now press Ctrl+S to save a page and continue editing, or Ctrl+Shift+S to save a page and return to the index page. * We’ve reduced the number of flash messages in favor of status messages that pop up when you submit a form. * We’ve added support for the tab key to text areas. On Safari and Firefox there is also support for multiline indent and unindent. This release is primarily aimed at extension developers. We want to encourage all extension developers to update their extensions to work with 0.9.0 as the interface changes in this release are significant and will break existing extensions. We would like to hear as much feedback as possible about what we can do to make it easier to upgrade extensions for the new version. Any patches or pull requests that are submitted in this vein will be given a higher priority. There are a number of changes that did not make it into this release candidate that may make it into the final version in one form or another. Among them internationalization, asset management, password reset, filter toolbars, and a revamped settings interface. We now using GitHub Issues to keep track of feature requests and bug reports. If there is a particular feature that you feel should be in 0.9.0 or a bug report that you would like to file, do so there. You can also vote on existing features to improve the odds that they will be implemented by one of the core team members. As always we welcome your feedback and contributions. == Download Install You can download the gem here: http://radiantcms.org/downloads/radiant-0.9.0-rc1.gem Install it with the gem command: gem install radiant-0.9.0-rc1.gem This will install the gem as ‘radiant-0.9.0’. == How to Upgrade an Existing Project or Site 1. Update the Radiant assets from in your project: rake radiant:update 2. Migrate the database: rake production db:migrate 3. Restart the web server -- John Long http://wiseheartdesign.com http://recursivecreative.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Bespin Editor Extension
I just created an extension that embeds the Bespin editor from Mozilla into Radiant. Bespin is a full featured code editor with syntax highlighting, indentation support, etc... You can see a screenshot of Bespin in action here: http://www.flickr.com/photos/johnwlong2000/3994356654/ To install: script/extension install bespin_editor This version of the extension has only been tested on edge, it will probably NOT WORK with earlier versions of Radiant. Try it out and let me know what you think. Patches and pull requests welcome. -- John Long http://wiseheartdesign.com http://recursivecreative.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] New How-Tos for Dreamhost
Andrew, Thanks for writing this stuff up. Please make sure that links to these articles make it onto the wiki. -- John Long http://wiseheartdesign.com http://recursivecreative.com On Oct 7, 2009, at 11:03 PM, Andrew Siegel wrote: I been spending a lot of time working with Radiant CMS 0.7.1 and 0.8.1 on DreamHost and documented my latest deployment of Radiant 0.8.1 to a Dreamhost shared account. Please take a minute to review my tutorials and provide feedback. Installing on Dreamhost and Bootstrapping - http://blog.ajsiegel.com/2009/10/07/setting-up-radiant-cms-0-8-1-on-dreamhost/ Setting Up Extensions(drag_order, paperclipped, tinymce_filter) - http://blog.ajsiegel.com/2009/10/07/adding-extensions-to- radiant-0-8-1/ Thank you, -- Andrew J. Siegel President Stegel Systems Consulting http://www.stegelconsulting.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
[Radiant] Roadmap for 0.9.0
Howdy folks, I spent some time today working on an official roadmap for 0.9 and beyond using the GitHub issue tracker: http://github.com/radiant/radiant/issues As you can see there are a lot of items that are tagged with the 0.9.0 maybe tag. That's because we would like to do another release this fall, but are not sure that we will get to everything. == Help Us Prioritize I've tried to prioritize the list based on what's important to me, but I'd also like to request that the community vote on the items so that the core-team can factor in your needs as well. Votes won't necessarily change an item's priority, but it will give us a good idea of what is important to you. == Did We Miss Something? Feel free to add your own feature requests or suggestions to the issue tracker. Items that are tagged with a release number are part of our official commitment for Radiant. == We Need Your Help! Working on Radiant is a labor of love for the members of the core team. We are all busy individuals that don't always have a lot of time to devote to Radiant. So if some of this is going to get done it is going to take the support of individuals like you. So please, help us knock these issues out in your own fork. Once you have a feature implemented and well tested, send the radiant github user a pull request. Also, if there is a feature that you are passionate about you can always up it's priority by working on it in your own fork. -- John Long http://wiseheartdesign.com http://recursivecreative.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] URL tags
On Sep 23, 2009, at 10:53 AM, Andrew vonderLuft wrote: As info, these are the tags Sean mentioned: tag 'if_blank' do |tag| ... end tag 'unless_blank' do |tag| ... end I like this: r:if_blank part=my_part r:unless_blank part=my_part The current semantics of if_content are nice because you can leave a part blank to intentionally get it not to render. If you only had if_blank, there is no way to get that behavior. -- John Long http://wiseheartdesign.com http://recursivecreative.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] URL tags
On Sep 23, 2009, at 12:17 PM, Chris Parrish wrote: Anton Aylward wrote: Personally I am tired of the if_ and prefer the more generic simple if with some parameter. It look more natural. I suppose you all know where I stand on this. Anton, I use my conditional tags extension (http://github.com/SwankInnovations/radiant-conditional-tags-extension ) for just this reason. I can already do most (all?) of this now using it. Ah, the age old argument for adding real conditionals to Radius. :) Yes, if you feel this way, use Chris's extension. -- John Long http://wiseheartdesign.com http://recursivecreative.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] URL tags
On Sep 23, 2009, at 3:26 PM, Jim Gay wrote: Users don't care about keeping the database clean. Developers might care, but regular content editors just want to know where to put their content. And the problem with deleting a page part is that the user needs to remember what it was called to successfully recreate it and have it appear in the layout. True, but it's developers/designers that make a decisions about using either if_content or unless_blank, not the users. I'm willing to concede that this is something that people want and accommodate for it with the if_blank tag, but I would personally discourage it's usage. I think that an appropriate way to discourage the use of if_blank is to insist that it be in an extension. It's default presence in the list of Available Tags is encouragement of its use, in my opinion. It depends on how strongly you want to discourage it's use. Maybe. It's not the addition of a tag or attribute that I'm after, it's the purposeful, intuitive naming of tags and the correction of ones that aren't quite right: if_url and if_content being examples. I think that it is hear that I again have to point to ruby. The principle of least surprise does not mean that it is your least surprise, it's matz's. In the same way intuitive for you doesn't necessarily mean intuitive for me or others. What about recording the previous existence of page parts for each page? So that after you delete a part, a link/button becomes available to re-add that part (blank). That, to me, would solve the problem where users would not be required to recall the exact name (related-links, related_links, RelatedLinks, what was it?) and would better connect the idea that content is an actual page part, and not the text. Actually, it would be cool to see a list of all of the existing page part names on the add part dialog. Click on a name to fill in the the part name. Type to filter the list. Would that solve the problem? -- John Long http://wiseheartdesign.com http://recursivecreative.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] URL tags
On Sep 23, 2009, at 5:33 PM, Jim Gay wrote: So how will Radiant (or John Long) be discouraging its use? Would the documentation in the tag reference say that? I don't think there is a need to document this in the tag reference. It will be somewhat discouraged by having if_content and unless_blank instead of having the default behavior of if_content be to not render blank content. Couldn't you argue that we should keep the behavior of if_url based on that? I suppose you could argue that, but it's somewhat different in this case. This is about intent. The if_url change is about being more consistent with Rails. I'd rather not need to do r:if_content part=my_partr:unless_blank... all the time just to allow users to keep their easy-to-understand-and-remember places to put text. You won't. You'll do: r:unless_blank part=sidebarr:content part=sidebar // r:unless_blank There is no need to use both conditionals. True; I'm making that same point. Although if_content is intuitive to you, it is not intuitive to me and to some of my users. Your opinion is obvious that page parts are content, but I don't agree (and I don't think the Radiant interface encourages that idea). I have experienced questions from people using if_content where they expected content in the if_content tag to mean text. Changing the interface, could possibly solve that discrepancy between our opinions/experiences. I'm definitely up for changes that help make the intent clearer. Actually, it would be cool to see a list of all of the existing page part names on the add part dialog. Click on a name to fill in the the part name. Type to filter the list. Would that solve the problem? Yes, if it stored names of parts that used to exist. Suppose there is one page that has a widget_x part. A user may delete it and try to recreate it later and they would either need to recall that it is not WidgetX or some other variation, or the list of parts would need to contain widget_x even though it may not exist anymore on any page. What about a radiant config setting for standard part names? Perhaps it is default page parts that should go away. My initial thought was that it would be just for the current page, but then it would be a pain to find part names of parent pages, so a site-wide list would be much better. Agreed. I envision your suggestion like the 'suggest a friend' interface on facebook. Something like that. -- John Long http://wiseheartdesign.com http://recursivecreative.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] URL tags
On Sep 23, 2009, at 8:01 PM, Jim Gay wrote: Ok. At first this seems reasonable, but will unless_blank also implement the inherit attribute to look up the page tree? I'm fine with that. If it will be implemented with inherit, it brings me back to just wanting to use if_content. And if_content has other nice features like finding multiple parts. It can be implemented that way on if_blank as well. -- John Long http://wiseheartdesign.com http://recursivecreative.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] Blade Interface merged into edge
For those of you who are developing extensions for Radiant, please update them to work with the new interface and give us your feedback on what your like and dislike. The most significant changes in the UI have been made to help extension developers keep things organized. --John On Sep 15, 2009, at 12:45 PM, Sean Cribbs wrote: Radiant users, John Long and I just merged the blade branch into the master branch. This includes a large number of changes to the user interface and some fundamental API changes (especially related to the navigation tabs). The work is by no means done on the interface, but now you can start using it if your project is on edge. We look forward to your input! Cheers, Sean ___ 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] Blade Interface merged into edge
On Sep 15, 2009, at 3:47 PM, john muhl wrote: i sent a bunch of feedback to the list sometime ago about the blade ui but it was never responded to. should i bother re-sending that? or was the lack of response the response? I must have missed that somehow. Please repost it. -- 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] Volunteers Needed! Radiant Wiki Migration
On Apr 8, 2009, at 2:37 AM, Simon Rönnqvist wrote: Are we really 100% sure that we want to keep the project forever at GitHub? Few things are forever. But this does look like a good strategic move for the future. There isn't a great Ruby-based wiki solution. And if we hosted it ourselves it would be one more thing to keep up and maintain. I've looked at other hosted wiki solutions and have even asked for free hosting on some of the more well-known ones, but didn't get a response. As long as the Rails community is on Git, GitHub will be a great solution. -- 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] Volunteers Needed! Radiant Wiki Migration
On Apr 7, 2009, at 1:21 PM, Steven Southard wrote: I'm happy to help. I'll do the first part or the second. It only looks like about 50 pages. Let me know which you want from me. Awesome Steven. Why don't you start on the first part. -- 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] Volunteers Needed! Radiant Wiki Migration
On Apr 7, 2009, at 2:24 PM, Steven Southard wrote: The images look like they can stay were they are for now. Agreed. I believe they are all hosted on other servers. Is a txt file named with the page title containing the page content okay? I don't see the author and date info, do we need that? If it's okay I'll make a file for any page that has content under http://wiki.radiantcms.org/all/list . I think that'd be fine for now. Maybe look through the generated pages before moving on to step 2 and remove any that are bogus. -- 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] [ANN] Radiant 0.7.0 Intaglio Release
On Feb 8, 2009, at 12:13 AM, Mohit Sindhwani wrote: Congratulations to everyone! This is great :) Sean, I'm guessing Radiant 0.7.0 is considered stable now. Should we start migrating documentation to Radiant 0.7.0? Absolutely. :-) -- 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] Cache Home Page (prevent the long delay)
On Jan 22, 2009, at 10:50 AM, Ben Morrow wrote: I run Radiant on Passenger and I was wondering if there was a way to have the home page of a site always cached. When there have been no visitors to a site for about a day, it often takes the sever more than 20 seconds to respond to a request for a page. You could set the cache timeout to 2.days, or something of that nature. -- 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] Radiant for Bloging - articles
Speaking of the Summer Reboot, maybe it would be good to fold it into the Radiant Handbook now and start the Spring Documentation Continuum. After all, it's hardly Summer anymore, and small iterations are good. Just my 2 cents. :-) And thanks to everyone who has contributed to the documentation effort. You are all heros in my book. -- 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] r:find question
On Dec 3, 2008, at 8:56 AM, Sean Cribbs wrote: YAY! Someone who agrees with me! The caveat, of course, is that often you need to put Radius tags inside the attributes of HTML tags. But that's because Radius is not strict XML, but interpolated. When explaining Radius to a local web design meetup, one sorta-technical guy suggested we use an XML parser/XSLT and I had to tell him no. It only looks like it could be. To add to this, another reason to avoid it is that it requires parsing the template twice. Once to parse the tags out and once to parse the attributes. I'm more interested in the idea of adding support for some kind of variable notation from within the tags. Something like Chris Parrish's extension, though I think the syntax could be improved. -- 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
[Radiant] Re: [Radiant-Dev] [ANN] Radiant Mini-Sprint - December 13
More info: I’m excited to announce that we are planning another Radiant CMS Sprint in December. == What A day-long hackfest to help finish some features for the 0.7 release of Radiant CMS. The official goals are—refactoring the admin controllers toward REST, continuing work on the new UI, adding blogging features, improving the extension registry, and writing more documentation. == When Saturday, December 13, 2008, 9:00am-6:00pm == Where Red Hat 1801 Varsity Dr Raleigh, NC 27606 Map: http://tinyurl.com/redhat-raleigh == Who Members of the Radiant dev team and anyone else who wants to attend - hopefully you! THIS IS NOT A CONFERENCE! The focus is on hacking out a lot of code/ design/documentation in a short amount of time. We encourage anyone who can contribute their code, web design, or writing skills to attend. If you’ll be coding, it would be good to have a working knowledge of Rails, RSpec, and Git — bonus points if you’ve worked on Radiant before, built extensions, or have experience with RESTful controller design and web-services. If you are interested in helping with the design, it would be good to have a working knowledge of HTML, CSS, JavaScript, and image manipulation. If you want to do documentation, we expect you to be able to write clearly and use the Radiant wiki. After the hackfest a group of us will probably go out to one of the nearby restaurants for some of the local fair. If you plan to attend, please RSVP on the Raleigh Ruby Brigade's meetup page: http://www.meetup.com/raleighrb/calendar/9235561/ Interested in sponsoring some food, drink, or swag for the attendees? Contact me or Sean Cribbs privately. -- John Long http://wiseheartdesign.com http://radiantcms.org___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radius Now on GitHub
I finally got around to putting Radius on GitHub this evening. Fork away: http://github.com/jlong/radius/tree/master -- 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] So how did things go this weekend?
On Oct 27, 2008, at 8:59 PM, Nate Turnage wrote: Is everybody still asleep after the long weekend? I am dying to hear how things went with the sprint. Sean? John? Anyone? It was a great weekend Nate. Sean headed up the work on the code and I worked with people who were interested in helping implement the new design. I'll let Sean tell you more about the work that was begun on code, but I can tell you a little of what was accomplished on the design side. The most visible stuff was integrating the work Chris Parrish has done on the HTML for the new design. You can see some of the results in the prototype. (There's a README in the prototype project on GitHub for getting it up and running.) Jim Gay spent some time working on rewriting the HTML for the treeview to use a list instead of a table. He didn't complete it, but some valuable things were learned along the way and we had some good discussions about how the real-estate can be better used on the pages tab. Daniel Beach worked on the HTML for custom page attributes. When this is integrated it will make it easier for people to add custom attributes to pages for configuration and some of the other things that they are using page parts for. You can see some of the results in his fork of the radiant prototype. Justin Blecher did some wireframes that sparked some of the treeview discussions and wrote up some excellent suggestions for improvements to the website and documentation. I pretty much presided over the work being done and talked a lot. :-) To me the most valuable part of the weekend was not so much the work that was done, but the relationships that were formed. I am hoping that the groundwork was laid for some exciting contributions from folks in the future. As a side note anyone interested in helping with design stuff on Radiant should check out the radiant-mockups and radiant-prototype projects on GitHub. The mockups project contains a lot of the ideas for the new UI. And the prototype contains the HTML for some of the new things that are being developed. If you are interested in helping, fork the prototype, implement your idea, and tell us about it on the mailing list. If we like it, your changes will be incorporated into the official prototype and will be slated for development for sometime in the future. Also contributions and improvements on the HTML and CSS are welcome! -- John ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New wiki article: removing scaffolding from the Link Roll
On Oct 2, 2008, at 6:52 PM, Andrew Neil wrote: I've written a new article for the wiki, which follows on from the original Creating Radiant Extensions[1] tutorial. It demonstrates how to remove the scaffolding from your extension, and style it so that it looks more like it belongs in Radiant. Find it here: http://wiki.radiantcms.org/Radiant_extensions_without_a_scaffold I would be very pleased if anyone could follow it though, and let me know if everything makes sense. It is a wiki, so do please fix any typos or factual errors. I was originally planning to merge this directly into the Creating Radiant Extensions article. When I first read that article, it recommended using scaffold :link in the LinksController, but since Radiant moved onto Rails 2 this method hasn't worked. There is a section now in the article called Hacking a Scaffolded Controller and Views, which I hadn't seen before. I considered deleting that section, and replacing it with the article above, but I wondered if it made the article just too long. Great stuff here Andrew. Why don't you merge this with the original tutorial (delete the Hacking section), but make your article a Part 2 on a separate page. That way it will complete the original tutorial. Excellent work on this, BTW. -- 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] Re: File-based Snippets/Layouts with Support for Radiant Tag
I seem to recall an extension for VIM that allowed you to edit stuff in Radiant using VIM. You might give that a try. I can't imagine file- based stuff making it into core though. Perhaps the closest we would get to that would be an import/export feature. --John On Aug 25, 2008, at 1:03 AM, Arik Jones wrote: Sorry Mohit, but that really doesn't help. I think it's a fairly important feature to be able to modify Layout/Snippets outside of the web UI. Also, relying on one browser platform to get this done is quite silly and actually defeats the purpose of a text-editor. Eh... just a thought. -- 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] Shared Layouts
On Jul 6, 2008, at 1:06 PM, Sean Cribbs wrote: Since there seems to be some confusion about how to use share_layouts lately, I'll break it down into steps for you and everyone. I hope this makes it on the wiki somewhere. :-) -- 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] r:children:if_first r:children:if_last
On Jun 26, 2008, at 8:36 AM, Jim Gay wrote: I think it should allow a group or size option. r:if_first size=3 would apply to the first 3. Working with more than just one would be useful. I would want to have these tags with that option: if_first / unless_first if_last / unless_last I'm not sure about the name of the parameter though. Perhaps r:if_first window=3 How about: r:if_index in=1,2,3# if it's one of the first 3 children r:if_index in=-1,-2,-3 # if it's one of the last 3 children r:if_index is=1# equivalent to r:if_first / r:if_index is=-1 # equivalent to r:if_last / r:if_index is=even # if it's an even row r:if_index is=odd # if index is an odd row Seems like a 1 based index would be most helpful here. -- 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] Two Slightly related Questions
On Jun 22, 2008, at 8:00 AM, Mohit Sindhwani wrote: 1. How can I add pictures to the wiki? I want to add screenshots to the Summer Reboot documentation. You will need to post the screenshots on another Web site to do this. A tool like Flickr or Skitch could be used for this. 2. Which is the correct list address? Should I be using radiant@radiantcms.org or [EMAIL PROTECTED] Either is fine. -- 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] Adminstrator and Developer role clarification
On Jun 21, 2008, at 4:21 PM, Alex Wayne wrote: Are my assumptions right? I just want to be sure that in my public extensions I am exposing the right sections to the right users. Nope. An administrator is a superuser. A developer can do everything, but create and edit other users. The two roles are really more akin to root and designer. -- 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] Highline
On Jun 20, 2008, at 9:27 AM, Jamey Cribbs wrote: I've googled a lot, but have not found anything. Is my only alternative to manually replace the older version of highline in the radiant gem's vendor directory with the newer version of highline? You could try that. The other alternative would be to freeze Radiant into your vendor directory and make your changes there. If you really wanted to get your hands dirty, forking Radiant on github, updating and testing the new lib, and then submitting a pull request would be ideal. -- 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] Re: problem updating to v0.6.7
On Jun 2, 2008, at 9:28 AM, Sandip Gangakhedkar wrote: I managed to get it workingthanks for your reply. What was it that you did that made it work? It's always helpful a solution if you figure something out that you posted about to people searching the mailing list archives in the future. -- 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] State of the RadiantCMS UI
On May 29, 2008, at 3:25 PM, Arik Jones wrote: What are some ideas to clean it up or streamline the modify column? We've been playing with some ideas on github. Have a look at the new pages mockups: http://github.com/jlong/radiant/tree/master/mockups/blade -- 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
On May 28, 2008, at 1:15 PM, Chris Parrish wrote: nurilized wrote: why dont you git? You guys are killing me. John's pushing me there today too ;-) For the record, I use Windows and Eclipse (Aptana's RadRails) to do my development. I'm used to, and like both very much. Right now, I can do all my source code control right in my IDE wonderfully -- visually see which files have changed, apply properties, commit, update, etc. Unfortunately git support is weak for Windows and weaker still for Eclipse. So I'm going to have to figure out a new workflow to use my IDE and git as an external tool in order to make the switch. It'll probably happen eventually but I've got enough irons in the fire already for now. The killer thing about git in my mind is Github. It makes it super easy to push changes back and forth on projects. I'd highly recommend sitting through the Peep Code screencast if you haven't already. -- 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] Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Could someone work up a patch for this issue. -- John Long http://wiseheartdesign.com On May 17, 2008, at 10:45 AM, Sean Cribbs wrote: I like your solution better, Martins. Sean Mārtiņš Grunskis wrote: On 5/17/08, Chris Parrish [EMAIL PROTECTED] wrote: I fixed the issue mentioned below. The updated version can be found at: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.2.1 This fix solves the error but still does not properly register the created_by_id and updated_by_id fields in Stylesheets and Javascripts (which was tied to the source of the original error). Does anyone know how to append classes to UserActionObserver? I'd like to fix this issue but if I have my extension's activate method call: UserActionObserver.observe Stylesheet, Javascript it seems to wipe out the existing observation of Page, Snippet, etc. I had this same issue some time ago and you can take a look at how I fixed it here: http://mgr.devjavu.com/browser/audioguide/vendor/extensions/forum/forum_extension.rb#L34 The 0.6.7 issue will have to wait another day... -Chris I'm also getting a undefined method `updated_by' for #Javascript:0x236d6c8 on 0.6.6 when I try to edit a javascript that I just created. Thanks. Looks like a last minute change + no spec coverage on view (yet) = sloppy programmer. ___ 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] Re: if/else statements in radiant tags
On May 1, 2008, at 9:16 PM, Arik Jones wrote: Speaking of code, the radiant admin page textareas could use some sort of tab-enabled feature so I can indent my heavily-dynamic (tons of indented code) pages. I've implemented this with decent results in every browser except the most recent betas of Firefox 3. That sounds very interesting. Finish it off and send us a patch. -- 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] Phusion Passenger and Radiant
On Apr 15, 2008, at 11:11 AM, Giovanni Intini wrote: I've got only one ruby on the system, I'm really clueless on what could be the problem. Have you asked about this on the Phusion mailing list? They might be able to offer you more advice. -- 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
