Hi Everyone,

I used Edwin's suggestion to overcome the problem by adding an empty 
page part to the stylesheet and then using the <r:unless_content 
part="no_menu"> tag to determine which pages should be added to the main 
menu.  That works fine.

I also followed the extensions tutorial to create an extension that 
allows you to create properties.  That portion works, but I don't yet 
know how to add properties to specific pages :-S (the extensions 
tutorial doesn't work on per-page properties) so I'm not yet sure how to 
go about it.  But I hope that I'll find out some more by looking at some 
other extensions.

Cheers,
Mohit.
8/3/2007 | 4:59 PM.


Mohit Sindhwani wrote:
> Hi Keith
>
> Thanks for the suggestion and the link.  I've seen the tutorial for the 
> extension before and I think it has incredible detail on how to go about 
> doing something like this.  So, I shall follow that through and as for 
> advice again if I run into something.
>
> Cheers
> Mohit.
>
> Keith Bingman wrote:
>   
>> I would do this in an extension. John has a very nice tutorial 
>> at 
>> http://www.radiantcms.org/blog/archives/2007/06/23/tutorial-creating-radiant-extensions/
>>  
>>
>> This should get you going. In short, radiant has extension generators 
>> that work like the normal rails generators. 
>>
>> Keith Bingman
>> [EMAIL PROTECTED]
>> Tel: +49-7731-7983830
>>
>>
>>
>> On Aug 3, 2007, at 8:29 AM, Mohit Sindhwani wrote:
>>
>>     
>>> Thanks Keymone,
>>>
>>> I have my work cut out for the weekend now.  I think this will also give 
>>> me the chance to try out adding a Rails model to a Radiant site 
>>> (something I haven't yet done).
>>>
>>> Do I create the model in the same way as a regular Rails app?  In the 
>>> root of the Radiant directory, I just go
>>> [#]script\generate model .....
>>>
>>> Thanks for your help.
>>>
>>> Cheers,
>>> Mohit.
>>> 8/3/2007 | 2:27 PM.
>>>
>>>
>>> Keymone wrote:
>>>       
>>>> maybe there is a reason to implement page properties?
>>>> using page parts for that can cause huge overhead
>>>>
>>>> it's better (and more obvious) to type
>>>> <r:if_content property="hide from menu"> </r:if_content>
>>>>
>>>> on rails side you only have to add Property model
>>>> and give Page has_many :properties
>>>>
>>>> there will be "properties" tab on page edit and user should be
>>>> able to add properties specifying property name and property
>>>> value. to improve performance of SQL queries properties can
>>>> also have type attribute e.g. int, string, date and properties
>>>> inheritance between pages.
>>>>
>>>> On 8/2/07, * Mohit Sindhwani* <[EMAIL PROTECTED] <mailto:[EMAIL 
>>>> PROTECTED]>> 
>>>> wrote:
>>>>
>>>>     Hi Edwin,
>>>>
>>>>     Thank you for the suggestion.  I'm still new to the tags in
>>>>     Radiant, but
>>>>     I shall keep a lookout for the unless_content tag.
>>>>
>>>>     I'm still a bit confused about how to use your suggestion, but
>>>>     I'll try
>>>>     a few things and hopefully stumble on the correct meaning! :)
>>>>
>>>>     Cheers
>>>>     Mohit.
>>>>
>>>>
>>>>     Edwin Vlieg wrote:
>>>>         
>>>>> Hi,
>>>>>
>>>>> I always overcome this problem by adding an empty page part to the
>>>>> stylesheet. By using the <r:unless_content part="no_menu"> tag
>>>>>           
>>>>     you can
>>>>         
>>>>> determine which pages should be added to the main menu.
>>>>>
>>>>> Edwin
>>>>>
>>>>> Op 2-aug-2007, om 11:32 heeft Mohit Sindhwani het volgende
>>>>>           
>>>>     geschreven:
>>>>         
>>>>>> Hi Everyone,
>>>>>>
>>>>>> After being away for a while, I'm now taking a few days to play
>>>>>>             
>>>>     with
>>>>         
>>>>>> Radiant again in the hope of migrating one of my static sites to
>>>>>> Radiant.  In my 'Hello World' example that I uploaded as a
>>>>>>             
>>>>     tutorial, I
>>>>         
>>>>>> created a stylesheet as a child of the main page and then used
>>>>>>             
>>>>     that for
>>>>         
>>>>>> styling the main page as well as any of its children.
>>>>>>
>>>>>> Now, I've run into this problem.  If I try to iterate through the
>>>>>> children of the main page to create a list of links to the
>>>>>>             
>>>>     children, it
>>>>         
>>>>>> obviously also creates a link to the stylesheet.  I'm sure that
>>>>>>             
>>>>     there is
>>>>         
>>>>>> a simple way to avoid it, but I think I'm too green just yet. :-|
>>>>>>
>>>>>> Thanks for the help.
>>>>>>
>>>>>> Cheers,
>>>>>> Mohit.
>>>>>> 8/2/2007 | 5:32 PM.
>>>>>>             
>>>>>           
>>>>     _______________________________________________
>>>>     Radiant mailing list
>>>>     Post:   [email protected]
>>>>     <mailto:[email protected]>
>>>>     Search: http://radiantcms.org/mailing-list/search/
>>>>     Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Regards, Keymone 
>>>>         
>>>       


_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to