My good friend Jenni just announced the grand opening of her site "Code Novice" – already she has a few scripts and tutorials up that look pretty interesting. 😀
My good friend Jenni just announced the grand opening of her site "Code Novice" – already she has a few scripts and tutorials up that look pretty interesting. 😀
Happy Birthday Scriptygoddess – Two years old today.
(Does this mean I've entered the "terrible two" stage?) 😉
(Still on old news for you CSS-pros. I'm wondering why YOU'RE not writing this blog. All the comments have been more helpful than my posts!! LOL!)
Just wanted to jot these down so I could find them later:
font-weight: bold;
font-size: 10px;
font-family: Verdana,Arial,Helvetica,sans-serif;
shortcut:
font: bold 10px Verdana,Arial,Helvetica,sans-serif;
margin/padding shortcuts:
margin: top# right# bottom# left#
ie. margin: 5px 0px 2px 10px;
or
margin: top&bottom# left&right#
ie. margin: 10px 5px;
color shortcuts (websafe hex)
color: #000000;
shortcut: color: #000
color: #FFCC00;
shortcut: color: #FC0;
This will come in handy when trying to figure out how pages are constructed in CSS: a mouseover DOM bookmarklet
[via Melissa]
(Also from that same post on Melissa's site: Javascript Weblog)
So I'm moving along in my CSS understanding. I (think) I get float, positioning. I even get the box model, and box model hack.
I had a small site that used a tabled-design that is due to go live next week, so I decided I'd quickly convert it to CSS before the launch. (Yes, I know it's Wednesday. Yes, I'm a glutton for punishment).
I got my layout working 99%. I had previously removed the doctype declaration – so when I put in the box model hack – it didn't seem to work in IE 6. I pasted this one in from a page online that I knew used the hack and worked, and then it worked for me too:
I don't understand doctype declarations. I know they're important and that I should understand them. Right now, I'm just glad my layout is happy again. Baby steps here… baby steps!
This blog gets quite a number of comments. Some are just nice words of appreciation, others are kind of useful. Then there are some that are more valuable than the post itself! (For an example of this – check out my last few posts about CSS.)
I really hope that if you've been reading this blog for awhile, you've learned to comb through the comments. Sometimes the scripts get completely overhauled in there. Other times, people post other solutions, solve installation problems, etc. post helpful links.
Of course the difficult side of that request, is that some posts have A LOT of comments. Unfortunatley, in some cases you'll see the same question get posted over and over again – when it was already answered or addressed previously – but you'd never find that answer in all the comments. Quite simply, it's difficult to find the answers you really need when there's so many comments in a single post.
SO – my script idea is a "COMMENT" rating system – much like this one which was designed for POSTS (side note: Seems like some updates were added and here is the most recent version). As well, there's an update with timestamps and banning here.
It would be simple enough to modify those scripts to store ratings for comments. Additionally what I would add is this: if the comment is rated 50% or 75% (user choice) positively, then highlight it so it's easier for people to find. (This would probably be a simple div around each comment that has a php include in it – that checks the comment's rating and gives the div a background color for a hightlight) By 50 – 75% I mean this: for example if there are "10" votes on a comment and if 7 of them were + (3 of them were – – maybe from people who didn't completely agree) it would get highlighted. If it got only 3 + votes (from a total of 3 votes) – it would get hightlighted – since 3 out of 3 is 100%.
Here's why I haven't just jumped in and written the script.
1) I don't know when MT 3.0 is coming out and I don't know if maybe it already has a feature like this (My comment queue script is already going to be a waste of space – as MT 3.0 will have it baked in. For this I'm glad – because it will be better that way)
2) Since comment stuff is changing in MT 3.0 – I'm not sure what to expect and I don't want to write a script that will have to be updated/modified the day the new version comes out.
3) Since this script is specifically designed for posts with many comments – my original "design" for it meant checking the database x number of times (where x = the number of comments.) For particularly popular posts (I can't believe that one has 125 comments!!) – would this kill my database, bandwidth, and "download" speed?
So just wanted to throw this out there – I won't be writing this script before the MT 3.0 release… but I'd REALLY like to as I think it would greatly help people trying to use scripts from this site. If anyone else has any ideas – feel free to leave a comment.
Just a note that maybe will save someone else the headache I had yesterday.
If you're using Dreamweaver – and create a new HTML page – it automatically sets your doctype like this:
This caused a problem with a table-based design I had done. Images placed inside cells of a table had this odd space after all of them. Even though I had specified the table, and it's cells to the exact width and height of the image, as well, there was no space in the HTML itself. It only would happen on Netscape 6 – and as soon as I removed the doctype declaration – it went away.
So, I'm checking out CSS Zen Garden – I'm now using firefox because of all the cool extensions it has specifically the PNH Toolbar which lets outlines the blocks (ie. grids) on the page, as well as this one: Edit CSS which lets you see and EDIT the current page's CSS and redisplays your changes in real time. (mentioned in the comments of this post, by Andrew Dupont) (THANK YOU for those!!!)
In doing so, I was examining the first Zen Garden page's CSS which uses this trick to swap images instead of text. That is just so cool. (I know, all you CSS-freaks have probably known about that little trick for eons.)
A brief break from the eye-bleeding CSS talk. LOL! ;o)
I needed a text field to be prefilled with text. If the user clicked on it, the text would clear out. If they "left" the text field (changed focus) without changing it – I needed it to revert back to the original text. If they DID enter information in it, I needed it to NOT revert back to the original text. (Clear as mud?)
Here's what I mean:
Here's how (and why) I did this:
Read the rest of this entry »
Sorry for the placeholder, my plan is to fill in the answers. (If I get the answer wrong, please correct me! As well, feel free to answer any of them in the comments – if you do, I'll move your comment into the body of the post – with credit (and then delete the comment to clean up) (Actually there was an answer by Tom (anonymous) in the comments – I'll leave his there, and try to put it in my own words – maybe then I'll get it! LOL!)
Question
What's the difference between static, relative, absolute, fixed positioning. And what scenario would be a good example for use of each?
Question
what's the difference between inline vs block display (and some of the other options for display)? good examples for use? (I know that display: none hides stuff. That's about it)
Question
Float?? What's the best use for this – doesn't this fight against positioning?
(Incidentally – I just tried to find the answers to those questions in this book, and I DO believe my eyes are starting to bleed… The definitions made NO sense. Don't get me wrong – Eric Meyer is great… except for those particular definitions)