Web Dev Q&A #2 - PHP Sessions, HTML5 Doctypes, and Form Styling

We're back with the second entry in the Nettuts+ Q&A series. Today, we discuss the difference between LESS and Sass, how to pass server-side values to your JavaScript, how to work with PHP and cookies, and the HTML5 doctype. Here we go!

1. LESS and Sass.

Hey Nettuts+. I'm confused. What's the difference between LESS and Sass? Are they the same?

There are advantages to using both; however, the truth is: both will get the job done wonderfully. It mostly becomes a case of preference, when it comes to the syntax and such. In the past, many preferred LESS, because it had a more friendly CSS-like syntax, though, as of Sass 3, they have a new syntax, known as SCSS (Sassy CSS), which is simply a subset of CSS3's syntax.

The Envato devs use Sass. Other popular developer prefer LESS. I'd equate it to comparing the 960 CSS framework to Blueprint. They're both great; so make up your own mind. There are no wrong answers!

2. Server-side to Client-side

I've been trying to figure out how to pass the value of a PHP variable to my JavaScript. How do I do this? Thanks!

The quickest and easiest solution is to echo your desired variable from within your JavaScript. For example, you could query your MySQL database with PHP, and then pass the returned value to your JavaScript by doing something along the lines of:

3. Custom Stylesheets with PHP

How can I choose a color scheme stylesheet for my website dynamically?

So you want to, for instance, choose red.css, or blue.css, and that would load a different color scheme for your website. Is that what you mean? There are certainly several ways to accomplish this task, and the correct choice will depend on if you're using a framework, a CMS, MVC, etc. Let's keep things simple, and as bare-bones as possible. We can use PHP sessions. First, we need to add a select box, for the user to choose their desired color stylesheet.

Next, with PHP, we'll listen for if the page has posted back -- or if the Submit button has been clicked. With a simple page like this, we can use the helpful $_SERVER['REQUEST_METHOD']. The "Request Method" determines which request method was used to access the page: 'GET', 'HEAD', 'POST', 'PUT'" At the top of your page, add the following: Since we can now confirm when the page has posted back, we can then create a session, and store the value of whatever the user chose from the select box. Here, we're first creating a new PHP session, with session_start(). Next, we create a new key, with $_SESSION, called "color_scheme." Feel free to name this how you wish. By default, we set this to "default" (see the "else" statement). This means that, if the user hasn't selected a stylesheet, we'll use the default one. However, if they did make a choice, we need to determine which option from the select element they chose, and store it in a Session key.

Returning to the mark-up, you'll find that we applied a name of "colors" to the select element.

When the page posts back, the selected value of this select element will be available to us, via $_POST['colors']. For example, if I choose the "green" option, $_POST['colors'] will then be equal to "green."

Without sessions and cookies, there would be no way to "remember" this user-selected value. That's why they're essential in this case. Now that \$_SESSION['color_scheme'] stores our desired value, we only need to load the appropriate stylesheet.

4. Rounded Form Elements

Hi Nettuts+! How do I create rounded form inputs with CSS for all browsers?

So you want stylized, rounded inputs in all browsers, including Internet Explorer? Okie dokie. Consider the following simple mark-up:

Using some simple CSS3, we can create rounded corners for those inputs. Because some browsers got a headstart on the spec, we need to use the -moz and -webkit vendor prefixes, as well as the official version of the "border-radius" property.

• -moz: Mozilla browsers (Firefox)
• -webkit: Webkit browsers (Safari, Chrome)

By specifying atype attribute of submit, that last snippet will only target submit buttons, and will style accordingly.

That Blasted IE

Unfortunately, as you probably guessed, Internet Explorer is a jerk. While the upcoming IE9 has support for border-radius (without a prefix), the older versions are still at a loss. At this point, you have two choices:

1. Ignore it. The world won't end if your readers see 90 degree angles.
2. Image Fallback. You can target Internet Explorer specifically, and apply a rounded background image.

Modernizr

I'm assuming the asker of this question requires consistency; so we'll go with the second option. Let's assume that you're going to be working heavily with CSS3 and HTML5 in your project. In that case, rather than using an IE-only stylesheet, why not have some fun, and use the helpful Modernizr library?

Next, apply a class of no-js to the Html element on your page.

When you view your project in the browser, Modernizr will apply a long string of classes to the Html element, which specifies exactly what your browser is capable of. Note that, obviously, this list of classes will vary, depending upon the browser.

This is a huge help! Now we can use the "cascade" effect to only target the form elements that are children of the html element with a class of "no-borderradius," and style accordingly.

If the browser does not support a particular feature, the word "no" will be prefixed to the rule.

And then we relax and have cake.

5. Doctypes

I noticed that you always use the HTML5 doctype. Don't you think that's dangerous, when all browsers don't yet support HTML5?

No, it's not dangerous at all. For those unfamiliar with the wonderfully simple HTML5 doctype, it's:

Seriously...that's it. That's all there is to it. No more multi-line spats of attributes; just a plain-ole DOCTYPE - as it should be. In older browsers, this doctype will trigger them into standards-mode. ...And if you're still worried, note that even Google uses it! Need more? John Resig was talking about this 2.5 years ago!

"What's nice about this new DOCTYPE, especially, is that all current browsers (IE, FF, Opera, Safari) will look at it and switch the content into standards mode - even though they don't implement HTML5. This means that you could start writing your web pages using HTML5 today and have them last for a very, very, long time."
-John Resig