15 replies to this topic

[paulobrien]

At the moment, I don't see an obvious way to define a mobile skin for front page and article views in IP.Content. This means that when people hit the front page of my site (IP.Content), they get a munged up view of the mobile forum skin and my desktop article view.

A fix for this would be really useful (or i'll have to roll my own I guess!).

P

[WD.]

Yes, something like this http://community.inv...te-mobile-skin/ for content would be ideal!

[bfarber]

Yes, something like this http://community.inv...te-mobile-skin/ for content would be ideal!

It's not really that simple, I'm afraid, since administrators set the page content and the database templates in the ACP.

Nevertheless, mobile support is something on our agenda.

[WD.]

It's not really that simple, I'm afraid, since administrators set the page content and the database templates in the ACP.

Nevertheless, mobile support is something on our agenda.

I suppose... I just thought IP.Content could come with a default mobile skin as it does for a desktop version as such: Pages would probably need to adopt the default ipb wrapper (mobile version) as database templates probably should. But of course you and other staff would have more insight. I find the default ip.suite architecture well formatted regardless. A solution I had wondered in the past was for article, page, and database templates have a separate demo mobile template that could be tied to a global mobile wrapper (and "untied" if desired via coding). In regards to a pages, each page could have a "mobile" tab for the HTML to be inserted. Obviously a single column layout would be advised as a simple solution for small devices, phones, to large devices, tablets.

[paulobrien]

A way to detect whether using the mobile skin in a page would be a useful start so we could at least define our own template differences...

P

[bfarber]

There is a way already (post in the help forum if you need assistance with that).

[Rimi]

It's something like

<if test="$this->registry->output->skin['set_id']==2">Code</if>

Of course that won't work on pages. You need a page template or block.
And your mobile skin's ID should be 2. Don't see why it wouldn't be.

[Stenis]

I vote for fixing mobile support for IP.Content ASAP. One way of doing it can be a landing page saying "welcome, this page does not yet support mobile browsers. You have two options: Proceed to mobile version for forums, gallery etc or use the full version skin to access the content".

[alexp999]

I have mobile support working great with IP.Content.

The problem is with the page content and not the skin or the app.

While I agree more could be done with the default templates, I just make a copy of them and make a few edits so it works nicely. Like only showing the sidebar and blocks if it not the mobile skin using code similar to above.

[WD.]

I have mobile support working great with IP.Content.

The problem is with the page content and not the skin or the app.

While I agree more could be done with the default templates, I just make a copy of them and make a few edits so it works nicely. Like only showing the sidebar and blocks if it not the mobile skin using code similar to above.

Isn't the solution to have a different page content for mobile versions?

[Rimi]

Isn't the solution to have a different page content for mobile versions?

Best solution is amazing css techniques.

[alexp999]

Isn't the solution to have a different page content for mobile versions?

Yeah, thats what I meant, I use conditionals on the page content mainly, and then a few conditional tweaks to the article templates so they show correctly.

[paulobrien]

So which variable / technique are you using to detect the mobile skin? The things I tried in the page templates didn't work...?/

[alexp999]

Right, well I use the following for my main index page, you will need to make sure the page is set to Raw PHP though:

if ( $this->registry->output->skin['set_key'] == 'mobile' ) {
	echo '{parse articles}';
} else {
	echo '
<div class="ipsLayout ipsLayout_withright ipsLayout_largeright clearfix">
	<div class="ipsLayout_right">
		{parse block="latest_posts"}
   	 ...
   	 ... // More blocks here
   	 ...
	</div>
	<div class="ipsLayout_content">
	   {parse articles}
	</div>
</div>';
}

Then in the article/database/page/block templates, I use the following to control whether certain parts get shown:

<if test="$this->registry->output->skin['set_key'] == 'mobile'">...Stuff Here to only Show on Mobile...</if>

<if test="$this->registry->output->skin['set_key'] != 'mobile'">...Stuff Here to NOT Show on Mobile...</if>

[gxgEric]

This really seems old fashioned. Why not just make the entire default template responsive?

[GreenLinks]

This really seems old fashioned. Why not just make the entire default template responsive?

 

I personally don't like responsive designs. Instead of responsive , i prefer direct mobile style or mobile app.