The only issue I have with conditional comments is that they are proprietary to MS and they are embedded in the markup. In most cases I will have a default.css, which in turns uses @import for my typography, color, layout, reset, and hacks. Yes, I compress and combine when necessary. However, as much as I hate hacks - I would rather manage hacks in a separate stylesheet, then add extra markup that was given to use by Microsoft due to their crappy support.
So, while it is a solution - I would rather manage all of my CSS inside of my CSS. Then, when a hack is fixed, I can remove it from the stylesheet. When all hacks are fixed I can remove the entire stylesheet - but I never had to edit the markup to remove the stylesheet or change information specific to IE.
There are pros/cons to both - I just don't like the idea of using conditional comments to achieve the task. Better yet, build your layouts so they don't require hacks. Well....that might not always be possible. ha.
They have had it that way on Amazon since the book started shipping. In fact, they had him listed as 2 authors - Jonathan Snooks and Jonathan Snook. I would have thought it would have been corrected by now. Or - snook has a double personality.
This book really is more of a cookbook of sorts. I don't think it really teaches the intricacies of CSS, but helps extend CSS for those who are already very familiar with it. I definitely have some other books that I would recommend if you are interested in learning CSS.
This book was a quick read, and with multiple authors the chapters were not very lengthy. I tried to give a brief scan of each chapter with some insight to what the chapter covered. If I were to go into too much detail, I would be re-writing each chapter. The chapters also consisted largely of code examples which take up a good chunk of space.
Feel free to contact me if you have any specific questions. I have found that I can't please everyone with my reviews. You said there wasn't enough, while others in this thread said the review was too long. I want to find a good balance so I really do appreciate the critique.
Kevin,
Looking back at the review now I can see my abundance of deviations. I apologize for the interjections, and hope that you can look past that and still get some information from the review.
This helps me improve my writing of reviews - so I appreciate the feedback.
I haven't checked out the Head First book yet - but it does look like it would be a good starting point. I am at the point that with most of the CSS books I have read I start to see all of the overlapping. I like books that can bring something fresh and different to the table. This is why I liked this book - it examined real world scenarios and layout options.
Slashdot Mirror
The only issue I have with conditional comments is that they are proprietary to MS and they are embedded in the markup. In most cases I will have a default.css, which in turns uses @import for my typography, color, layout, reset, and hacks. Yes, I compress and combine when necessary. However, as much as I hate hacks - I would rather manage hacks in a separate stylesheet, then add extra markup that was given to use by Microsoft due to their crappy support.
So, while it is a solution - I would rather manage all of my CSS inside of my CSS. Then, when a hack is fixed, I can remove it from the stylesheet. When all hacks are fixed I can remove the entire stylesheet - but I never had to edit the markup to remove the stylesheet or change information specific to IE.
There are pros/cons to both - I just don't like the idea of using conditional comments to achieve the task. Better yet, build your layouts so they don't require hacks. Well....that might not always be possible. ha.
They have had it that way on Amazon since the book started shipping. In fact, they had him listed as 2 authors - Jonathan Snooks and Jonathan Snook. I would have thought it would have been corrected by now. Or - snook has a double personality.
Cromar,
Thanks for the feedback.
This book really is more of a cookbook of sorts. I don't think it really teaches the intricacies of CSS, but helps extend CSS for those who are already very familiar with it. I definitely have some other books that I would recommend if you are interested in learning CSS.
This book was a quick read, and with multiple authors the chapters were not very lengthy. I tried to give a brief scan of each chapter with some insight to what the chapter covered. If I were to go into too much detail, I would be re-writing each chapter. The chapters also consisted largely of code examples which take up a good chunk of space.
Feel free to contact me if you have any specific questions. I have found that I can't please everyone with my reviews. You said there wasn't enough, while others in this thread said the review was too long. I want to find a good balance so I really do appreciate the critique.
Kevin,
Looking back at the review now I can see my abundance of deviations. I apologize for the interjections, and hope that you can look past that and still get some information from the review.
This helps me improve my writing of reviews - so I appreciate the feedback.
I haven't checked out the Head First book yet - but it does look like it would be a good starting point. I am at the point that with most of the CSS books I have read I start to see all of the overlapping. I like books that can bring something fresh and different to the table. This is why I liked this book - it examined real world scenarios and layout options.
CSS books come in many different flavors. Some are CSS specifications broken down. Some are just explanatory of the different selectors. Some, like this book, give real world examples. And still others such as Transcending CSS, challenge you to move forward in your designs.
Again, thanks for the critique.