Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Please see the attached txt file to get the CSS for the "blue" skin.
Comment | File | Size | Author |
---|---|---|---|
#3 | megamenu_skin_blue.patch | 2.83 KB | silverfly |
megamenu-skin-blue.txt | 1.5 KB | silverfly |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedI'm changing the title to "Skin Contributions" so other designers can post skins here. Thanks Nick :-)
Comment #3
silverfly CreditAttribution: silverfly commentedI re-rolled this skin as a patch against 6.x-2.0-ALPHA1. This patch includes a fix to IE7 - the parent items were not displaying inline.
Comment #4
avenir CreditAttribution: avenir commentedHow can I use it with megamenu.Please give me an idea here how to use the patch.
Comment #5
drwierdo CreditAttribution: drwierdo commentedUsing 7.x-dev of megamenu.
I want to upload my own own skin for use with megamenu. In the readme, it says that there are two options for doing this, one is to follow the on-screen direction to upload the skin and the other is to css the theme. Now i was looking for the former option, trying to keep the theme clean. But unfortunately, i am not shown any on-screen uploading option.
All i want to know is where should i keep the custom skin???
Comment #6
asb CreditAttribution: asb commentedInteresting question, as it seems to accept only the default theme's folder, not an optional one.
Also it says: "Type in the name of your custom skin (This will become a class value applied to the menu: megamenu-skin-[skin name]), and should be referenced in your custom CSS."
So if we have something like
.megamenu-skin-blue .megamenu-parent h2 a:hover {}
, the custom skin file would need to be labeled as "blue.css". Too bad that this file is ignored. Probably I don't grok the concept behind this :-(Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedWe removed the option to upload a CSS file into the files folder after the first beta. For one, it wasn't a very logical place for keeping CSS files, especially if one is building a site with version control and ignoring the files folder. Secondly, there were issues with the order in which CSS files are loaded. Theme CSS files are loaded after module CSS files, which made it difficult for skin rules to exhibit more specificity. For those reasons, all CSS is now handled in your theme.
What you put in the box for the name of your custom skin, will simply be a class applied to the menu. You can put rules that target that class in any CSS of your liking as long as it is loaded by your theme.