Franco - Html and Web development : New vision for web development

Maybe I will be one optimistic, but I believe that we found in one time revo- lucionria to the development web. The Internet is proliferated by world gra the to advance the of band wide and the various devices capable of browsing the network

- cell phones, tablets, televisions and video games. Several companies in the digital world driving the evolution will of the technologies we use to create a be er web. Professionals at companies such as Google, Microso, Apple and Facebook work

exclusively on improvements to the most used browsers, and par- ni of cipar will new standards and disseminate enough kno w ledge with h t c e ommunity of de v elopers.

And everything will continue to expand. New companies, new standards, new devices. The internet industry will continue to grow and we need a lot of help to continue this work. And it's very easy to ensure your space into this universe that is moving as one train bullet. Just participate.

If you are one designer without a lot of experience with development, or one programmer more accustomed to working with lines of command and compilado- res of that browser, I let explain one bit the importance of to learn HTML and CSS. If you are working or want to work with technology, I believe that good part - or all - of their projects will be used by the one na- vegador. Is an internal system of a bank, a social network, a major portal of news or sites for campaigns of publicity, the middle common today in day is the web, and it is quite interesting to have one great base of knowledge about devel- opment front- end (of the terms used to refer to the interface of a true are) to contribute to the success of the projects that you are participating. For this, I recommend a lot that you learn about the

what makes the web work.

In addition to books like this, there are many courses and sites for you to learn more the about or learn other technologies related. Imagine taking care of one park of servers without having a good knowledge

of operating systems and topology networks, or work in advertising printed without understanding about the colors or paper used.

All the HTML and CSS we write comes to life inside the browsers used by those who access our pages and websites, so it's very important to have a good understanding of how they work and, especially, the holes in the way. Ever since the days of Mosaic (which eventually became Netscape) and early versions of Internet Explorer in we have always faced a war of incompatibility between browsers and the need for standards to ensure web interoperability between different clients. While this fight may cost some hair ours, it also drives the evolution will of the technologies that make

the browsers work. The Google Chrome has changed the outlook on the process

of updates will continuously, ensuring that the majority of your users have the UL- last version of the browser, Firefox eats or to adopt a similar process. And the component of debug and Inspe will of Firefox, the Firebug, the niu the model base to which the other browsers implement tools like.

Currently, the Google Chrome tends to be the champion of the tests of compatibi- ity with the latest speci O s, always followed the close of the latest versions of Firefox, Safari and Opera. Good part of the inclusions of HTML and CSSI already are dis-

a v ailable in these browsers in full or through proprietary prices. T h I e nternet Explorer, currently in v ersion is (at the time of writing this book to version OTH is in development), it is still well behind the others, but promises to the your next release are interesting.

The dangers live in cases where we need to go beyond the latest versions and tra- balhar with older, like previous versions of Firefox to ~ and the infamous Internet Explorer and . The difference to between the browsers and the performance of JavaS-

Cryptography in comparing will with the their latest versions is astonishing, but in some cases

the audience you want to keep prey to these browsers by complicates s to be updating the browser or to the system operational - The latest versions of Internet

Explorer does not are compatible with the Windows XP for example, the that hinders the updated will in some environments enterprise.

For this, it is important to define the boundaries of the browser that you want to work, and take advantage of adequeadas techniques or solution existing s for problems related to them.

For those who are following the crest of the wave, several properties and functioning bilities new not to lie completely de ned and implemented in the na- vegadores, but it does not in preventing the use

versions "experimental" them. For this, each browser usually exposes these news with speci c prices for difference implements the O Journal will. What at first may sound like a great idea, it became one burden for all the developers: write the same lines of CSS (up) | times, like this:

.button {

/ * Pre ix for the Firefox. */

- moz - transient n : al l 0.2 s linear;

/ * Pre ix for the Chrome, Safari, Safari Mobile and Android. */

-webkit-transition: all linear 0.2s ;

/ * Pre ix to the Opera. */

- the - t ransitio n : Al l 0.2 are linear;

/ * Version end, yet not supported in all the browsers * / transition: all 0.2s linear;

}

While hacks like this can seem unnecessary and guilty for messing up

the code, you need to understand their importance . We are already enjoying and testing

these properties as they are de ned and re ned . The objective is, eventually , to no longer need the fixed versions and to use only the canonical version of the properties.

But not everyone stops to follow the progress of these items. Properties like border-radius and box- shadow does not need more of pre xed to the main browsers for desktops, and to the final of other properties like animation , transition and transform will be vidualised and properly implemented.

For this, we need to take into consideration will two items: Stay up to date on the support of browsers for new features - my reference fa- vorita is the http://caniuse.com, which has a relationship will of browsers with support com- plete, partial or non - existent, and I usually visit from time to time - prin- ly to come air new projects - for me update on this subject. Another important point is that you should mitigate or automate the noise and rework ge- ered by the use of pre xed, is with solution O s as

pre-processors or tools in JavaScript, and focus on the their work in what is taken as standard, as at some time

ment the pre xed not be more necessary.

For this, we will work with the defined standards and eventually cite the prices when necessary.

In this book, we're going to go through several recipes and techniques for you to use in your projects, and we're going to read and write a lot of code very much . We will use tags and pro- priedades that are in use the years, in addition to spending by adi s recent of HTML

and the CSSI. The My intention will it show examples practical likely you

came to see or will use in your day-to-day, but I leave this assessment to you. I know several of them already I helped one or two times by then.

For all this, we need an exit point, a blank canvas for our work. In addition to the HTML basic structure below, we use some tools to help the our work and leave some parts not so integrated ressantes the development web of hand, so we can focus on what really ma ers. We will use Normalize.css ( h t tp: //necolas.github.com/normalize.css/) as a basic style, to ensure be er consistency between browsers different and the -pre x-free ( h t tp: / /leaverou.github.com/pre xf ree /), which is respon- sible for dealing with pre xed owners for the properties of CSSI still not be made one standard among browsers. Besides them, we will need to