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:
> >
> > Recall seeing that you can use a temp skin to override the regular skin.
> >
> > Thinking of using this to provide a mobile version of the same data.
>
> Sure it could be done, somehow. Just need something to trigger, like a
> little php script that says somehow if browser, set skin to this. It
> can be done in index.php, a config file, a plugin, wherever. Just
> reset $BOLTskin. And the new code v3.18 should handle it nicely.
>
> Only thing I'm not sure exactly what to use to tell whether or not the
> browser is a mobile. Can you help?
>

Wasn't thinking so much as an automatic method, but I could  see that
working for some devices.  Many provide agent info that clearly make them
mobile devices.

Rather I was thinking of  an option which would tell BW to use the mobile
skin.

For example.... an SMF forum will revert to mobile mode when the following
is added to a SMF site

?imode

Example:

http://www.weather-watch.com/smf/index.php

is normal... but

http://www.weather-watch.com/smf/index.php?imode

is mobile.

An alternative would be to setup a page called mobile which sets something
that stays with the connection providing the alternative skin.

Or something like  ?skin=xx  or ?s=xx

If this worked, you could do first option as well... have an autodetect
mode.  I know that wordpress has that option in one of its plugins.  Could
look there to see what they are looking for for detection.

> Also, can you add a group to a membership?  Like
> >
> > In hrgroup.group
> >
> > user1
> > user2
> > user3
> > @sagroup
>
> Shouldn't that be page group.hrgroup?  I won't work the other way, if
> you are talking about real groups...
>

yes... typo..  Thanks for the tips on that stuff.


>
> No, don't have this capability but I imagine we could add it. But
> could you make a case why this might be needed? If you wanted to give
> permissions to the members of two groups, couldn't you just do...
>
> site*: @group1,@group2
>
> Where sagroup is another membership group with 10 or so members in it.
> >
> > Tried to do it but it didn't work.  Perhaps there is a way to do with
> using
> > different syntax?
>
> Not that I know of. Though another idea is to allow limited markups in
> group pages when assigning groups. Imagine putting on a group page
> something like this:
>
> user1
> user2
> user3
> [(include group.othergroup)]
> [(search group=login data='state=ok' fmt={+p2})]
>
> Can you see the possibilities? The only draw back is it could slow
> down logins on pages with large numbers of groups.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to