Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About red

  • Rank

Profile Information

  • Gender
  1. There is a rough sample of what's going on at saczee.com/ZTEST/build20-11.html Pay little attention to the code, though. It deliberately violates "best practices" and is less than half done. It simply gives an idea of what the mega-menu structures are intended to do. Also keep in mind, the positions and sizes of the mega-panels are not fixed - and will change from edition to edition (of an online newspaper). The solution, if there is one, must be something that works independent of other features of containers and their styling. It needs to pretty much confine itself to matters of visibi
  2. Thanx Dave. I hope you had this on hand, and didn't have to make it up special. The question I have is about cookies. I don't want to store anything longer that the visitor/s session to the site (though that may include their visit to other pages) - the announcement window will only appear on the single 'home page'. After the visitor ends the session, the information should disappear. If they come back, they'll just have to see the announcement again. (we've promised our users there would be no cookies.) Will setting the expire time to '0' or '1' do that? or do I need to do something el
  3. I need a window on loading a page. No need to build one for me if someone knows where there's a script that is relatively safe and simple (as possible). I have no java, limited css, Here's what I'd like: - when I have an announcement to make, the window will superimpose on the page (i can activate when needed or comment out when not in use). - it should be css styleable in general features - height/width/position, fonts/sizes, color, borders, that sort of thing) - should have one of those 'x' close options in its upper right corner; [Optional, but nice:] -- has a semi-transparent ba
  4. okeydoke - just a bad idea. sorry to bother.
  5. yeah, not making myself too clear. I'm using 'layout' in the general sense (not the one that's argued about endlessly all over the net - 'layout', 'semantic', 'content', 'form', etc. blah...) Just the sense in which all the different "coding compartments" have to cooperate to make it all work. In that, the order of parts of the markup are as relevant as the cascade of css, and so forth. I mean "layout in the sense of saying in a nonspecific way "I'm trying to have a layout that looks like this, and accommodates that, and such -- not particular code problems, but more generic questions about a
  6. What would people think about a forum to discuss general layout approaches and solve general layout problems? Not that it wouldn't have specific coding and script solutions suggested for specific layout issues; but that we might be a little freer to discuss overall layout designs and how they might best be approached? Something less restricted to particular types of coding problems, too (css, html, js, etc.)I've had fantastic help here solving some vexing problems. But I also know that my layout is only about 59% of what I really started out wanting it to be.. I don't really feel free to disc
  7. I did find that its the column1-2 box that's masking the rest the page when i turn off the floats on that and the target article. If i apply a negative z-index to the column block the page reappears. but, of course, the target column and target article disappear. I don't know if that helps. I don't understand what's happening.
  8. As I guessed, there were more little float problems - worked them out. But one, in particular seems plain weird. It's a new, simpler layout for inside pages -- 2 columns and a side bar - same wrap&nest arrangement - an outer-wrap, left/right panels and inside that column boxes and then article boxes. the last 2-column/single-article container on the page I wanted to have wrap around the previous, longer right column above it (like wrapping text around a right-floated image.) What happened was that the last box on the page, a 2-column block with a single article in it, was doing the dro
  9. Yes, I see. Not that I know spit about js, but I coded in C and Pascal and Lillith & such, and the structures are familiar. I'll light it up tomorrow and see how it works (you've been right on the money so far, so I've no doubt it does the trick). Don't quite understand why the order of the hidden/visible button declarations should be important, but I take your word they are. &ya, display:none redundant. A habit from the old days (real old days) when I coded critical VLIS systems on which people's lives depended. We'd reassert global statements all over the place just to be damn sure
  10. yes, thank you, that seems to work. I also found that slightly decreasing the width of the 2-column block helped some. It was pinching column3 between itself and the parent panel. I take it that its always good to leave a little wriggle room when doing these side-by-side floats. It still intuitively puzzles me a little though. I would have thought that a sibling box, sensing insufficient space remained to the right, would have floated itself to the next available left-top flow position of its parent rather than clinging below its sibling. Well I'm sure I'll encounter other puzzles, it's all
  11. Problem: contained boxes will float horizontally, but will not rise vertically into spaces large enough to accommodate them.- relatively positioned floats that stick to the bottom of an existing box (column) and refuse to float into available space. layout: a simple responsive, 3-column (left) + right sidebar layout that mimics common newspaper layouts. uses: main page wrap, left/right panel divs, left-panel gets 3 column containers sized to fit side-by-side in which each will contain some n-number of separate articles. some articles (columns) will span 2 or even 3 columns in the layout (i
  12. Hmm, thanx for the tool tip. Didn't even know that was there. Useful. &ya, it's "z-index" isn't it. slipped my mind, & I've been using z-index for years. Ah, where did I put my Aricept?
  13. understood. It's fine for me when no data is sent from either button on check->uncheck on the visible one - I simply treat empty data returns as a 'not checked'. I've tested it on all four cases (both-checked/only one-checked/both=unchecked/ and they all return correct data via my fm php. As I said, The only problem I can see is the need to double click the second button if the first has been toggled. And that, I take it, has to do with the script not knowing (preserving) which button the data came from. So I'm still wondering if the simple and most straightforward way to handle that is
  14. If I put a couple of properties in the style section of my html page, they work fine. If I take those same two rules and put them at the beginning or end of an external stylesheet (which is otherwise working fine) they do not work. Some conflict somewhere -- and no, putting "!important" or the display property on them doesn't help either. Identical css, just placed in different locations. ( If I put it on both the html and the external css, it also works -- as I expected it would). Here's the snippet: its to permit visible box borders in selected text..story.box{ /* limit to se
  • Create New...