heydanreeves

I used Tsohost. They seem to be really good value for money and have excellent support.

AFAIK you can only do this by explicitly declaring the heights (or knowing the heights), faking it, or using javascript.
 
EDIT:
 
7 HTML & CSS methods: http://css-tricks.com/fluid-width-equal-height-columns/
 
Using jQuery: http://www.cssnewbie.com/example/equal-heights/
 
and this one talks about using jQuery with fluid layouts : http://css-tricks.com/equal-height-blocks-in-rows/

Hey Ben!
 
Cool username
 
Hope you enjoy being on the forum

I went to a conference on saturday and one talk was about 'Where do our clients come from?'. This small design firm (2 people) showed that for the first 3 years of their business over 50% of their clients were people that they knew directly, either family, friends, or old co-workers. The rest was referrals from family,friend and old coworkers or the clients that had taken on.
 
This was quite interesting to me, as someone just getting into the profession.
 
So, my advice, milk your contacts! Keep reminding everyone you know that you make websites and are looking for work.

I went to a conference on saturday and one talk was about 'Where do our clients come from?'. This small design firm (2 people) showed that for the first 3 years of their business over 50% of their clients were people that they knew directly, either family, friends, or old co-workers. The rest was referrals from family,friend and old coworkers or the clients that had taken on.
 
This was quite interesting to me, as someone just getting into the profession.
 
So, my advice, milk your contacts! Keep reminding everyone you know that you make websites and are looking for work.

Look at this demo I just made up: http://jsbin.com/emabuy/1/edit
 
You can see the 'directionNav: false' option working. Hopefully if you look at my code you can see how to get yours to work.

Change
<!-- Hook up the FlexSlider --> <script type="text/javascript"> $(window).load(function() { $('.flexslider').flexslider(); }); </script>  
to
<!-- Hook up the FlexSlider --> <script type="text/javascript"> $(window).load(function() { $('.flexslider').flexslider(directionNav: false); }); </script>  
 
The FlexSlider plugin has lots of options available to you, which you can read about here: https://github.com/woothemes/FlexSlider/wiki/FlexSlider-Properties

Change
<!-- Hook up the FlexSlider --> <script type="text/javascript"> $(window).load(function() { $('.flexslider').flexslider(); }); </script>  
to
<!-- Hook up the FlexSlider --> <script type="text/javascript"> $(window).load(function() { $('.flexslider').flexslider(directionNav: false); }); </script>  
 
The FlexSlider plugin has lots of options available to you, which you can read about here: https://github.com/woothemes/FlexSlider/wiki/FlexSlider-Properties

Chrome DOES support the .mp4 file type.
 
.mp4 is just a wrapper or container format but the video and audio formats under .mp4 file can be varied. For example, for video, MPEG-4 Visual and H.264 are common formats.
 
If you check this website (http://html5test.com/compare/feature/video-mpeg4/video-h264.html) you can see that chrome doesn't support the MPEG-4 Visual format but it DOES support the H.264 format.
 
So if you want to use the .mp4 file type for videos on the web, make sure the encoding is H.264 or convert it into H.264.
You can check the my previous post for further information on getting full browser support.
 
 
EDIT: However, back in 2011, Google said that they were dropping support for the .mp4 file type in favour for the WebM and Ogg Vorbis Theora file types which are open and patent free, in contrast with mp4.
 
They haven't actually removed support yet though (2 years later!) but just in case they remove it or it breaks and they don't fix it, I would make sure you support all the file types. More info in another post I made. Link here: http://www.webdesignerforum.co.uk/topic/67819-best-video-format-to-use-on-a-webpage-google-chrome/?p=427058

Here is a post I made on another thread not too long ago on this subject. I think it covers the subject pretty well.
 
Link: http://www.webdesignerforum.co.uk/topic/67819-best-video-format-to-use-on-a-webpage-google-chrome/?p=427058

Just to provide a difference of opinion here, I almost never use IDs any more (even for JavaScript). I prefer using classes because it makes the CSS more modular and easier to work with owing to the smaller specificity. Having read up on SMACSS, I live the idea of sub-classing my modules and that's much harder with IDs. 
I'm not saying that IDs are bad things, just that there are those of us out there who chose not to use them.

Why don't you use JavaScript to measure the dimensions of the users browser and then use a conditional statement to run the Tinybox script if the width and height are over a specific boundary?

For example...
 
if (screen.width > 600 && screen.height > 450){document.write("<script src='tinybox.js'>");}  
I'm not sure if that's correct or it will even work - I haven't used JavaScript in quite some time as I'm trying to get my head around OOP but it's worth a shot.

If you look at my demo again (http://codepen.io/HeyDanReeves/pen/Jnbqx) I made it look similar to the section you are styling. Hope that helps at all.

Exactly what Lyndsey said. You're positioning the p in such a way that depending on it's length it will pop out of its container. But yes, removing those two properties breaks the layout you're going for so you might have to play around or maybe restructure that section.
 
I may be able to play around with that.
 
As for your second question; yes, that's extremely easy to do. It's actually what floats were added to CSS for. Here is a super simple demo I just made: http://codepen.io/HeyDanReeves/pen/Jnbqx

You can do it with IE conditionals but you'll need two or three lines.
// Targets IE 7 and down <!--[if lt IE 8]> <link rel="stylesheet" type="text/css" href="ie7-style.css" /> <![endif]--> // Targets all IE above 7 <!--[if gte IE 8]> <link rel="stylesheet" type="text/css" href="style.css" /> <![endif]--> // Targets all other browsers <!--[if !IE]><!--> <link rel="stylesheet" type="text/css" href="style.css" /> <!--<![endif]-->  
 
EDIT: This article may also be helpful: http://stuffandnonsense.co.uk/blog/about/universal_internet_explorer_6_css
 
The general idea is to use
<link rel="stylesheet" type="text/css" media="screen, projection" href="http://universal-ie6-css.googlecode.com/files/ie6.0.3.css" />  
for the old IE browsers you're not supporting. It's just a general typographical stylesheet so your content will still be accessibile.

You can do it with IE conditionals but you'll need two or three lines.
// Targets IE 7 and down <!--[if lt IE 8]> <link rel="stylesheet" type="text/css" href="ie7-style.css" /> <![endif]--> // Targets all IE above 7 <!--[if gte IE 8]> <link rel="stylesheet" type="text/css" href="style.css" /> <![endif]--> // Targets all other browsers <!--[if !IE]><!--> <link rel="stylesheet" type="text/css" href="style.css" /> <!--<![endif]-->  
 
EDIT: This article may also be helpful: http://stuffandnonsense.co.uk/blog/about/universal_internet_explorer_6_css
 
The general idea is to use
<link rel="stylesheet" type="text/css" media="screen, projection" href="http://universal-ie6-css.googlecode.com/files/ie6.0.3.css" />  
for the old IE browsers you're not supporting. It's just a general typographical stylesheet so your content will still be accessibile.

Unfortunately Flash is the only way to go with this right now.
 
(Chrome and Firefox did recently add the WebRTC API which means video chat is available in the latest chrome and firefox (might just be the nightly builds) with just web technology! Cool demo: http://www.webrtc.org/demo)

Cross compatibility with HTML5 video is quite hard. Firefox and Opera need .ogg videos while Safari and Chrome need H.264. Meanwhile IE is just being IE.
 
You actually need a few file formats plus a flash fallback to get as much cross-compatibility as possible iirc.
 
Don't bother doing it all yourself though, some other smart people have put some time into writing some nice applications that can help. I would check these out and then look around if you're still not happy but these should do the job.
 
http://videojs.com/
http://sandbox.thewikies.com/vfe-generator/
 
EDIT:
I felt like going over this in a bit more detail, if not for anyone that reads this then for myself!
 
 
Have a look at this page for the browser coverage of each format: http://caniuse.com/#search=video
 
This shows that
<IE9 and Opera Mini need flash fallbacks. H.264(MP4) covers IE9+, Chome, Safari and iOS WebM covers Firefox, Chrome and Opera (Note: Will work in IE9+ and Safari provided the user has the WebM codecs installed) Ogg/Theora covers Firefox, Chrome and Opera However you might still need all three formats because they each started accepting different formats at different times. So you need the following:
MP4 for Safari, IE9, iPhone, iPad, Android, and Windows Phone 7 WebM/VP8 for Firefox4, Opera, and Chrome Ogg/Vorbis for older Firefox and Opera versions Flash fallback for non-HTML5 browsers without JavaScript But it depends on your own statistics as to what you want to implement.
 
Some more links/players:
http://mediaelementjs.com/
http://www.jplayer.org/ - has playlist support
http://mediafront.org/osmplayer/ - jQuery plugin, also supports playlists

You are right. That code is code is completely unmaintainable and not modular. Modular, or OOCSS, should definitely be best practice nowadays. IMO, the most selectors you should use in a row (e.g. .wrapper article h3 {) should be 3 at max. If you mark up content in a reusable way you shouldn't ever need more.
 
In the other direction, CSS like in your example is just bad. Not only is it more to write, which in a large stylesheet could really add up, but its lack of modularity will increase the amount of writing even more, needing entirely new declarations on things that could have shared common modules of CSS. It also introduces specificity problems. What if a 'section' in that chain was changed to an 'article' in one page. You would have to write an entirely new declaration for that one box.
 
SMACCS by Jonathan Snook is a nice little book on this subject, or I'm sure there are plenty articles to read online.

This is why you should always put the prefix free/standardized version at the end of the declaration. e.g.
-webkit-transform: rotate(7.5deg); /* Chrome, Safari 3.1+ -moz-transform: rotate(7.5deg); /* Firefox 3.5-15 -ms-transform: rotate(7.5deg); /* IE 9 -o-transform: rotate(7.5deg); /* Opera 10.50-12.00 transform: rotate(7.5deg); /* Firefox 16+, IE 10+, Opera 12.50+  
Because CSS is applied line by line and later lines will overwrite previous lines, writing it in the wrong order could lead to an outdated prefixed version of the property being used instead of the browsers latest, standards compliant version.
 
As for what actually happens to the prefixed property, they keep it in the browser for some time to allow a transition period but, eventually, they completely remove it. I once saw someone submitted a bug to the firefox bugzilla and continued to argue that browsers should retain all prefixes as 'legacy code'. Pretty funny stuff.
 
Found it: https://bugzilla.mozilla.org/show_bug.cgi?id=765645

This is why you should always put the prefix free/standardized version at the end of the declaration. e.g.
-webkit-transform: rotate(7.5deg); /* Chrome, Safari 3.1+ -moz-transform: rotate(7.5deg); /* Firefox 3.5-15 -ms-transform: rotate(7.5deg); /* IE 9 -o-transform: rotate(7.5deg); /* Opera 10.50-12.00 transform: rotate(7.5deg); /* Firefox 16+, IE 10+, Opera 12.50+  
Because CSS is applied line by line and later lines will overwrite previous lines, writing it in the wrong order could lead to an outdated prefixed version of the property being used instead of the browsers latest, standards compliant version.
 
As for what actually happens to the prefixed property, they keep it in the browser for some time to allow a transition period but, eventually, they completely remove it. I once saw someone submitted a bug to the firefox bugzilla and continued to argue that browsers should retain all prefixes as 'legacy code'. Pretty funny stuff.
 
Found it: https://bugzilla.mozilla.org/show_bug.cgi?id=765645

This is why you should always put the prefix free/standardized version at the end of the declaration. e.g.
-webkit-transform: rotate(7.5deg); /* Chrome, Safari 3.1+ -moz-transform: rotate(7.5deg); /* Firefox 3.5-15 -ms-transform: rotate(7.5deg); /* IE 9 -o-transform: rotate(7.5deg); /* Opera 10.50-12.00 transform: rotate(7.5deg); /* Firefox 16+, IE 10+, Opera 12.50+  
Because CSS is applied line by line and later lines will overwrite previous lines, writing it in the wrong order could lead to an outdated prefixed version of the property being used instead of the browsers latest, standards compliant version.
 
As for what actually happens to the prefixed property, they keep it in the browser for some time to allow a transition period but, eventually, they completely remove it. I once saw someone submitted a bug to the firefox bugzilla and continued to argue that browsers should retain all prefixes as 'legacy code'. Pretty funny stuff.
 
Found it: https://bugzilla.mozilla.org/show_bug.cgi?id=765645

You could use an SQL statement like:
SELECT field1, field2, field3 INTO OUTFILE '/path/to/file.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n' FROM table  
or if you want to do it through PHP check this link.

Hey JLS,
 
If you check out this demo I just put together. http://codepen.io/HeyDanReeves/pen/EvacA
 
The CSS property you're looking for/at is font-rendering. This is unadvised however for reasons outlined here: http://www.usabilitypost.com/2012/11/05/stop-fixing-font-smoothing/ as well as the property being -webkit- only, so you can only cover chrome, safari and soon opera with this.
 
Hope this helps.

Just found this really handy website if you've got someone who's having trouble using your website.
 
Shows all the details of their browser and lets them send is directly to you with a link or via email.
 
http://www.supportdetails.net