SitePoint Sponsor

User Tag List

Page 1 of 2 12 LastLast
Results 1 to 25 of 31
  1. #1
    SitePoint Evangelist fs_tigre's Avatar
    Join Date
    Feb 2009
    Location
    Close to Chicago, Illinois
    Posts
    517
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Start learning HTML5 and CSS3

    Hi,

    I have been hearing a lot about HTML5 lately and I'm wondering if it is time to start learning HTML5 and may be CSS3.

    Is this something we should be learning now?

    Is HTML5 and CSS3 official released?

    Thanks a lot
    Thank you very much!!!

  2. #2
    Programming Since 1978 silver trophybronze trophy felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, NSW, Australia
    Posts
    16,810
    Mentioned
    25 Post(s)
    Tagged
    1 Thread(s)
    CSS 3 is probably a lot closer to release than HTML 5 is since work on CSS 3 started quite a few years ago while HTML 5 was only recently started.

    See http://www.w3.org/Style/CSS/current-work for where things are at with the varions CSS 3 modules - those parts that say candidate recommendstion are the parts of CSS 3 that are actually finished and which browsers are therefore able to consider implementing.

    HTML 5 is a long way behind CSS 3 as it is still only at an early draft stage.
    Stephen J Chapman

    javascriptexample.net, Book Reviews, follow me on Twitter
    HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
    <input name="html5" type="text" required pattern="^$">

  3. #3
    Robert Wellock silver trophybronze trophy xhtmlcoder's Avatar
    Join Date
    Apr 2002
    Location
    A Maze of Twisty Little Passages
    Posts
    6,316
    Mentioned
    60 Post(s)
    Tagged
    0 Thread(s)
    HTML 5 is non-normative and parts of it are in a constant state of flux so there isn't much point in learning it yet and then there is the case that older browsers won't support a lot of it either.

  4. #4
    SitePoint Mentor bronze trophy
    John_Betong's Avatar
    Join Date
    Aug 2005
    Location
    City of Angels
    Posts
    1,833
    Mentioned
    73 Post(s)
    Tagged
    6 Thread(s)
    Here is an example


    Follow the development here at Code.Google.com


    You can easily download the source file from the bottom right hand link



    .
    Last edited by John_Betong; May 2, 2010 at 21:51. Reason: added link to example
    Learn how to be ready for The New Move to Discourse

    How to make Make Money Now with a *NEW* look

    Be sure to congratulate Patche on earning Member of the Month for July 2014

  5. #5
    SitePoint Guru Chroniclemaster1's Avatar
    Join Date
    Jun 2007
    Location
    San Diego, CA
    Posts
    784
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I concur, CSS3 has been kicked around the block quite a bit, and I'm even seeing bits and pieces turn up in various books. HTML 5 isn't currently supported by anything so it's way to early to even begin writing anything to it.
    Whatever you can do or dream you can, begin it.
    Boldness has genius, power and magic in it. Begin it now.

    Chroniclemaster1, Founder of Earth Chronicle
    A Growing History of our Planet, by our Planet, for our Planet.

  6. #6
    Programming Since 1978 silver trophybronze trophy felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, NSW, Australia
    Posts
    16,810
    Mentioned
    25 Post(s)
    Tagged
    1 Thread(s)
    Quote Originally Posted by Chroniclemaster1 View Post
    I concur, CSS3 has been kicked around the block quite a bit, and I'm even seeing bits and pieces turn up in various books. HTML 5 isn't currently supported by anything so it's way to early to even begin writing anything to it.
    Well HTML 5 has only been under development for a year or so while CSS 3 is over five years in. Some parts of CSS 3 have already been released for browsers to start implementing and the rest should reach that point over the next three or four years. HTML 5 will reach the same point about four or so years after that perhaps (depending on how many changes they make - its early days yet so plenty of time to throw it all out and start over a couple more times until they get closer to something that will work better).
    Stephen J Chapman

    javascriptexample.net, Book Reviews, follow me on Twitter
    HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
    <input name="html5" type="text" required pattern="^$">

  7. #7
    bronze trophy
    Join Date
    Dec 2004
    Location
    Sweden
    Posts
    2,670
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by felgall View Post
    Well HTML 5 has only been under development for a year or so while CSS 3 is over five years in.
    HTML5 development started in late 2003.
    Simon Pieters

  8. #8
    SitePoint Mentor bronze trophy
    John_Betong's Avatar
    Join Date
    Aug 2005
    Location
    City of Angels
    Posts
    1,833
    Mentioned
    73 Post(s)
    Tagged
    6 Thread(s)
    Timeline nicked from Code.Google.com:

    http://www.graabr.com/l0wpxf/


    .
    Learn how to be ready for The New Move to Discourse

    How to make Make Money Now with a *NEW* look

    Be sure to congratulate Patche on earning Member of the Month for July 2014

  9. #9
    SitePoint Evangelist fs_tigre's Avatar
    Join Date
    Feb 2009
    Location
    Close to Chicago, Illinois
    Posts
    517
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thank you all for your replies.
    Thank you very much!!!

  10. #10
    Non-Member bronze trophy
    Join Date
    Nov 2009
    Location
    Keene, NH
    Posts
    3,760
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)
    You want to learn them so you are prepared for what we MIGHT be able to do someday, then fine...

    Just do yourself a huge favor and don't even BOTHER trying to use either of them on production websites. It's called DRAFT for a reason. Implementing specifications before they are even out of draft is a hefty chunk of what makes IE such a stone cold ***** today... When released, IE 5.x and IE 6.x were the most standards compliant browsers of their time - IE 5.x by implementing most of CSS2 draft, and IE6 being little more than an attempt at bugfixing the release version while maintaining backwards compatibility to the thousands of sites that relied on the 'broken/incomplete' behaviors of 5.x - resulting in the whole mess aging like milk.

    Should be fun in a few years when all the people trying to use CSS3 on deployment sites today result in browsers like FF aging like milk as well.

  11. #11
    Programming Since 1978 silver trophybronze trophy felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, NSW, Australia
    Posts
    16,810
    Mentioned
    25 Post(s)
    Tagged
    1 Thread(s)
    And one of the biggest problems with IE5 implementing the CSS 2 draft was that the draft had changes made to it before it was finished and by jumping in too soon IE ended up having to support both that draft "quirks" mode and the actual standard version.

    There will probably be lots of similar changes to HTML 5 before it is finished.
    Stephen J Chapman

    javascriptexample.net, Book Reviews, follow me on Twitter
    HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
    <input name="html5" type="text" required pattern="^$">

  12. #12
    It's all Geek to me silver trophybronze trophy
    ralph.m's Avatar
    Join Date
    Mar 2009
    Location
    Melbourne, AU
    Posts
    24,176
    Mentioned
    454 Post(s)
    Tagged
    8 Thread(s)
    As I understand it, the HTML5 team is aiming for Candidate Recommendation in 2012, and Proposed Recommendation in 2022. Bits and pieces of it are becoming available already, and there are JS workarounds for browsers that don't support those features. I've heard people like Zeldman suggest that by 2012 we should be able to use some features of HTML5 pretty confidently (as we use some CSS3 features now)... but we'll see.

  13. #13
    SitePoint Evangelist fs_tigre's Avatar
    Join Date
    Feb 2009
    Location
    Close to Chicago, Illinois
    Posts
    517
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Wow, it looks like we are far from using HTM 5, I’m wondering why Steve Jobs even mentions this in his article about Flash on the iPhone if this is not even ready yet.

    See argument 5:
    http://www.sitepoint.com/blogs/2010/...d-flash-again/

    Complete article:
    http://www.apple.com/hotnews/thoughts-on-flash/

    Thanks
    Thank you very much!!!

  14. #14
    Non-Member bronze trophy
    Join Date
    Nov 2009
    Location
    Keene, NH
    Posts
    3,760
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)
    Sorry, but steve-o doesn't know enough about the technology he's talking about to even be offering an opinion - well, that and he keeps committing PR suicide so far as the whole codec bull goes.

    I prefer to go with what Ian Hickson said on WhatWG.
    http://wiki.whatwg.org/wiki/FAQ#When...be_finished.3F

    Quote Originally Posted by Ian Hickson
    It is estimated, again by the editor, that HTML5 will reach a W3C recommendation in the year 2022 or later. This will be approximately 18-20 years of development, since beginning in mid-2004. That's actually not that crazy, though. Work on HTML4 started in the mid 90s, and HTML4 still, more than ten years later, hasn't reached the level that we want to reach with HTML5.
    Frankly, IMHO using HTML5 or CSS3 on production sites before then is going to be NOTHING more than the exact same mess we have with HTML4/CSS2 - where even the 'compliant' browsers have GAPING holes in the *** specifications.

    Hell, it's one of the things that pisses me off about certain browser makers (ok, mozilla) - MAYBE they should be fixing the bugs that are OVER A DECADE OLD BEFORE they have people dicking around implementing specifications that aren't even out of draft? Hell, I'm the nutjob who applauded Microsoft for NOT implementing any of HTML5/CSS3 in IE8 since they figured it might be smarter to clean up their HTML4/CSS2 first.

    Priorities people. But because bugs like that one aren't fashionable or trendy, we'll likely NEVER see them fixed.

  15. #15
    SitePoint Evangelist fs_tigre's Avatar
    Join Date
    Feb 2009
    Location
    Close to Chicago, Illinois
    Posts
    517
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thanks a lot!
    Thank you very much!!!

  16. #16
    Follow: @AlexDawsonUK silver trophybronze trophy AlexDawson's Avatar
    Join Date
    Feb 2009
    Location
    England, UK
    Posts
    8,111
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)
    deathshadow60, I have to respectively disagree, especially in the case of CSS3. We aren't back in the days where people expected everything to be pixel perfect and we certainly aren't in a situation where people refuse to think forward. None of the browser makers have any intention (from what I can see) to keep hand holding outdated and primordial code (though they will support specifications which are still valid but kept for archival purposes, like HTML 4.01 will be when 5 goes final). Clearly Microsoft are learning their lessons from what happens if you interlock everything in such a way that people just don't follow the standards anymore. I wholeheartedly encourage people to make use of HTML5 and CSS3 under the condition that they ensure they maintain the source code and make sure it degrades gracefully. If anything, using new technologies off the bat HELPS the standards adoption process as it encourages more people to shape the spec via real world usage (thereby ironing out bugs). It's almost of the same way that microformat adoption has shaped the way semantics have grown.

    There is absolutely no reason for anyone to proclaim that those languages are not for production usage purely on the basis that their incomplete. If you ensure your code progressively enhances, maintain your code as new versions of browsers are released (thereby cutting the cord on proprietary extensions as their currently required) and strike the balance between using something to enhance the site and needing something for the site to work, you'll be fine. If we want to stop the issues of old there should be a zero tolerance approach from browser makers for deprecated code, debunked proprietary extensions and "hand holding" for the end user. Doing so as we currently do is what keeps resulting in the mess we find ourselves in, you could certainly break the zero barrier for entry issue if you struck down those who refuse to upgrade their skills and knowledge to match the requirements of progression or as I like to think of it, holding back the whole class because of the special needs kid in the corner. So I am firmly in support of CSS3 (especially) and HTML5 for regular code maintainers in production environments.

  17. #17
    Non-Member bronze trophy
    Join Date
    Nov 2009
    Location
    Keene, NH
    Posts
    3,760
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by AlexDawson View Post
    There is absolutely no reason for anyone to proclaim that those languages are not for production usage purely on the basis that their incomplete.
    Maybe it's just the engineer in me, but I thought that's what the word 'draft' means. Incomplete to the point it should ONLY be used for testing purposes and not for production use. Or for the dictionary version: "a first or preliminary form of any writing, subject to revision, copying, etc."

    Subject to revision makes it unsuitable for production use - end of story. That it's not even supported for over 50&#37; of the public (probably more than that real world given FF's artificially inflated numbers, thanks prefetch!) and much of it does NOT degrade gracefully (reliance on multiple backgrounds) or does stuff that the suits will ask "well why the hell can't IE do this? I've seen existing sites do this in IE..."

    It's not a good recipe for success.

    NOT that anyone seems to be paying the least attention to what draft, alpha or beta mean anymore.

    Though that could be my complete distaste for everything HTML 5 except the new form handling speaking, since if you are just talking markup it's a step BACKWARDS in progress from everything STRICT gave us.

  18. #18
    Follow: @AlexDawsonUK silver trophybronze trophy AlexDawson's Avatar
    Join Date
    Feb 2009
    Location
    England, UK
    Posts
    8,111
    Mentioned
    0 Post(s)
    Tagged
    1 Thread(s)
    No-one is arguing that making your work dependant on HTML5 or CSS3 is a good idea, what I've been putting across however is that especially in the case of CSS3, it's entirely possible to have a website function and work correctly and then layer CSS3 on the top to give it additional levels of visual value and flourishes that improve the design. As far as I'm concerned, if you're not dependant on the language but use the draft to enhance what you already have, there's absolutely no reason not to use it, even in a production environment as if it's not supported, it always has the traditional CSS 2.1 to fall back on (and still work with ease).

  19. #19
    Programming Since 1978 silver trophybronze trophy felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, NSW, Australia
    Posts
    16,810
    Mentioned
    25 Post(s)
    Tagged
    1 Thread(s)
    Quote Originally Posted by deathshadow60 View Post
    Maybe it's just the engineer in me, but I thought that's what the word 'draft' means. Incomplete to the point it should ONLY be used for testing purposes and not for production use. Or for the dictionary version: "a first or preliminary form of any writing, subject to revision, copying, etc."
    That was what caused most of the problems in IE. They took a draft version of the CSS 2 specification and implemented it it IE5. The specification changed significantly between that draft and the final standard resulting it IE needing to support two entirely different modes depending on whether pages assume that early draft version (quirks mode) or the final standard version.

    The biggest part of the problem was that IE didn't use the -ie- prefix on the CSS that they should have used for allowing testing of the draft specification but instead used the final names that were eventually given a different meaning in the standard.
    Stephen J Chapman

    javascriptexample.net, Book Reviews, follow me on Twitter
    HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
    <input name="html5" type="text" required pattern="^$">

  20. #20
    Non-Member bronze trophy
    Join Date
    Nov 2009
    Location
    Keene, NH
    Posts
    3,760
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by felgall View Post
    That was what caused most of the problems in IE. They took a draft version of the CSS 2 specification and implemented it it IE5.
    EXACTLY!!!

    But the Internet has no memory - those who forget history...

  21. #21
    SitePoint Wizard
    Join Date
    Jul 2003
    Location
    Kent
    Posts
    1,921
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    I'd say wait ten years then learn html 5, as by then IE13 will start implementing a small part of it.

    Remember your html 4 knowledge will still enable you to produce a working web page 10 - 50 years from now, IF you use a doctype that says it's html 4.

  22. #22
    It's all Geek to me silver trophybronze trophy
    ralph.m's Avatar
    Join Date
    Mar 2009
    Location
    Melbourne, AU
    Posts
    24,176
    Mentioned
    454 Post(s)
    Tagged
    8 Thread(s)
    Quote Originally Posted by Dr John View Post
    IF you use a doctype that says it's html 4.
    ...Or even if you just use <!DOCTYPE html>, which works for all flavors of HTML, apparently.

  23. #23
    SitePoint Zealot ajaxdinesh's Avatar
    Join Date
    Apr 2009
    Location
    India
    Posts
    137
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Angry

    Quote Originally Posted by felgall View Post
    CSS 3 is probably a lot closer to release than HTML 5 is since work on CSS 3 started quite a few years ago while HTML 5 was only recently started.

    See http://www.w3.org/Style/CSS/current-work for where things are at with the varions CSS 3 modules - those parts that say candidate recommendstion are the parts of CSS 3 that are actually finished and which browsers are therefore able to consider implementing.

    HTML 5 is a long way behind CSS 3 as it is still only at an early draft stage.

    I have tested some html code from this url http://www.w3.org/Style/CSS/current-work in the latest version Firefox. But not working. Am not able to see the proper output in this latest version Firefox browser.
    Is it currently in R&D?:
    Cheers,
    Dinesh

  24. #24
    Programming Since 1978 silver trophybronze trophy felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, NSW, Australia
    Posts
    16,810
    Mentioned
    25 Post(s)
    Tagged
    1 Thread(s)
    Quote Originally Posted by ajaxdinesh View Post
    I have tested some html code from this url http://www.w3.org/Style/CSS/current-work in the latest version Firefox. But not working. Am not able to see the proper output in this latest version Firefox browser.
    Is it currently in R&D?:
    If it just says "recommendation" then the standard is finished ready for browsers to implement. That doesn't mean that they have necessarily done so yet.

    If it says anything else then it is still a work in progress. Those that say "Working Draft" are a long way from completion. Those that say "Proposed Recommendation" are close to completion.
    Stephen J Chapman

    javascriptexample.net, Book Reviews, follow me on Twitter
    HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
    <input name="html5" type="text" required pattern="^$">

  25. #25
    SitePoint Evangelist fs_tigre's Avatar
    Join Date
    Feb 2009
    Location
    Close to Chicago, Illinois
    Posts
    517
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Excuse my ignorance but why does it take so long to implement a language like HTML or CSS (years)?
    Thank you very much!!!


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •