I thought about doing something similar with a few “features” actually. I ran into an issue, however, when the toolbar was positioned on either the left or right side because text wouldn’t fit in the small width. I chose to keep the consistent UI with the fly-out boxes on all toolbars.
If the status displays were icons with a popup caption for legend and a fly-out for setting, it would work in any orientation surely? Or have I missed something?
If the status displays were icons with a popup caption for legend and a fly-out for setting, it would work in any orientation surely? Or have I missed something?
I thought you were suggesting to put the text value of the status directly in the toolbar rather than in any pop-up/fly-out. What is your suggestion? (sorry for the confusion)
I just wanted to mention that the font size shows up HUGE for me. Adding:to the stylesheet on line 89 took care of that.font-size: 1em;
Hmm, good to know. I haven’t had it show up huge in any of my sites but I’ll certainly take your suggestion into consideration and set a default font size. Did you use any versions prior to 1.1.0? Did they not have a font size problem in the same EE install?
I just wanted to mention that the font size shows up HUGE for me. Adding:Hmm, good to know. I haven’t had it show up huge in any of my sites but I’ll certainly take your suggestion into consideration and set a default font size. Did you use any versions prior to 1.1.0? Did they not have a font size problem in the same EE install?to the stylesheet on line 89 took care of that.font-size: 1em;
I’ve tried 1.0 and 1.1 and they were all huge for me. Looks like in my case it inherits the reset stylesheet’s 100% font size otherwise, where I have the body font set to 62.5%. The 1em setting changes the inheritance.
I’ve tried 1.0 and 1.1 and they were all huge for me. Looks like in my case it inherits the reset stylesheet’s 100% font size otherwise, where I have the body font set to 62.5%. The 1em setting changes the inheritance.
Yeah I was specifying the font size on the parent div rather than the actual paragraph and anchor tags. I’ve tweaked this for the next update. Thanks 😊
I thought you were suggesting to put the text value of the status directly in the toolbar rather than in any pop-up/fly-out. What is your suggestion? (sorry for the confusion)
My suggestion was - is now 😊 - to show those 4 status indicators as individual icons on the toolbar, the icon reflecting the on/off, 1/2/3 state of the indicator.
Hovering over the icon would display a legend indicating what the icon represented (and/or it’s current state?). Clicking the icon would display a fly-out allowing the state to be changed (my preference would be clicking the icon toggled it’s value, but one is 3-valued - boo!)
…to show those 4 status indicators as individual icons on the toolbar, the icon reflecting the on/off, 1/2/3 state of the indicator.
Okay I’m with you now. So your suggestion is to place them on the toolbar itself and not a level deep to “save mouse clicks”? If I’m not mistaken this still requires the same amount of movement on your mouse…
…to show those 4 status indicators as individual icons on the toolbar, the icon reflecting the on/off, 1/2/3 state of the indicator.Okay I’m with you now. So your suggestion is to place them on the toolbar itself and not a level deep to “save mouse clicks”? If I’m not mistaken this still requires the same amount of movement on your mouse…
It saves ‘mousing’ of all sorts as the statuses are visible directly, So it is viewing an icon directly rather than mousing over to a label and sliding down, to change status requires the same movement/clicks.
Where can I change the “system” folder name?
Try going to Admin > System Preferences > General Configuration and looking for “URL to your Control Panel index page”. There’s also a chance it was set in your path.php file so you might want to check there if the General Config setting doesn’t do the trick.
Chris and I chatted about the issue and he can now see the toolbar. We narrowed it down to his authentication on the front end not being correct. He wasn’t recognized as logged in due to cookie/domain conflicts. If anyone runs into that check something simple like turning on Template Debugging and if you can’t see it on the front end then you aren’t a logged super admin.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.