Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 45883 invoked from network); 22 Sep 2005 20:31:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Sep 2005 20:31:01 -0000 Received: (qmail 77516 invoked by uid 500); 22 Sep 2005 20:30:57 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 77203 invoked by uid 500); 22 Sep 2005 20:30:55 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 77188 invoked by uid 99); 22 Sep 2005 20:30:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2005 13:30:54 -0700 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=DNS_FROM_RFC_BOGUSMX,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [69.59.195.3] (HELO pyramid-02.kattare.com) (69.59.195.3) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Sep 2005 13:31:01 -0700 Received: from SYNAPSE (69.37.177.227.adsl.snet.net [69.37.177.227] (may be forged)) (authenticated bits=0) by pyramid-02.kattare.com (8.12.10/8.12.11) with ESMTP id j8MKUUO0030682; Thu, 22 Sep 2005 13:30:31 -0700 From: "Kito D. Mann" To: Subject: [ANNOUNCE] New article on writing WAP renderers Date: Thu, 22 Sep 2005 16:42:01 -0400 Message-ID: <02ad01c5bfb6$181c5430$6401a8c0@vivid.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hello, I just wanted to announce a new article at JSF Central entitled = "Developing Unwired Components". Here's an excerpt: "The proliferation in recent years of web-enabled devices has brought tremendous challenges to application developers, with the need to = develop components that can work across various platforms. For example, = extending an application built for a standard web browser to work on a WAP device may require components of your web application to be rendered in more than = one way. It is tempting to think that if you use JSF it will be a simple matter = to extend an application built for a standard web browser to work on a WAP = 2.0 device, requiring adjustment only for screen size. However, some = components (such as a table) are not viewable on mobiles, while other components = don't work because of the bugs in WAP browsers (which are more common than is usually recognised). Thankfully there is a solution. We can use JSF to extend WAP with self-programmed components supported by render kits. This article will = show you how to implement JSF components that use different renderers = depending on the device used. This is achieved by separating the rendering from = the rest of the component." Read the rest of the article here: http://www.jsfcentral.com/articles/unwired_components.html. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kito D. Mann (kmann@virtua.com) Principal Consultant, Virtua, Inc. (http://www.virtua.com) Author, JavaServer Faces in Action=20 http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info Are you using JSF in a project? Send your story to = trenches@jsfcentral.com, and you could get your story published and win a free copy of JavaServer Faces in Action!