KevinM1

Wow, awesome post! Thanks a lot!

Months ago, I put one of my websites up for critique here (it's at http://www.francoamericancentrenh.com). The criticism I remember the most was 448191's rather blunt response to my "Please have JavaScript enabled" comment, which was along the lines of "I have JavaScript disabled, how is your navigation going to work?" Now, I know I can make flyout menus using pure CSS -- I've found a few on cssplay, but haven't put them in yet. That's not the point of this message, though. What I'm curious about is how to make sites that seem to require JavaScript, for whatever reason, function adequately if JavaScript isn't available. Is this even a concern with modern browsers and increasingly savvy users? Are there any design conventions to follow if you can forsee where not having JavaScript could be a problem? Any standard procedures to follow in those cases?

Well, I just tried every flavor of overflow, and the sizing problems remain. I don't think I'll ever be able to get evenly sized date cells with my current approach.

I've been reading through Deke McClelland's "Photoshop CS One-on-One," and it's been great. Definitely the best Photoshop resource I've found so far. He also writes the "Photoshop CS Bible." I'm wondering if it's basically a rehash of One-on-One, or if it fills a complimentary roll. If anyone out there owns both, should I consider buying the second?

Nope. Hint: it's from a TV show.

Is there anyway to enforce height, then? Maybe min/max-height?

Well, here's my line: It's a pretty famous one if you're a nerd. EDIT: fixed by ober... you forgot to close the quote.

This line is from one of the best movies of all time, Airplane.

Yup. My brother has one. It's also good for people who hike and whatnot. http://en.wikipedia.org/wiki/Global_Positioning_System

GPS = Global Positioning System. GPS is made up of satellites that orbit the Earth. If you have a GPS receiver, you can get your global coordinates (longitude and latitude). Modern GPS devices are very accurate, usually within a few feet/meters. Most modern cellphones have GPS capabilities so the police can find missing people. From what I gather, the original poster wants to 'borrow' another site's GPS info for his own use.

Here are my screenshots of the simple examples: http://www.nightslyr.com/ieexample.jpg http://www.nightslyr.com/ffexample.jpg As you can see, the cell height stretches to fit the text, which is what I don't want. The widths are uniform because the text is the same, but when the text is different, that becomes messed up too: http://www.nightslyr.com/ieliveversion.jpg http://www.nightslyr.com/ffliveversion.jpg I use the same td { width: 76px; height: 76px; overflow: auto; } CSS for the live version. EDIT: my OS chrome is just something one of my coworkers gave me...I am running XP.

Hmm..could it be a Windows XP thing, then? Because both IE7 and FF on my comp give me the same problem. With the simple example above, the widths of the cells are all approximately 76px, but their heights most definitely are not. I'll post a screenshot when I get to work.

It has to be a runtime conflict. I changed the markup of my test case to XHTML and got the same result. And both IE and FF give me the same sizing problem.

That sucks, but thanks for the info.

I just checked the cartridges and they're fine, except the cyan one is expired. I had originally thought that replacing the black cartridge caused the problem, since that was the description I was given, but I don't think the cartridge was replaced last night (it's a family computer printer, so I wasn't the one to swap cartridges), so there's no real causal relationship between the two. I also checked the user manual .pdf. Nadda. I don't like the idea of replacing a perfectly good color cartridge because of some manufacturer defined use-by date in order to print at all, which is why I was hoping to find a work-around. Unfortunately, it doesn't look like there's any setting I can change to tell the printer to use expired cartridges.

I have an HP 3000 series printer. After changing the black ink cartridge, my printer won't print. It keeps telling me that the color cartridges are out of date. These color cartridges are still, at the very least, half-full, so that's not an issue. It's incredibly frustrating not being able to print at all because of this expiration date crap. I've already tried Google, but haven't found anything addressing this particular issue. So, does anyone know of a work around? Or am I forced to buy new cartridges even though the old ones are still good?

I'll have to argue that it's the mass of material that's covered in that book, not the editing, that can cause confusion. I, too, use the same book, and I've found it to be the best resource by far that I have found and gleaned from in the PHP OOP realm. Take your time with it, and it will come to you. It's definitely one that builds as you go through, too, so you can't just skip examples in it. Heh, I think I'm just dense, then. I've re-read the first few chapters a few times now, and beyond the syntactical stuff I already knew about (defining classes, initializing objects, using __autoload, etc), a lot of the rest of it makes me scratch my head. I think some of it is the author -- case in point, the first use of the Strategy pattern comes out of nowhere, and he doesn't really describe it very well in that first use (certainly not as well as the Factory patterns). Then there's the Factory pattern and Abstract Factory pattern. To my untrained eye, they look virtually identical. There are some code examples where it looks like he forgot to mention a database table name, or perhaps used the wrong name (I believe one of them is the ReflectionAPI module loader example, or maybe the Factory example when he was describing exceptions). I dunno...it just doesn't seem as clear and concise as it could be to me, and things like that, as little as some may be, tend to throw me off.

Are there any resources the gurus here could recommend for an OOP newbie? Any books, sites, etc.? I have one book (PHP Objects, Patterns, and Practice), but it's not edited very well, so it can get confusing at times. I'd like to know if there are any particular things I should check out before relying on Amazon and hoping I don't blow my $$ on a book that really isn't as good as its rating.

Well, I just tried a very simple version of my calendar, and I'm still getting table cells that stretch. My code is below. HTML: <html> <head> <title>Test</title> <script type="text/javascript" src="test.js"></script> <link rel="stylesheet" type="text/css" href="test.css" /> </head> <body> <table> <tr> <td></td><td></td><td></td><td></td><td></td><td></td><td></td> </tr> <tr> <td></td><td></td><td></td><td></td><td></td><td></td><td></td> </tr> <tr> <td></td><td></td><td></td><td></td><td></td><td></td><td></td> </tr> <tr> <td></td><td></td><td></td><td></td><td></td><td></td><td></td> </tr> <tr> <td></td><td></td><td></td><td></td><td></td><td></td><td></td> </tr> </table> </body> </html> My JavaScript: var W3CDOM = (document.createElement && document.getElementsByTagName); function init(){ if(!W3CDOM) return; printCalendar(); } function printCalendar(){ var days = document.getElementsByTagName('td'); for(var i = 0; i < days.length; i++){ days[i].innerHTML = "I'm making a long ass paragraph to see if the table cells expand, so blah blah blah blah"; if(i / 2 == 0){ days[i].style.backgroundColor = "black"; days[i].style.color = "white"; } else if(i / 3 == 1){ days[i].style.backgroundColor = "red"; days[i].style.color = "white"; } else if(i / 5 == 1){ days[i].style.backgroundColor = "blue"; days[i].style.color = "white"; } else{ days[i].style.backgroundColor = "green"; days[i].style.color = "white"; } } } window.onload = init; My CSS: td { width: 76px; height: 76px; overflow: auto; } I'm wondering if not using XHTML (or, at least, not declaring my document as XHTML) is messing it up.

Try this: var previous_id = "Nothing"; function hover_country(id){ window.alert("You hovered over: " + id); window.alert("You previously hovered over: " + previous_id); previous_id = id; }

I just want to make sure we're on the same page, as something in your previous post just caught my eye: My CSS isn't written to the page from the JS script. It's merely an external CSS file linked to the HTML. Only the calendar dates, info, and background colors are written from the JS. Would this make a difference?

It looks like you're attempting to create a sticky form, but your logic is a bit messed up. The typical logic flow is: Process the form if it's been submitted Display it if not, or if there are errors. Your current logic is: Connect to database Display form Process form So, you should start off with a conditional that checks if the form has been submitted: <?php if(isset($_POST['submit'])){ //process form } ?> Then display the HTML after you've done everything, including sending info to the database. Secondly, you never set an action for your form. If you want to have everything in one script, you'll need something like: <form method="post" action="<?php echo $_SERVER[php_SELF]; ?>" > This tells the form to use the current script for processing. Hope this helps you figure it out.

I think this is the problem as I haphazardly put items into the different tables. So, to use the Microsoft keyboard/mouse combo example, in the peripherals table it has an id of 14. In the gaming_peripherals table, it has an id of 1. Unfortunately, my scripts require the id of each item. In any event, it doesn't matter much now as this project has been put on the backburner for a bit. If/when I come back to it, I think I'll just redesign the tables from the ground-up. I never thought I needed to normalize my tables when this project started months ago as I thought it would remain small, but it kinda blew up on me and caught me with my pants down.

How would I test for this? Maybe use setTimeout?

Unfortunately, I'm still getting repeated rows. Like I tried (horribly) to show above, as an example row 13 in peripherals and row 1 in gaming_peripherals have the same info across the board. Instead of just having one of those two rows (it doesn't matter which one for my script) returned, I get both back.