Fred, Although I haven't tested it in uPortal 3.1 specifically, there has been built-in support in uPortal for quite a while now to have different user-agents associated with different templates, so that you could have a WML template, XHTML template, etc. I believe.
However, the list of user-agents that come out-of-the-box with uPortal didn't (last I checked, but perhaps it has changed) come with the full list of user-agents possible nor with mappings to appropriate templates for each possible mobile device. For example, an almost full list of mobile user-agents is managed in the wurfl project here: http://en.wikipedia.org/wiki/Wurfl But uPortal (at least in older versions, and I think is true with latest version?) asks the user which template they want to use if it doesn't recognize the user-agent. If your goal is to support every possible mobile device that could hit your portal, you really should hire a company out to help you out that has the experience and expertise as well as a large set of mobile devices and decent-sized QA department that they can use for testing content out. I used to work for a company that has these types of resources available (because they were a mobile content provider and aggregator). For older mobile devices, there were all sorts of quirks about how they supported the various standards. And of course the screen resolutions/width/height varied, and the physical user interface varied. But if your goal is just to be able to support a subset of devices, I'm fairly sure that you could make it work. Additional things to keep in mind when trying to determine what to support: * If it costs the user an additional amount to browse the web on a device that is going to browse content slowly, do you really think they will use it? * The more templates you have and/or more devices and browsers you have to support with the same template/portlets, the more time it will require to maintain those. It isn't just a matter of the one-time cost of developing the template; you will need changes later. * Will the device be able to use all of the portlets you were intending them to use without significant modifications? * How easy will it be for the user to authenticate, etc.? Hope that helps, Gary On May 3, 2010, at 9:51 AM, Frederic Ravetier wrote: > Hello Jennifer, > > Thank you for your answer. I already watch this video. > Let me give you a quick draw in order to understand our level of knowledge > about uPortal: we are doing uPortal deployment and portlet development since > 2005, for French universities, mainly based on uPortal 2.x. > > Is there this user-agent mapping in 3.1 ? > > > We are going to target handset with less possibilities than "WebKit-based > browsers", for example a basic Samsung mobile that support XHTML/CSS. And > using a specific theme (bundle of CSS+images) for mobile is nice but seems > not enough. Because it is necessary to adapt the XHTML code to the > possibilities of the handset. Do you have any ideas? Do you have > suggestions?...? > > Best regards, > Fred > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
