HTML 4 to HTML 5 and Web Applications

HTML5-Wiki is being developed as the next major revision of HTML (Hypertext Markup Language), the core markup language of the World Wide Web

HTML5-W3C A vocabulary and associated APIs for HTML and XHTML. W3C Working Draft 4 March 2010. W3C.

HTML 5 Tag Reference at W3Schools

What is the WHATWG?

The Web Hypertext Application Technology Working Group (WHATWG) is a growing community of people interested in evolving the Web. It focuses primarily on the development of HTML and APIs needed for Web applications

HTML5 differences from HTML4

Current HTML HTML-4

HTML Help by The Web Design Group

HTMLHelp.com is maintained by the Web Design Group to provide Web authoring reference material, tips, and answers to frequently asked questions

Make Apps and Applets Resource Friendly

Some Apps and Applets or Widgets take more CPU and Memory Resources, Here is a gadget made to demonstrate it Aquatic Animations. When the Screen shows entire Aquarium, CPU Loads use FreeMeter to study. The 1 GHz computers are also affected. We cannot assume all have state of the art machines and browsers. The Latest Desktop Programs also just Choke the Machines.

The CPU is being made faster and multicore and the OS Makers again overload the Architecture by luxurious resource hungry Systems. This has been happening since 286, but most pronounced now. The OS can be developed without making it Beefy and Heavy. The CPU cant keep getting faster. It needs to be Energy Efficient and the OS Slim and Sensible.

The only solution is to move to Handhelds and Webapps to end this Runaway OS Design Process.

Conclusion -

The computing capability requirement for a future user is enormous, The data and databases unmanageable. Neither can he carry a Supercomputer in his Knapsack, nor can he afford to keep it in his home. He would either way not use it to full capacity.

He can carry or keep on his desktop a Light Weight Affordable Viewer alone. Hence "Move the Computation Online".

The User of the future will say "Just gimme an Ajax". He will pay for the Results. Not a Supercomputer.

HTML Help - Web Design Group

HTML Help - Web Design Group

The Web Design Group was founded to promote the creation of non-browser specific, non-resolution specific, creative and informative sites that are accessible to all users worldwide. To this end, the WDG offers material on a wide range of HTML related topics. We hope that with this site as a reference, you will be able to create Web sites that can be used by every person on the Internet, regardless of browser, platform, or settings.

• HTML 4 Reference
• HTML Help Forums
• HTML Validator
• Cascading Style Sheets Guide
• CGI Programming FAQ
• Guide to Accessibility
• Improving Search Engine Rankings

Alan Woods Unicode Resources

Alan Wood's Unicode Resources

Information about Web browsers, fonts, editors, word processors and various utilities that support Unicode, plus pages for most of the Unicode ranges that enable you to test your browsers and fonts.

Character entity references in HTML 4.01

An indexed list of the 252 named entities (for letters with diacritics, Greek letters and various special characters) that are supported in HTML 4.01.

Information about your Web browser, detected by:

• JavaScript
• PHP: Hypertext Preprocessor
• SSI: Server-side includes

Markup Validation of HTML pages

Some tools that help you build valid html webpages.

Clean up pages with html tidy

w3.org/People/Raggett/tidy
tidy.sourceforge.net

Editors or Composers.

nvu.com/features.html
mozilla.org/products/mozilla1.x
evrsoft.com/1stpage3.shtml

see also ...

thesitewizard.com/webdesign/htmlvalidation.shtml
addons.mozilla.org
validator.w3.org
htmlhelp.com/tools/validator

I think you can clean with the tidy html free tool. or use Nvu or 1st page 2006. I also made a new discovery,zoundry.com can clean code and validate online. It can also save the post as html page. It interfaces with many CMS and Blog Services. Includes Drupal and Wordpress Lamp-Apps. Blogger and many more Web-Services.

This post by zoundry Validated xhtml .

Webmaster Basics

I am putting back some of my old posts (~1999) after review and corrections. Excuse Spelling, Grammar and Content mistakes.

• Keep information 3 clicks away to improve accessibility, have a search and site map too.
• Html tables can be sized with % and not by pixels, so that it can resize according to different computers of say 1024*768 and 800*600. use pixels for single columns only or when you put all in a 740px limited page.
• FTP not working use passive mode for fire walled sites. Use Filezilla.
• Avoid frames even iframe of dhtml, use the noframes option. Main problem is that visitors cannot get back to your frames site after finding a nice page on the search engine, or keep a link on every framed page to home index.html with '_top'.
• Webpages should be usable, at 1024*768 and 800*600. viewable by mozilla 1.0+ and IE5+, most used vga settings are 1024*768 high.
• The KiloByte weight of a single web page with images, flash, js and css could be a max of 100 kb for up to 10,000 views per day, 200 kb for 1000 visitors per day, 500 kb if you have only 10 visitors per day. Due to bandwidth requirement of server and other bottlenecks. A page of 500 kb will cause great frustration to some users at busy times and poor connection. Use >1Mb pages only for Intranet or offline work.
• Always keep your local website in one folder like 'myweb' all sub folders within that, to a large extent use lower case, 8.3 format like anewpage.htm, .html and .js etc. If you use long file names do not use space in file names or folders, try something like my-best-book.html.
• Images should be like ../images/cat.gif or pictures/jug.jpg. not like file://d://myweb/images/cat.gif this will not work url should be 'relative' only or 'absolute' like http://www.sun.com/jug.png.

Widen Website Usability - Keep it Simple.

The webpages you make should be verified in all major browsers. The pages, webapps, scripts and applets must work well in Linux, Mac and xp.

Making it very flashy, Animated DHTML navigation, etc. may impress a few but may be a big usability problems for some visitors, search engines also will have trouble indexing your pages. Avoid too much frames and scripts too, use some CSS. DHTML-CSS generation in some Wysiwyg work only in certain browsers and OS - Beware.

• The Pages must be Viewable by 800*600 and 1024*768 Monitors.
• The PNG transparency must work for few versions of all above browsers.
• The Main Pages must load quickly for users of Broadband and Dial-up-Networking.
• Very Big Jpeg, Pdf, Mpeg, Flash, mp3 or Webapps must load only on Request.
• A Menu / Toolbar, Breadcrumb, sitemap and a search to Navigate and Return.
• Appropriate Meta-Tags, Proper title wth not more that 6 or 7 words.
• An About-Blog-Cell in Main Page to indicate in short what the website is for.
• An easily Accessible Online email form to contact you easily.
• A clear indication of who is the webmaster or company behind website.
• The Font size should not shrink and become unreadable on some browsers.
• light background preferable with dark 12px font or better.
• Inform in advance, pages about cookies, activex and java that needs information.