HTML
  Home arrow HTML arrow Page 2 - Honey, I Shrunk My Website
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
HTML

Honey, I Shrunk My Website
By: Keith Reichley
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 3 stars3 stars3 stars3 stars3 stars / 3
    2002-10-22

    Table of Contents:
  • Honey, I Shrunk My Website
  • Decide What to Publish

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Honey, I Shrunk My Website - Decide What to Publish


    (Page 2 of 2 )

    Your first step is to decide what to deliver to your PDA-equipped audience. Start small and be selective. News stories, articles, product descriptions and order forms are good candidates for a channel's timely content.

    You want a simple 2-3 level navigation, such as a main menu, submenus (optional) and content pages. For example, our WEBtheJOINT channel consists of two levels - a main menu of articles, and the articles themselves.

    Keep the sum total of your pages to 50-100KB in size. AvantGo enforces limits of 256KB per channel, 32KB per page. Pages should be short and limited to one subject.

    Coding Basics
    AvantGo supports HTML 3.2 -- with exceptions. Forget about using frames and image maps. Image tag attributes like height, width, and text floating won't fly either. Text formatting capabilities are limited. The FONT and BASEFONT tags are useless.

    Keep screen size in mind. You can design your pages for the lowest common denominator (Palm's 150 x 150 of usable screen). Or, you can use an HTTP Header (described in the next section) to adapt your content to fit the larger screens of Windows CE and HPC Pro devices.

    With PDA's limited graphics capabilities, your safest bet is to use high-contrast grayscale images with a width of 150 pixels or less. Color images will be converted to grayscale by non-color devices. Be sure to use alt tags.

    Using HTTP Headers
    Once you've identified your channel's content-to-be, you face the prospect of optimizing it for the PDA. You can create separate versions for the standard browser and for PDA's, but the experienced developer may prefer to use JavaScript, PHP or another scripting tool to optimize pages on-the-fly. Use HTTP headers to determine the client's operating system, screen size, color capabilities, and more.

    For our channel, we use PHP simply to determine whether the user's browser is "AvantGo". If it is, a downsized header file (PDA_header.inc) containing the HTML for one small image and a few navigational links is called, rather than the full-blown header (FULL_header.inc) that our regular site's visitors see:

    <?php
    $agent = getenv("HTTP_USER_AGENT");
    $handheld = strpos($agent, "AvantGo") ? "Yes" : "No" ;
    if($handheld == "Yes")
    {
    include("../PDA_header.inc");
    } else {
    include("../FULL_header.inc");
    }
    ?>


    Click here for the full scoop on using HTTP Headers.

    Create Your Content
    Design a small home page that gives the visitor a clear idea of what lies beneath. A main menu is good. Second and lower level content can either be created from scratch, or existing pages can be scripted with HTTP Headers as described above to eliminate the need for separate PDA-friendly versions.

    Save the home page file and any other new or modified files on your web server. Consider putting the home page file into a separate subdirectory with header, footer and image files used solely for your AvantGo channel.

    Using Forms
    Any website worth the cyberspace it occupies has some interactivity via forms. AvantGo and PDA's can handle just about any kind of form. Be sure to keep in mind screen size and the HTML limitations mentioned previously.

    The form that your user fills out and submits on the PDA is saved in the Forms Manager. The next time the user sync's to your channel, AvantGo sends the completed form to your server where it is processed as usual by your form's cgi-bin or other action.

    The only major change you need to make to the form is to customize the Submit button with a little JavaScript. Replace the standard:

    <input type="submit" name="submit" value="Submit">

    with:

    <input type="button" name="submit" value="Submit"
    onClick="document.forms[0].submitNoResponse(
    'This is the message that will be displayed after form
    submission',
    false,
    true);
    back()">


    The submitNoResponse function is AvantGo's way of displaying a confirmation message t the user, and of specifying whether the form is hidden in the Forms Manager (in this example, "false") and whether multiple forms can be submitted ("true").


    Create Your AvantGo Channel
    If you haven't already done this, sign up for a free AvantGo account. Next, use AvantGo's wizard to create your channel. You'll specify the location of your home page, link depth, and more. This should take all of five minutes.

    When finished, click on "Export Channels" to generate the URL that you can copy and post on your site so that customers can sign up for your channel. The URL will look like this:

    http://avantgo.com/mydevice/ autoadd.html?title=WEBtheJOINT&url=ht
    tp%3A%2F%2Fwww.webthejoint.com %2Favantgo%2Findex.php&max=100&dept
    h=2&images=1& links=0&refresh=always&hours=1&dflags=127& hour=16&qu
    arter=30&s=00

    It ain't pretty, but it works like a charm. When you go to this URL the channel will be added to your "My Channels" list. Sync up your PDA, and then click the AvantGo icon on your PDA to test your handheld-friendly site.

    If you don't own a PDA, don't worry. Download the Palm OS Emulator onto your Windows/Mac/Unix computer here.

    Alternative PDA Browser Solutions
    AvantGo's not the only game in town, but it's way ahead of whatever's in second place.

    Blazer: Palm browser that can access virtually any site on the web, but strips out unsupported content (streaming media, Java, JavaScript). Unlike AvantGo, Blazer does not store content on the PDA. Cost: US$19.95.
    http://www.handspring.com/software/blazer_overview.jhtml

    Web Clippings: Stand-alone applications supported by Palm VII handhelds, Palm Vs with the OmniSky modem, and other handhelds with the Mobile 1nternet Kit installed.
    http://www.palmos.com/dev/tech/webclipping/

    What Are You Waiting For?
    If you haven't already, sign up for a free AvantGo account. Subscribe to several channels -- you'll quickly find some with elegant navigation and valuable content. Yours could be one of them. Give it a shot.
    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

     

    HTML ARTICLES

    - Comparing Browser Response to Active Client ...
    - Testing Browser Response to Active Client Pa...
    - Active Client Pages: Completing the Code for...
    - ACP and Browsers: Setting up an Example
    - How Browsers Respond to Active Client Pages
    - Completing a Tree with Active Client Pages
    - HTML Form Verification and ACP
    - Building an ACP Tree
    - Completing an ACP 3D HTML Table Image Gallery
    - Building an ACP 3D HTML Table Image Gallery
    - A Multiple Page Image Gallery with Active Cl...
    - Building an Image Gallery with Active Client...
    - Concluding a Menu for All Browsers
    - A Vertical Menu for All Browsers
    - Downloading Long HTML Pages with ACP







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek