Mega Menu is here

Permalink 1 user found helpful
I've seen a lot of talk about mega menus in the forum. No need to wait any longer! I've created a new C5 Mega Menu add-on. It's awesome and currently waiting for marketplace approval (hopefully within a week). You can find the full details and a couple videos at:
http://c5extras.com/add-ons/mega-menu/...

If you really need it now and can't wait a week, just pm me to purchase it directly. I've got lots of existing add-ons in the marketplace and fantastic reviews. So you're guaranteed to love it.

JB

jb1
 
hursey013 replied on at Permalink Reply
hursey013
Looking forward to this - thanks.
jb1 replied on at Permalink Reply
jb1
The wait is finally over. Check it out:
http://www.concrete5.org/marketplace/addons/mega-menu/...

Enjoy!
naresh replied on at Permalink Reply
naresh
Hi

Just now i purchased this, not sure how to add it to my site, i am not able to find it anywere, please help I am new to Concrete5
jb1 replied on at Permalink Reply
jb1
Hi, you can find installation help on the C5 website at:
http://www.concrete5.org/marketplace/how_to_install_add_ons_and_the...

If you're still stuck, just open a support ticket by visiting the marketplace page:
http://www.concrete5.org/marketplace/addons/mega-menu/...
and click "support" on the right side.

Hope this helps.

JB
JohnTurner replied on at Permalink Reply
JohnTurner
I just bought Mega Menu Vertical and really like it. One thing that I notice though that seems not to work is the "preview" tab. If I edit the menu and hit the "preview" tab, it give me a "fatal error." But, the menu works fine.

I am also interested in having the menu highlight the current page. So, even though the menu would close when not in use, it would hightlight the visible blocks so that users could see where they are on the website. Just a thought.
jb1 replied on at Permalink Reply
jb1
Thanks for the message. This has been answered via support ticket.
boomgraphics replied on at Permalink Reply
boomgraphics
I have ported all of Design Chemical's javascript logic into php (plus quite a bit more), except the margin calculations which can only be done via javascript.

I was thinking that a useful function would be to write a parser that dynamically creates an array for block themes (not templates). It would scan the database's installed themes for any folder that matches the block name, and then list those themes in the block's settings panel like you have it now, but not hard coded. That way it would be trivial to create a new theme and allow it to be used in a global menu block. At least until global blocks work properly and pull their own assets.

Thoughts?

PS. Design Chemical's js script generates some invalid html... I attempted to tell the dude who wrote it on his site, but they deleted my comment. :-(
It is an easy fix though. At least in the php side.
jb1 replied on at Permalink Reply
jb1
Hi, thanks for the feedback. I'm not quite sure if I understand exactly what you're suggesting - are you talking about creating a new custom skin for the Mega Menu or theming add-on blocks?

I've been made aware of a little known function called "autoAddHeaderItems" but haven't had time to test it out yet. Here's a link to the forum discussion:
http://www.concrete5.org/developers/pro-accounts/community-leaders-...
boomgraphics replied on at Permalink Reply
boomgraphics
lol I read that thread you mentioned and it is quite vague. The function I have been throwing about in my head is something that queries the database to find all installed themes (actual site themes, not block themes), and then checks each installed theme directory for a predefined folder structure.

It would be something like themes/block_name/block_template_name/theme_name/assets .css | .jpg | .js |etc

Then it would dynamically list all the theme_name folders categorized by the template it affects, and find its thumbnail image.

That way all themes would be listed in a sort of gallery in the block edit dialog. When you click on a block theme, its url would be submitted into the database, and those assets added to the header when the page is viewed. This eliminates the global block issue, and also provides a nice interface for themes that are compatible with that particular view.php template.

It would also be trivial to create a configuration .txt file for easy designer access to theme specific options. For instance, my view dynamically counts rows and columns, adds html around each second level dropdown, checks for more than 11 attributes, does dynamic image cropping and positioning, creates an optional accesskey legend, uses 28 separate classes for different things, etc. I think it would be fantastic to be able to configure the menu for a specific theme, rather than go into the code and foul things up even more. Something like eliminating classes that aren't needed, specifying the html around each element, etc.

I want to begin coding a class that allows for easy creation of config options to check for, and that also finds and displays all installed themes for all available templates.

Thoughts?
jb1 replied on at Permalink Reply
jb1
I like your ideas, some good concepts there. I try to keep my add-ons as simple as possible, but still flexible for as many possible uses. The reality is that I don't get rich from making add-ons for C5, it's something I enjoy doing in my spare time and have to run a web design business full-time. If there was a bigger market for C5 add-ons it would be worth spending more time fleshing out this kind of thing. But in all honesty, the return on investment isn't there for me to spend dozens of hours doing advanced features that only a relatively small number of c5 members would use.

In saying that, if you had the time and desire to create the code for it, I'd be happy to incorporate it into Mega Menu. Or if you even wanted to sell an add-on for it, I'd be happy to support it. Alternatively, if you wanted to make a tutorial video or release free code I can link to it from the C5 marketplace listing.
boomgraphics replied on at Permalink Reply
boomgraphics
PS. This would also make it trivial for site theme designers to include many block themes with no extra fussing around with php.