Is it possible to put the sliding region to the default theme, so I can switch back to admin pages by using a link from the sliding region?
right now I have to leave an administer link in one of the blocks of the homepage theme to switch to admin theme/RootCandy.
Right now I'm torn between "admin" and "rootcandy", but I like root candy better, because it doesn't steal my custom blocks ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | rootcandySlider.tar_.gz | 8.12 KB | maulwuff |
| #5 | rootcandySliderRegions.tar_.gz | 8.1 KB | maulwuff |
| #4 | rootcandySlider.png | 15.09 KB | maulwuff |
| #3 | rootcandySlider.tar_.gz | 7.96 KB | maulwuff |
Comments
Comment #1
maulwuff commented"admin" module demands me to put
right after the body tag to get the admin-bar shown. Would there be an similar approach for root candy?
Comment #2
sign commentedno, there is no simple way how to do this with rc right now, but it might be a good feature actually
Comment #3
maulwuff commentedI've built a small module adapted from the admin module, which adds the slider to the main theme.
Would you mind maintaining this module? I can do it, too, but it's very dependent on rootcandy development.
Right now all slider parts are doubled (panel html, css, panel images). At first I thought, that's not good at all, but it leaves the user free to modify the slider when displayed on the main theme. I.e. it makes no sense to overlap the content of the page (position:absolute), if the slider is only visible when scrolled to the top. So I switched it to position:relative, but inside rootcandy it's still position:absolute. ;)
Comment #4
maulwuff commentedsmall screenshot showing rootcandySlider on multiflex3
Comment #5
maulwuff commentedthis is a modified version to support regions in slider.
see #504370: Add regions to slider
Comment #6
maulwuff commentedComment #7
maulwuff commentedsupport rootcandy dark and rootcandy fixed, too.
Comment #8
sign commentedagain thank you!
wandering now, whether to place it into rootcandy contrib dir within this theme, or whether you should create a module contrib out of it? what are your thoughts?
Comment #9
maulwuff commentedI'm undecided ;)
It's easier for users to have a single package where everything is put in. But: I don't know if sites/all/themes/rootcandy/contrib/rootcandyslider will get recognized. On the other hand, there is some effort needed to get it working, because users have to modify their page.tpl.php to see the slider. Therefore they have to read the readme and copy the slider from rootcandy/contrib to sites/all/modules. So no real win of comfort.
A own module would be the clean way, but it's very dependant on rootcandy. I've seen that while implementing the addidtional regions. :)
I can't believe that this is such a hard decision *g*
Comment #10
sign commentedIt is indeed :)
I would suggest to make a module out of it? I'll link to it from rootcandy page and mention it on handbook page and so on.
Most of the people don't read README files btw. :)
Comment #11
maulwuff commentedallright, that seems to be the clean way.
Comment #12
sign commentedhi maulwuff,
how far did you get with this? :)
Comment #13
maulwuff commentedoh I thought you would create it, as you are the rootcandy maintainer.
Comment #14
ghosty commentedI like that you are using the slider in your main theme, but is there a way to include the menu with the icons in the main theme? Same kind of concept, but I guess this would have to be a module. What do you guys think?
Comment #15
sign commentedOk, finally had time to spend some time on this and here it is.
http://drupal.org/project/rootcandy_header
I am marking this as fixed now... all other issues should go into the rootcandy_header issue queue if they are related
@ghosty ^^ - but I doubt your idea will happen tho.
Comment #16
ghosty commentedI actually created my own module that shows the menu with the icons, so I'm all good now.