On Sun, May 1, 2011 at 11:11 AM, shelan Perera <[email protected]> wrote: > On Wed, Apr 13, 2011 at 3:29 PM, Nicolas Muller <[email protected] >> I am working too about a mobile website with roller. These are my ideas! >> >> 1) Create a group of news pages dedicated for mobile into an existing blog. >> It is powerful roller function to be able to create pages (drupal can do it, >> wordpress not). Associated these pages with a new domain (m.mydomain.comfor >> example). You could do create a new blog and display information through >> planet. It >> is possible but a little hard to do
Interesting idea. Do I understand you correctly? Instead of creating a mobile theme for each blog, you propose to create an aggregation of all blogs on the site using Roller's built-in planet aggregator? That is not a bad idea, but I would still like to see Roller have the ability to provide a separate mobile theme for each blog. >> 2) Use DetectMobileBrowser.com from this tutorial to switch from your >> normal site to the mobile one. That appears to be a client-side technology, useful for directing a web browser to the mobile version of a weblog. It's available for use under public domain license, so we could consider using it in Roller. >> 3) USE JQUERY MOBILE :) Forget other libraries. >> It is easy easy in one hour with doc to have a blog running with mobile >> templates thank to jqueymobile JQuery does rock, but I'd like theme authors to be able to use whatever JavaScript libraries they want -- and not be forced to use JQuery. However, I believe Shelan plans to create at least one mobile theme for Roller and be could choose to use JQuery. >> Nota bene : A major point will be to have a way to detect mobile from vm >> template. >> In order to reduce page weight. "Display:none" with css is not good for >> mobile design. >> It is not necessary to load hidden data. User experience is wrong with it. >> Another idea would be to add this info into theme.xml >> >> I will publish a code source to have this information into vm template. I >> have to do it Yes, I agree. We want templates to be able to detect need for mobile pages, on the server side, and that is different from what DetectMobileBrowser.com because it works on the client side. > Thanks for the ideas and feedback.After a bit of searching i am trying to > use WURLF[1] to assist in mobile detection.There are two things which become > handy in using this. > > 1) Identifying the device > > 2) Identifying the device capability. > > At present i am evaluating its reliability and functionalities.I thinkat the > filtering stage we can get the user request and let the WURLF to parse it > and get the device.(As convenient as wurfl.getDeviceForRequest(request)).So > we can decide the rendering after that according to user preference.( Unless > user preferred a desktop or full theme always.) > > I think we can fine tune it more since WURLF can give the device > capabilities.So it we may have to scale down the rendering for some devices > which do not have some requirements. > > [1]http://wurfl.sourceforge.net/ Unfortunately, WURFL is released under a GPL license and Apache projects are not allowed [1] to depend on or ship GPL code. I'm not sure we need something as powerful as WURLF... how much do we need to know about the device? - Dave [1] http://www.apache.org/legal/resolved.html#category-x
