<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Released: DotNetNuke Templated Mega-Menu Provider</title>
	<atom:link href="http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/</link>
	<description>Observations about the intersection of technology, business, and intellectual property</description>
	<lastBuildDate>Wed, 21 Oct 2009 16:16:51 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: GR</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-2509</link>
		<dc:creator>GR</dc:creator>
		<pubDate>Tue, 22 Sep 2009 12:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-2509</guid>
		<description>Thank you very much... This is an amazing menu...</description>
		<content:encoded><![CDATA[<p>Thank you very much&#8230; This is an amazing menu&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-2495</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Fri, 28 Aug 2009 13:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-2495</guid>
		<description>As I mention in the discussion, this provider relies on the underlying DNN:Nav implementation for almost all of its (non-templating) functionality.  As such, I would expect that most anything that works without the adapter would also work WITH the adapter (barring a specific templating error).

That said, if I were in your shoes, I would ensure that the level and startTabId attributes are working properly with the underlying provider (by restoring your navigation provider settings to their original configuration); once you have tweaked these settings to your taste, re-adding the templating provider should produce a menu that works identically (save for the added templating features).

Hope this helps!

B</description>
		<content:encoded><![CDATA[<p>As I mention in the discussion, this provider relies on the underlying DNN:Nav implementation for almost all of its (non-templating) functionality.  As such, I would expect that most anything that works without the adapter would also work WITH the adapter (barring a specific templating error).</p>
<p>That said, if I were in your shoes, I would ensure that the level and startTabId attributes are working properly with the underlying provider (by restoring your navigation provider settings to their original configuration); once you have tweaked these settings to your taste, re-adding the templating provider should produce a menu that works identically (save for the added templating features).</p>
<p>Hope this helps!</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GR</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-2490</link>
		<dc:creator>GR</dc:creator>
		<pubDate>Mon, 24 Aug 2009 22:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-2490</guid>
		<description>Excellent menu. Thank you very much.

If I want to start from level=&quot;child&quot;, this doesn&#039;t work. Is there a way where I can make it work from any level? I want to use Level=&quot;Child&quot; StartTabid=&quot;39&quot; in the dnn:nav tag. 

Please let me know your suggestions.

Thanks once again,
GR</description>
		<content:encoded><![CDATA[<p>Excellent menu. Thank you very much.</p>
<p>If I want to start from level=&#8221;child&#8221;, this doesn&#8217;t work. Is there a way where I can make it work from any level? I want to use Level=&#8221;Child&#8221; StartTabid=&#8221;39&#8243; in the dnn:nav tag. </p>
<p>Please let me know your suggestions.</p>
<p>Thanks once again,<br />
GR</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-2163</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Wed, 15 Jul 2009 13:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-2163</guid>
		<description>Hi Hardik,

Take a look in the Providers/TemplatedDNNMenuNavigationProvider directory for the sample templates that come with the provider; there you may copy one (and then instantiate it by name), or less optimally modify the template itself.

Since these templates are simple ASCX/HTML markup (e.g. Default.ascx) and CSS styling (e.g. Default.css), virtually any visual presentation format is possible.  In your case, you might want to use two unordered lists; one with the first ten elements floated left, and the rest floated right.

Hope this helps!

B</description>
		<content:encoded><![CDATA[<p>Hi Hardik,</p>
<p>Take a look in the Providers/TemplatedDNNMenuNavigationProvider directory for the sample templates that come with the provider; there you may copy one (and then instantiate it by name), or less optimally modify the template itself.</p>
<p>Since these templates are simple ASCX/HTML markup (e.g. Default.ascx) and CSS styling (e.g. Default.css), virtually any visual presentation format is possible.  In your case, you might want to use two unordered lists; one with the first ten elements floated left, and the rest floated right.</p>
<p>Hope this helps!</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hardik</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-2160</link>
		<dc:creator>Hardik</dc:creator>
		<pubDate>Wed, 15 Jul 2009 11:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-2160</guid>
		<description>Hi Brandon,

Can I control the number of menu items per line in mega-menu. E.g. I need to display only 10 menu items in first line and the remaining menu items in second line ?

Thanks
Hardik</description>
		<content:encoded><![CDATA[<p>Hi Brandon,</p>
<p>Can I control the number of menu items per line in mega-menu. E.g. I need to display only 10 menu items in first line and the remaining menu items in second line ?</p>
<p>Thanks<br />
Hardik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1747</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Tue, 23 Jun 2009 13:35:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1747</guid>
		<description>Hi Greg,

The DotNetNuke Nav control, which is the control (typically) utilized by skins to display the menu, automatically initializes the navigation provider with the page hierarchy.  This means that you&#039;ll be out of luck using it to display non-page-hierarchy content (without some sort of ugly kludge, anyway).

Unfortunately, DotNetNuke does not really include any control that will accomplish what you&#039;re looking to do.  Your recourse here is to reproduce the behavior in the Nav control and provide your own menu element hierarchy, or roll-your-own user control (that presumably would do the same thing).

Assuming you do so, I do not see any reason that you could not utilize templated menuing to accomplish a mega-menu-style display; there might, however, be a bit of custom skinning CSS that would be required.

Hope this helps!

B</description>
		<content:encoded><![CDATA[<p>Hi Greg,</p>
<p>The DotNetNuke Nav control, which is the control (typically) utilized by skins to display the menu, automatically initializes the navigation provider with the page hierarchy.  This means that you&#8217;ll be out of luck using it to display non-page-hierarchy content (without some sort of ugly kludge, anyway).</p>
<p>Unfortunately, DotNetNuke does not really include any control that will accomplish what you&#8217;re looking to do.  Your recourse here is to reproduce the behavior in the Nav control and provide your own menu element hierarchy, or roll-your-own user control (that presumably would do the same thing).</p>
<p>Assuming you do so, I do not see any reason that you could not utilize templated menuing to accomplish a mega-menu-style display; there might, however, be a bit of custom skinning CSS that would be required.</p>
<p>Hope this helps!</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1736</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Mon, 22 Jun 2009 21:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1736</guid>
		<description>Brandon-

I want to have mega-menu as a module so I can use Live Content to pop-up my site menu with one button. Any ideas of how I could go about doing this?

Thanks
Greg (@leazon)</description>
		<content:encoded><![CDATA[<p>Brandon-</p>
<p>I want to have mega-menu as a module so I can use Live Content to pop-up my site menu with one button. Any ideas of how I could go about doing this?</p>
<p>Thanks<br />
Greg (@leazon)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francisco Pérez Andrés</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1627</link>
		<dc:creator>Francisco Pérez Andrés</dc:creator>
		<pubDate>Mon, 15 Jun 2009 10:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1627</guid>
		<description>Does anyone know any menu, for DNN 4, quite similar to this. It&#039;s a great extension but I&#039;m afraid we still have a few months before we can set DNN 5 for production sites.

TIA,
Francisco</description>
		<content:encoded><![CDATA[<p>Does anyone know any menu, for DNN 4, quite similar to this. It&#8217;s a great extension but I&#8217;m afraid we still have a few months before we can set DNN 5 for production sites.</p>
<p>TIA,<br />
Francisco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1585</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Wed, 10 Jun 2009 16:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1585</guid>
		<description>@Ely: While I understand and agree with your reasoning here, this package is designed to be a simple extension to the existing DNNMenu provider.  Unfortunately, it appears that that this base menuing system does not deal well with a hierarchy of HTML as element children (and indeed this was likely an unforeseen use-case on their part).  And while it would be generally out of scope for me to adjust the base behavior in any way, I&#039;ll have to think about how this shortcoming might be addressed.

@Noorin: This package is designed against DotNetNuke version 5.0.1 and higher.  It will not work out-of-the-box for pre-5.0.1 installations.  However, I believe that the overwhelming majority of the differences will be simple changes between deprecated calls and there is little post-version-5 functionality that is being taken advantage of here.

If you urgently require a 4.x install, I suggest downloading the code and compiling a custom version against the 4.x line.  I think it will be fairly straightforward (but I will be unable to offer specific guidance in this particular process).

Otherwise, I suggest considering an upgrade to 5.1 in the near future.  It is looking to be a highly stable distribution.

B</description>
		<content:encoded><![CDATA[<p>@Ely: While I understand and agree with your reasoning here, this package is designed to be a simple extension to the existing DNNMenu provider.  Unfortunately, it appears that that this base menuing system does not deal well with a hierarchy of HTML as element children (and indeed this was likely an unforeseen use-case on their part).  And while it would be generally out of scope for me to adjust the base behavior in any way, I&#8217;ll have to think about how this shortcoming might be addressed.</p>
<p>@Noorin: This package is designed against DotNetNuke version 5.0.1 and higher.  It will not work out-of-the-box for pre-5.0.1 installations.  However, I believe that the overwhelming majority of the differences will be simple changes between deprecated calls and there is little post-version-5 functionality that is being taken advantage of here.</p>
<p>If you urgently require a 4.x install, I suggest downloading the code and compiling a custom version against the 4.x line.  I think it will be fairly straightforward (but I will be unable to offer specific guidance in this particular process).</p>
<p>Otherwise, I suggest considering an upgrade to 5.1 in the near future.  It is looking to be a highly stable distribution.</p>
<p>B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noorin</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1584</link>
		<dc:creator>Noorin</dc:creator>
		<pubDate>Wed, 10 Jun 2009 15:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1584</guid>
		<description>Hi Brandaon,

This is a great menu! But is it only for DNN 5.x? Or does it support DNN 4.x also? I tried installing it in DNN 4.9.4 but I was not successful. Could you please give me details on this? It is quite urgent because if this is not supported in DNN 4.x, I&#039;ll have to look for some other third party control.

Thanks!

-Noorin</description>
		<content:encoded><![CDATA[<p>Hi Brandaon,</p>
<p>This is a great menu! But is it only for DNN 5.x? Or does it support DNN 4.x also? I tried installing it in DNN 4.9.4 but I was not successful. Could you please give me details on this? It is quite urgent because if this is not supported in DNN 4.x, I&#8217;ll have to look for some other third party control.</p>
<p>Thanks!</p>
<p>-Noorin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ely</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1428</link>
		<dc:creator>Ely</dc:creator>
		<pubDate>Thu, 04 Jun 2009 08:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1428</guid>
		<description>Hi Brandon,

Just installed your release. What I noticed is that the menu is not stable when you use the tab key. I can tab to the menu and when I use my arrow down key the menu pops open. When I tab to the submenu&#039;s the menu dissapears.

Tabable menu&#039;s are very important because blind people who use screenreades use that function to read the menu.

Can you take a look at this ? I hope u understand, of you have any questions please feel free to ask.

Regards,
Ely</description>
		<content:encoded><![CDATA[<p>Hi Brandon,</p>
<p>Just installed your release. What I noticed is that the menu is not stable when you use the tab key. I can tab to the menu and when I use my arrow down key the menu pops open. When I tab to the submenu&#8217;s the menu dissapears.</p>
<p>Tabable menu&#8217;s are very important because blind people who use screenreades use that function to read the menu.</p>
<p>Can you take a look at this ? I hope u understand, of you have any questions please feel free to ask.</p>
<p>Regards,<br />
Ely</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Haynes</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1343</link>
		<dc:creator>Brandon Haynes</dc:creator>
		<pubDate>Mon, 01 Jun 2009 17:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1343</guid>
		<description>I have updated the documentation to indicate that the plural &quot;Descriptions&quot; should be used in the meta content tag (where it was previously incorrectly indicating that the singular should be used); I believe that this will remedy this issue.

I do not believe that the distribution contains any hard-coded template files, so the release will not need to be meaningfully updated otherwise.

Thanks for that report CPG.  It is greatly appreciated.

Brandon</description>
		<content:encoded><![CDATA[<p>I have updated the documentation to indicate that the plural &#8220;Descriptions&#8221; should be used in the meta content tag (where it was previously incorrectly indicating that the singular should be used); I believe that this will remedy this issue.</p>
<p>I do not believe that the distribution contains any hard-coded template files, so the release will not need to be meaningfully updated otherwise.</p>
<p>Thanks for that report CPG.  It is greatly appreciated.</p>
<p>Brandon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cpg</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1342</link>
		<dc:creator>cpg</dc:creator>
		<pubDate>Mon, 01 Jun 2009 17:32:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1342</guid>
		<description>Under /Providers/TemplatedDNNMenuNavigationProvider/, your provider zip file contains Descriptions.ascx, but when you apply the templated skin, it gives an error saying it can&#039;t find Description.ascx -- with no &quot;s&quot;. I just removed the s from the filename and it worked. Please fix in your distribution files.

I haven&#039;t had much chance to play with this but I have hopes. It looks great. thank you for you efforts.</description>
		<content:encoded><![CDATA[<p>Under /Providers/TemplatedDNNMenuNavigationProvider/, your provider zip file contains Descriptions.ascx, but when you apply the templated skin, it gives an error saying it can&#8217;t find Description.ascx &#8212; with no &#8220;s&#8221;. I just removed the s from the filename and it worked. Please fix in your distribution files.</p>
<p>I haven&#8217;t had much chance to play with this but I have hopes. It looks great. thank you for you efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dax Davis</title>
		<link>http://blogs.law.harvard.edu/brandonhaynes/2009/05/31/released-dotnetnuke-templated-mega-menu-provider/comment-page-1/#comment-1340</link>
		<dc:creator>Dax Davis</dc:creator>
		<pubDate>Mon, 01 Jun 2009 15:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/brandonhaynes/?p=115#comment-1340</guid>
		<description>Very cool extension.  Thanks a lot!</description>
		<content:encoded><![CDATA[<p>Very cool extension.  Thanks a lot!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
