[Radiant] Weird children:each behavior when mixing filters in 0.6RC1
Hello, I found a weird bug (I think) in 0.6 RC1. It appears that the behavior of the Radius tags differ depending on the filter. I have the following content structure: /Home Page (published) /Stukken (published) /1999 (published) /Beauty Queen of Leenane (published) /2000 (published) /Een draad in het donker (published) /2001 (published) /Roberto Zucco (published) /2002 (draft) /2003 (draft) /2004 (draft) /2005 (draft) /2006 (draft) /2007 (published) /Adel Blank (published) /Festen (published) Some might recognize plays here, and you would be right :) In the default layout there is the following: In Home Page I have the part 'sidebar', filter: Textile (currently this is the only page which this part): In Stukken I have the part 'menu', filter: None: All of the published plays have a 'menu' part, filter: none. When I request the home page what I expect is: 2007 Menu content for Festen. Menu content for Adel Blank. 2001 Menu content for Roberto Zucco. 2000 Menu content for Een draad in het donker. 1999 Menu content for Beauty Queen of Leenane. However, I got the following: 2007 Menu content for Festen. Menu content for Adel Blank. Menu content for Roberto Zucco. Menu content for Een draad in het donker. Menu content for Beauty Queen of Leenane. Also note the weird placements. When you change the filter of 'Home Page' part 'sidebar' to None, I get the expected results. Shall I add this to Trac? Regards, Erik. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Two new extensions - WYSIWYG editor and Maruku filter
On Fri, 23 Feb 2007 19:55:04 -0700, Chris Parrish <[EMAIL PROTECTED]> wrote: > Sounds good. I'm looking forward to playing with this. I can see it > being very useful (though I share John's distaste for using WYSIWYG > editors) for my customers. Ditto. How have you persuaded them to use something else? Mind altering drugs, perhaps? ;) Mine have always been convinced that they need to use dreamweaver to manange their hundreds of pages ... I figured that Radiant with a WYSIWYG was the lesser of two evils. > Are you willing to provide any details on the asset management piece you > are working on? I've read about what the others are doing on and none > of the approaches seems quite "right" for my needs. I think that John believes that assets should belong to a page rather than being more universal in nature, but I honestly think that this may complicate things too much for the average user. In my system all assets are available to all pages. You add those assets (be they images, pdfs, whatever) to your bucket (yes, I'm shamelessly ripping off Mephisto's buckets), and then you simply click on them to insert them into your page. The insert behavior is "smart". If you are inserting an image, it will insert an image tag into the page. This tag differs depending on the filter applied to the page ... if you have no filter applied, or if you have my WYSIWYG applied, a basic will be inserted into the page; if you use markdown you'll get a  ... you get the idea. If you try to insert a PDF, mp3, etc. into the page (or something else that can't be directly viewed by the browser) the insert behavior will stuck a link into the page instead. Like above, the precise form of this link will depend on the filter that is applied to the page. In short, I think that inserting an asset into a page should be a simple procedure ... the user shouldn't have to think about the markup required to insert it. Since most assets are likely to be images, I want to make it easy for the user to resize those images to suit their needs. The URL of the image determines the size of the image, and the image can only be resized from the admin side of things. I'm still working out the details of how all of this will work, but I've got a basic system in place that seems to work well. It still hits the database to determine if an asset matching the size parameters exists ... I need to work that out yet to minimize the database load. Is this at all like what you're looking for? What are your ideas on the matter? -- Nathan Wright ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Two new extensions - WYSIWYG editor and Maruku filter
Sounds good. I'm looking forward to playing with this. I can see it being very useful (though I share John's distaste for using WYSIWYG editors) for my customers. Are you willing to provide any details on the asset management piece you are working on? I've read about what the others are doing on and none of the approaches seems quite "right" for my needs. Actually, anyone working on an asset management system is welcome to contact me directly. If there is some way to make things work, it is possible that I could generate some funding to help develop it. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Two new extensions - WYSIWYG editor and Maruku filter
I was a little late to the game when it came to checking out the Mental branch, but *wow* I really like what I see. The extensions are very slick, and I can already see myself spending long hours making new ones. In fact, I've got a few to offer right now. The first is a simple text filter based on Maruku http://maruku.rubyforge.org/ >. Maruku is very much like Markdown, but it has extended HTML support and a number of other goodies. You can download it here: http://tinyurl.com/yr96bz > The second is the one that I know a lot of people have been waiting for (Florian, I'm looking at you ;) ). This is a WYSIWYG extension based on TinyMCE. It's still a work in progress (I want to integrate an asset handler) but the basic functionality is all there. http://tinyurl.com/2xfegp > Try 'em out and tell me what you think ... I'll be around on and off over the weekend to answer questions or help with problems, so don't be scared to ask. It may take a minute to get back to you, but I'll do my best. -- Nathan Wright ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Facets branch extensibiliy extended
On Feb 23, 2007, at 1:14 PM, Jacob Burkhart wrote: > If you guys would like to keep up with my "usecase" for the facets > changes I proposed, you can now take a look at: > > http://dev.eyebeam.org/projects/radiant-partatts/browse > > > Thank you to Jaime for setting this up. > Jacob, Is there a public URL to check that out? I found this link referenced for svn https://dev.eyebeam.org/svn/ radiant-partatts but it requires svn user to authenticate. dm ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Facets branch extensibiliy extended
If you guys would like to keep up with my "usecase" for the facets changes I proposed, you can now take a look at: http://dev.eyebeam.org/projects/radiant-partatts/browse Thank you to Jaime for setting this up. Hopefully this will eventually morph into a the repository for Just the partatts extension. (And supplemental TinyMCE and FCKEditor extensions) Currently, it maintains a full version of radiant (modified facets) as well. I am more interested in making the Radiant a powerful platform, than I am in simply getting my changes checked in to core. If you guys can come up with a better API for supporting multiple page editors, I'll be happy to port my extension over to use it. Using my API as a base, and improving it. Is also a possibility I encourage. Also... perhaps we should come up with a convention for extension including static files. It's no big deal to have to copy the fckeditor javacripts into public to get the extension to work, but perhaps there should be an official standard. public/extensions//etc... for example. Jacob -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] default options
David Minor wrote: > so what does the dev.host config option do? It allows you to preview "draft" pages: http://dev.radiantcms.org/radiant/wiki/HowToDevAndProduction -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
