On Tue, Oct 6, 2009 at 7:30 PM, Kevin <[email protected]> wrote: > On Tue, Oct 6, 2009 at 3:31 PM, The Editor <[email protected]> wrote: >> >> On Tue, Oct 6, 2009 at 5:17 PM, Kevin <[email protected]> wrote:
> An alternative would be to setup a page called mobile which sets something > that stays with the connection providing the alternative skin. I like this method most. Why not create a page called mobile plus a mobile skin. Then on that page use the cookies plugin to set a mobile cookie of some sort... [(setcookie mobile=true expires="+10 days")] Lastly in config.php, put if ($_GET['mobile'] == 'true') $BOLTskin = 'mobile'; I suppose we could put all of this in a plugin, called mobile with a backup file containing the code.skin.mobile and code.style.mobile. Plus the page mobile, perhaps with content like [(include main)] [(mobile)] We would create a custom mobile function to set the cookie and have the skin set to mobile on the mobile page or when the cookie is set. If you would design a simple mobile skin/css (navigation is the problem I guess) I'll be happy to pull the plugin together. Shouldn't take 5 minutes. Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
