Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Ekkk - I just looked today for the first time:
Comment | File | Size | Author |
---|---|---|---|
#19 | bartik-929440-v2.patch | 905 bytes | jensimmons |
#15 | snapshot2.png | 33.82 KB | threewestwinds |
#13 | bartik-967132.patch | 811 bytes | jensimmons |
#7 | demoblks.png | 53.67 KB | dcrocks |
#7 | demoblks2.jpg | 97.41 KB | dcrocks |
Comments
Comment #1
rjgoldsborough CreditAttribution: rjgoldsborough commentedHere's a patch to start things off. A less alerting color but still gets the point across I think. Also, I thought the header region looked better and made more sense to be full width. After all, the header is more than just the little block it shows now. I also thought the descriptions looked better centered. Also looks good across other color schemes.
Comment #2
threewestwinds CreditAttribution: threewestwinds commentedTested in Firefox 3.6, Chrome 7, and IE 8 against a fresh install of 7.x-dev. Makes the page look very much nicer, and the header block is more accurate about where blocks actually end up on the page. The changes are minor enough that I didn't feel the need to fire up more browsers than that.
The grey is somewhat hard to see against a white background, but still infinitely less eye hurting than the yellow it replaces.
Style in the new CSS meets standards.
Comment #3
Jeff Burnz CreditAttribution: Jeff Burnz commentedShould we make all the region names the same font, font size etc? The featured one looks the oddest having the text shadow.
Comment #4
threewestwinds CreditAttribution: threewestwinds commentedAgreed that the shadow looks a bit weird and the size should be standardized.
To be honest though, I'm not sure the proper way to set font-size in a situation like this. Using em or % inherits the size changes from the parent element (meaning either Featured doesn't shrink or the rest of the blocks do), but using an absolute size is bad for accessibility (since the size doesn't change properly in all browsers).
We could do a "#featured .page-admin-structure-block-demo .block-region" specific fix, but that feels like a hack to me, and would need to be fixed every time someone modified the #featured font size. Yuck.
I'll roll a patch if anyone can help me with how to make that change.
Comment #5
Jeff Burnz CreditAttribution: Jeff Burnz commentedUse a keyword, i.e.
A keyword font-size will lock the relative size to the browser default and scale with normal text re-sizing.
Comment #6
threewestwinds CreditAttribution: threewestwinds commentedMy first patch ever. Thanks for the tip on keyword font-size - you learn something new everyday.
Same as the last patch, plus two lines, one to remove the header text-shadow and another to set all the block-demos to a uniform "medium" text size.
Comment #7
dcrocks CreditAttribution: dcrocks commentedI don't know if this is the right place to put this but I just ran into a weird problem. On a vanilla 7.x-dev system dated 11/14, if bartik is not the default theme, when using admin/structure/blocks, the line " Demonstrate block regions(*theme name*) " never shows bartik, even though bartik is the theme whose block structure is currently displayed. See attached, where garland was the current theme but I was displaying bartik's blocks. The block structure of the current theme(garland) is displayed. If bartik is default, it works fine. If you choose another theme that is not default, it works fine. It only seems to have a problem with the 1st theme in the list, in my case bartik.
ps. Can the " Exit Block Region Demonstration " message be on a transparent background. If you have a region that displays top left, you can't see the label.
Comment #8
threewestwinds CreditAttribution: threewestwinds commentedA quick search on my part doesn't show anything about your problem - if you open a new issue, I'll try and take a look at it.
But not here - this is just a quick cosmetic fix. This shouldn't even be a bug report, I suspect, now that I think about it. I'll go with the handbook: "Feature Requests are for situations where the software works as designed, but the design can be improved. " (http://drupal.org/node/73179)
Comment #9
dcrocks CreditAttribution: dcrocks commentedIf I understand you correctly I need to create 2 new issues: a bug report about the "demonstrate regions" command, and a feature request about adding transparency to the "exit demonstrate regions" message.
Comment #10
threewestwinds CreditAttribution: threewestwinds commentedI did a little bit of looking at the block bug you mentioned - it's a Garland specific problem. At least, I think so - Analytic displays the region demonstration properly (http://drupal.org/project/analytic just happened to be the first theme I grabbed that defined additional regions).
Yes, two issues - one on the "block.module" component for the transparency request (that's where the CSS for the tab you'd like transparent resides), and one on the "Garland Theme" component for the improper regions demonstration.
I know they both sound like they belong here, but they're actually separate issues from different modules. ;)
Comment #11
dcrocks CreditAttribution: dcrocks commentedOk, I'll do the transparency issue, but I don't think the other is a garland problem. I tried other themes as well. If I can put it more generally, you can not use the the "Demonstrate Block Regions" command on any theme that appears first in the list of themes in the admin/structure/blocks overlay page if it is not the current default theme. Instead the regions for the default theme will be displayed. It appears that the 1st theme in the list is always the theme that was default when you logged in.
ps. After further checking, after caches are cleared, the current default theme is the 1st in the list and there is no problem. But I don't think you can expect people to clear cache every time they change the default theme.
Comment #12
jensimmons CreditAttribution: jensimmons commentedOk, everything in comment #7, 8, 9, 10, and 11 should not be on this issue. Let's keep talking about the original issue and comments #1–6 here. Please do not say anything else regarding comments #7–11. Open new issue(s) for that.
Comment #13
jensimmons CreditAttribution: jensimmons commentedBefore:
After:
Comment #14
tim.plunkettCode looks great, and the regions look even better.
Comment #15
threewestwinds CreditAttribution: threewestwinds commentedWhen I apply it, the header region stays narrow, and I don't see any lines in your patch that would have made it expand like your images.
I definitely prefer the yellow you reintroduced. It makes the blocks immediately visible, regardless of background. Am I missing something?
Comment #16
tim.plunkettI'm not sure how the header expanded for that screenshot, because it won't and shouldn't. After #845834: Fix Bartiks Header because its totally borked, that's where header is, and where blocks put in it will go. Any tweaking to get the header to stretch just for this page is too much.
So the screenshot is wrong, but the patch is right.
Comment #17
tim.plunkettOn second thought, this is worth a quick conversation with Jen. Will probably be right back to RTBC.
Comment #18
jensimmons CreditAttribution: jensimmons commentedHm, first an explanation about the latest patch. I'm here at BADCamp with webchick and timplunkett and we had a little chat about the design of these markers. Webchick was pushing hard for us to use a yellow very similar to what's there before this patch, since we are about to push D7 out the door, and it's too late for things the change the look to much. And I don't mind the yellow too much — the tan is prettier, but it blends into the theme too much. These markers need to jump off the page and let people know — hey this is not part of the theme, these are thingys marking where the regions are. So I came up with a new design. This new code provides markers that have:
And congrats to threewestwinds!!! Your first patch :D YEAH!!!!!!!!!!!! And yeah rjgoldsborough for working on this too.
Comment #19
jensimmons CreditAttribution: jensimmons commentedRe comment #15 — Great point. Here's new patch with a wider header marker.
When reviewing this patch, please put blocks in all the regions, and test to make sure this CSS doesn't affect the content on the page.
Comment #20
threewestwinds CreditAttribution: threewestwinds commentedTested blocks in all regions, no difference in appearance between patched and unpatched version except on the page in question.
Looks good to me.
Comment #21
tim.plunkettI second this.
Comment #22
jensimmons CreditAttribution: jensimmons commentedScreenshot of the last patch for webchick. Meow.
Comment #23
webchickCommitted #19 to HEAD. Thanks!