We provide quality IT training and services Visit our website or call 464-7446 for advice We are at suite 505-506, Newry Complex St Jean Road, Quatre-Bornes, Mauritius
I also find PHP in Action: Objects, Design, Agility quite interesting. The focus is less on developing web apps or websites and more on learning and using PHP as a "real" object-oriented programming language. This book made me realise that PHP5 is somewhat close to Java for instance...
After reading those two books, I would say that reading a book on a PHP framework is important. For example, Zend Framework, A Beginner's Guide is a good book on Zend Framework created by the same people who develop PHP. Of course, other frameworks (e.g. CakePHP, Yii, Recess, etc.) are also worth reading about.
There is a sale going on during this month on Sitepoint. The books look quite interesting. You will find books on PHP, Javascript, Jquery, HTML5, CSS, etc. The prices are rather good too. Here is the link: http://www.sitepoint.com/sale
Well, so start with, I think you can try http://www.w3schools.com/ for a first overview, try things from there. Although, it is less good than many books, i really believe it can help you to start
I think websites are great to read about new technologies and techniques. But nothing beats actually doing those things e.g. designing a website from scratch using W3C-compliant and semantic HTML(5) and CSS(3). This is where one really learns about the enormous gap between theory and practice :-)
101% correct. Dealing with compliant browsers vs IE is the most tedious work for a front-end developer.
Also, i'll recommend everyone (especially newbies) to forget about WYSIWYG editors (Frontpage - still exists ? - Dreamweaver, etc). Hand-code your (x)HTML(5) / CSS(3). Use notepad or vi (well you have other editors in Windows / Linux, but the point is HAND-CODING). True web developers hand-code (this is important for SEO, remember)
Yep, WYSIWYG editors are not the way to go. You should be crafting semantic markup first, then applying CSS to do the layout. A WYSIWYG tool would encourage a workflow that's the opposite of what you should be doing.
The slice plugin will create small images as well as an HTML file using a TABLE to include the images. This is not as good as using DIVs and CSS but it's good enough. One can then replace the "dummy text" sections with real text directly within the . Of course, nothing prevents someone from using CSS to style the text.
Of course, at this point, someone conversant with CSS can relatively easily transform the TABLE based layout into something more standards-compliant.