域卡的卜 Vicker’s Blog

Hong Kong Adobe Flash platform (Flex, Flash and AIR) developer
  • rss
  • Home
  • About
  • Resume
  • Flickr
  • Contact

Blog Talk 2 – How to Implement Consistent Framework

Vicker | November 15, 2005 | 11:43 pm

I think all of you have done the redesign assignment already and starting to write the report. When you are redesigning the web, I think most of you may have faced a certain problem in mind that is how to make all the pages consistent? As all the pages will have the same html opening tags, meta tags, linking of the style sheets, header navigation bar and the footer copyright declaration part. If I simply copy and paste it to every page, it is time consuming and not easy to maintain in the future. So I want to introduce a few methods here.—————————————————————1. FramesI think I don’t need to talk too much about frames, it is just a standard HTML tag that is easy to implement. It will divide the screen into areas which each area will load it’s corresponding page.The advantage is that it is server independent, any web hosting services can run it. However there are a bunch of problem using frames to achieve consistency which are shown below.- Browser don’t know what to bookmark- Opening the source will open the frameset but not the page- Search engine will have problem crawling the pages—————————————————————2. Client Side IncludeInclude means that you will insert one page (in here HTML) into another one. For example, you may have a navigation menu which will appear in every page. So you can simply include the navigation menu page into every pages of your web site to achieve consistency. In here client side include means the include process is done on the client side which can be achieved using JavaScript.Here is the JavaScript example:

<script type=”text/javascript”>function print_header (){var elem = document.getElementById (”header_content”);elem.innerHTML = “<table><tr>…….</tr></table>”}</script><span id=”header_content”></span>

The advantage of using client side include is that it is server independent just like frame. Any browser which supports JavaScript will work. However there are a few disadvantages as below.- Destroying HTML structure (if you look at the JavaScript structure, you can see that it is some sort of program and strings instead of standard HTML)- Hard to maintain- Search engine won’t be able to crawl because it is made at client side—————————————————————3. Server Side IncludeIn contrast, server side include is done by some server side scripting. It can be some simple ones like the SHTML or some complicated ones like PHP, ASP or JSP. The pros of server side include is that it can totally eliminate all the disadvantages in the previous methods. However the main disadvantage is that it is server dependent, and it is sad that CityU personal web do not support these.The example of SHTML is illustrated below:=> index.shtml

<!–#include file=”header.html”–><body>……</body><!–#include file=”footer.html”–>

=> header.html

<!DOCTYPEhtml PUBLIC “-//W3C//DTD XHTML 1.1//EN”"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd”><html xmlns=”http://www.w3.org/1999/xhtml” xml:lang=”zh-tw”>

More resources and tutorialsHow do I include another file inside a HTML file?How do I include one HTML file in another?

Related posts

  • 繼續學會去輸 (0)
  • Web Content Accessibility Guidelines (0)
  • The Form Assembly (0)
Comments
No Comments »
Categories
Web Usability
Tags
frame, HTML, include, PHP
Comments rss Comments rss
Trackback Trackback

Making Searchable Flash Content

Vicker | October 19, 2005 | 9:31 am

I have seen quite a number of classmates taking about how bad Flash is when considering about usability and accessibility. Take for an example Flash give too much freedom to the designers resulting that Flash always give a non standard interface.Another main problem that mentioned is that Flash either can’t be identified by the search engines and searched effectively.Having a short research on this, I have summarize a number of methods to make Flash more searchable.1. Preparing both Flash and HTML version of the webThis method is the best among all the methods, but the most time consuming one.It can achieve two purpose. First, allowing the contents of your web (in HTML version) being indexed by the search engines. Second, provide alternative browsing method without Flash for the visitors.2. Using a HTML file to embed the Flash, then applying META tagThe easiest method to apply which is still very effective. By means of the META tag, search engines can easily locate and categorize what the Flash content is about.3. Separate the content and interfaceInside the Flash movie, all the contents are not directly written inside. An external data source is used, e.g. using database to store the data and some server side script to forward the data to Flash. The advantage is that additional to being searchable, it is also portable. Because Flash is just an interface, the data is portable to other platforms, let say building RSS feeds.4. Personal submission to the search enginesNo need to explain too detail here. This must be a guaranteed method.Actually the search engines are improving too. Say for an example Google already have their own mechanism to search Flash contents. Further, Macromedia have provided the Flash Search Engine SDK for users to build their own search engine.No matter what, as a Flash developer, we should bear in mind that fancy is not everthing.ReferencesShari Thurow, Optimizing Flash for Search EnginesJames Ellis, Accessible Flash PartsDeveloping User-Friendly Flash ContentFlash and Search Engines

Related posts

  • Google 同 Yahoo! improve Flash indexing (0)
  • 重返 EE (0)
  • 時光倒流第二集 - Thanks FLABER (0)
Comments
No Comments »
Categories
Web Usability
Tags
Flash, HTML, meta, SEO
Comments rss Comments rss
Trackback Trackback

The Form Assembly

Vicker | September 27, 2005 | 11:48 pm

HTML Form, I guess anybody who written some web pages before should be familiar. It is not a really hard one actually. With some form elements like input, select, options, etc… the form already works. However is it usable and accessible? Have you done enough form validation? Have you provide enough labels for the form elements?Building a good HTML form is not a easy task, especially if you want to follow those standards. Googling for a while, found out this web which is great to achieve the mentioned points above. The Form Assembly (http://www.formassembly.com)Same as other informational web sites, there are articles and tutorials on building the web forms. But my focus are on the three links on the left hand side of the web.Form BuilderA web tool which will help you to build your form in a standard format. What you have to do is just filling your requirements and thats it.Form LibraryHere you can access a large number of templates with different stlye and even different language.Form GardenPersonally I suggest this to everyone, which is a CSS form builder. You can select the styles available on the right and test it in the center. After your selection, you can simply download the CSS and use it in your own web page.It is so convenient with all these handy tools and the most important thing is that we can learn from their source and design :p

Related posts

  • Web Content Accessibility Guidelines (0)
  • Sometimes I hate Flex… Sometimes (0)
  • Making Searchable Flash Content (0)
Comments
No Comments »
Categories
Web Usability
Tags
CSS, form, form assembly, HTML
Comments rss Comments rss
Trackback Trackback

Web Content Accessibility Guidelines

Vicker | September 13, 2005 | 10:54 pm

Before having the first lecture there are already quite a large number of things that can be explored simply browsing Andy’s web.You may notice that there are a number of small icons on the bottom of Andy’s course web. Saying W3C XHTML, W3C CSS, W3C WCAG, BOBBY 508 and BOBBY AAA.For the first two, I guess is quite familiar to many people. They are the standards posted by W3C. (World Wide Web Consortium) Using the validators provided by them, (HTML validator and CSS validator) anyone can check whether their web page fullfill the requirements of the standards. If it is a success, they can place this icon on their web.But how about WCAG, 508 and Bobby??Due to my curiosity, I have made some search on W3C. Actually WCAG stands for Web Content Accessibility Guidelines. It is a guideline which will make a website more accessible. (WCAG 1.0) Section 508 is something similar to WCAG but written in US Federal law.WCAG have a total of 3 accessibility compliance, A, AA and AAA. (where AAA is the best and of course the hardest to achieve) Although W3C do not provide any automated WCAG checker, we can still check it through WebXACT. (WebXACT) I guess the former name is Bobby but now changed. However even WebXACT can not do all the testing inside the guideline, because some of them are not coding related, e.g. color matching.Although it is hard to acheive all these standards, I think as a web designer we should try our best to do at least most of these. This improves not only the speed of loading the page but also helping our visitors to browse.

Related posts

  • The Form Assembly (0)
  • Alternate Style Sheets (0)
  • 論壇升級 2.5 (0)
Comments
No Comments »
Categories
Web Usability
Tags
bobby, CSS, HTML, validation, W3C, WCAG, webxact
Comments rss Comments rss
Trackback Trackback

Meta

  • Register
  • Log in
  • Entries RSS
  • Comments RSS
  • WordPress.org

Certification


Adobe MAX 2008

Categories

Archives

Tag Cloud

Adobe MAX design pattern Molyx Apple VideoDisplay PHP JAWS braille APICTA John Koch Lego MovieClip Gary Wong music Densha Otoko Eva Shi good dog u Adobe WMV form gundam Battlenet HTML blog flv Web Usability Flex Builder hea job hunting include YouTube CityU Chris Liang Hacken Lee Laszlo Flash UI sitemap validation textformat protoype CSS OO birthday ActionScript bt business Misaki Ito AIR FYP Andy Chun web page XHTML Tim Shiu the core OSS W3C exhibition depth manager flash video encoder ACSS MOV Mac AdvancedDataGrid PS2 flysbookmark prototype WCAG WYSIWYG Cyber Formula XML Flex FAQ WarCraft accessibility stylesheet flysforum textfield hyperlink component color selector meta SEO frame color algorithm Munsang College FLABER Macromedia bobby webxact Experts Exchange HKICTA family form assembly suck Flex presentation Yahoo freelance Google

Flickr

0511_web_usability_asg_a.jpg 0509_battle_system_1_5.jpg 0601_flaber_0_4_7.jpg dojang1.jpg english2.jpg vector_td msc_bio_v3_1.png wanshan.jpg iad2.jpg msc_bio_v2_3.png 467138530_19ab43538e_o 11092007102.jpg 0511_web_usability_asg_b.jpg msc_bio_v1_2.png 469811325_48b2617196_b diarybox1.jpg

Blogroll

  • Eva’s Blog
  • Way’s Blog

RSS FxAIR.org

  • ActionScript for Random Numberic Text Lucky Draw
  • Post in cookbook to win a copy of Flex 3 Pro
  • Adobe Flash Player 10 Release is out
  • Adobe CS4 Launch Seminar
  • Flex 3 + external swf with embedded video
  • Flex & AIR @ BarCamp Hong Kong on 6 Sep.
  • Mojave Experiment by Microsoft
  • FotoViewr beta
  • RIAJobs
  • Cairngorm on opensource.adobe.com
rss Comments rss valid xhtml 1.1 design by jide powered by Wordpress get firefox