You wouldn't. There would be a seperate .json or .yml file. I would even think that it would be easier to manage this way. As it is right now, you probably have the same section and chapter names repeated in several pages, so if ever you decided to rename a section, you would have to duplicate that change in several places.
Oookay. I have six sections: "Beginning", "(eXtensible) HyperText Markup Language", "Cascading Style Sheets", "JavaScript", "Other", "Appendices". How would I set those up and some chapters in each section?
The W3C also remade HTML as XHTML, releasing version 1.0 (based on HTML 4.01) in 2000 and XHTML 1.1 (based on XHTML 1.0 Strict) in 2001, and proceeded to work on XHTML 2.0 (based on what the experts thought the web needed). XHTML 2.0 was pretty much booed off the web, and the Web Hypertext Application Technology Working Group started updating the venerable language again in 2004. As of this writing, HTML5 remains a work in progress.
Last edited by Mr Initial Man; 04-05-2012 at 02:41 PM.
The W3C also remade HTML as XHTML, releasing version 1.0 (based on HTML 4.01) in 2000 and XHTML 1.1 (based on XHTML 1.0 Strict) in 2001, and proceeded to work on XHTML 2.0
This seems largely correct.
XHTML 2.0 was pretty much booed off the web
This seems like a broad and hard to verify statement. If you're interested in accuracy, then it may be safer to stick to what you can backup with citations.
"Apple, Mozilla and Opera were becoming increasingly concerned about the W3C’s direction with XHTML, lack of interest in HTML, and apparent disregard for the needs of real-world authors."[*]
the Web Hypertext Application Technology Working Group started updating the venerable language again in 2004. As of this writing, HTML5 remains a work in progress.
Sorry, but every post on XHTML 2.0 that I read back them seemed VERY negative towards the language. That, and I wanted to have a rather casual, light-hearted tone to the book.
I dropped XHTML some while back and use HTML4.01 Transitional until HTML5 has all the bugs out of and is finalized (whenever that may be).
The problem with any of them is that developers try to stretch stuff beyond the browser's parameters and have to code in all kinds of extra stuff. CSS drop downs are a good example of this.
It's really. apply the KISS Rule to whatever you do and stop trying to second guess the browser.
I don't know of anyone who likes Flash, so HTML5's animation thing will be a very welcome relief as long as they make it so the dangers associated with Flash cannot be implemented in any way, shape or form.
I don't know of anyone who likes Flash, so HTML5's animation thing will be a very welcome relief as long as they make it so the dangers associated with Flash cannot be implemented in any way, shape or form.
I can't say that I like flash .. but really? You don't know anyone who likes Flash?
... You don't have anyone in your office whose job even depends on the popularity of Flash?
I don't know of anyone who likes Flash, so HTML5's animation thing will be a very welcome relief as long as they make it so the dangers associated with Flash cannot be implemented in any way, shape or form.
Developers are experts at making the worst of any technology. "Make something idiot-proof, and Dame Fortune will hand you a better idiot."
I don't know of anyone who likes Flash, so HTML5's animation thing will be a very welcome relief as long as they make it so the dangers associated with Flash cannot be implemented in any way, shape or form.
What's an HTML5 animation?
I've switched careers...
I'm NO LONGER a scientist,
but now a web developer...
awesome.
Google: html5 animations
There's quite a lot about it.
I think we could consider this still in its infancy. There is some software available and JavaScript is heavily involved from what I see (perhaps too much so). I've not investigated it all that much as I'm now involved in other things.
HTML5's canvas is part of HTML5, so no plugin is needed. This takes it away from a single software developer (Adobe) and opens up stuff. If it is anything like Flash in its results, then we should be seeing graphics/text combined with movies and sound.
Initially there will be the usual playing around with stuff that for all intensive purposes is totally useless (moving an object around inside a box for no other reason than to move it), but can be an inspiration for more practical visual implementation like creating an object and expanding it into a movie etc-etc.
We shall just have to wait and see how it all grows. The possibilities are there and now it's time for the artists to get to grips with packages and concepts to produce some exciting visuals.
The W3C also remade HTML as XHTML, releasing version 1.0 (based on HTML 4.01) in 2000 and XHTML 1.1 (based on XHTML 1.0 Strict) in 2001, and proceeded to work on XHTML 2.0 (based on what the experts thought the web should use). XHTML 2.0 was never really adopted. To begin with, it had very little to do with classic HTML and was not backwards-compatible, which meant that it was simply another language that browsers had to support—even though it technically did the same thing as HTML. Developers thought that the W3C had lost touch with developers and the Web Hypertext Application Technology Working Group was created outside of the W3C to start updating the venerable language again in 2004. As of this writing, HTML5 remains a work in progress.
Originally Posted by Mr Initial Man
Reply With Quote
).
Bookmarks