> Take a look and maybe link it from your usenet/wiw page as a mobile/pda > link to the resource?
I could of course, but I'm not seeing the point, really - maybe I'm just being thick, but what's the difference with the link to the real page? AFAICS the original page works just as well on a mobile phone... Am I missing something (obvious even maybe)?
-- Els http://locusmeus.com/ Sonhos vem. Sonhos vão. O resto é imperfeito. - Renato Russo -
>> Take a look and maybe link it from your usenet/wiw page as a mobile/pda >> link to the resource?
> I could of course, but I'm not seeing the point, really - maybe I'm > just being thick, but what's the difference with the link to the real > page? AFAICS the original page works just as well on a mobile phone...
Seems to work just fine (only minor issues that you'd want to address if pushed) using Ericsson P910 here.
> Am I missing something (obvious even maybe)?
another opportunity to worship at the feet of gods?
William Tasso wrote: > Fleeing from the madness of the LocusMeus.com jungle > Els <els.aNOS...@tiscali.nl> stumbled into news:alt.www.webmaster > and said:
>>> Take a look and maybe link it from your usenet/wiw page as a mobile/pda >>> link to the resource?
>> I could of course, but I'm not seeing the point, really - maybe I'm >> just being thick, but what's the difference with the link to the real >> page? AFAICS the original page works just as well on a mobile phone...
> Seems to work just fine (only minor issues that you'd want to address if > pushed) using Ericsson P910 here.
'if pushed' - do I need to push you to get you to say which minor issues? ;-) Are these issues absent in the special mobile phone version by google's /gwt/ ?
>> Am I missing something (obvious even maybe)?
> another opportunity to worship at the feet of gods?
not sure what you mean - once people already are on my site with their mobile phone, I'm guessing they don't need the special mobile phone version to get to a next page?
-- Els http://locusmeus.com/ Sonhos vem. Sonhos vão. O resto é imperfeito. - Renato Russo -
>>>> Take a look and maybe link it from your usenet/wiw page as a >>>> mobile/pda >>>> link to the resource?
>>> I could of course, but I'm not seeing the point, really - maybe I'm >>> just being thick, but what's the difference with the link to the real >>> page? AFAICS the original page works just as well on a mobile phone...
>> Seems to work just fine (only minor issues that you'd want to address if >> pushed) using Ericsson P910 here.
> 'if pushed' - do I need to push you to get you to say which minor > issues? ;-) > Are these issues absent in the special mobile phone version by > google's /gwt/ ?
dunno - didn't look at the g-version on my mobile, but I'd guess they don't occur on there as they seem to strip all images and CSS.
I didn't mention what they are as: o the page is perfectly usable. o other phones (or more accurately their UA implementations) will have different display characteristics.
However, things to think on for 'handheld' displays include floats, widths and image sizes. Once you get into the mindset of optimising for handheld it isn't too hard to make the CSS - assuming a good base to start from of course :)
>>> Am I missing something (obvious even maybe)?
>> another opportunity to worship at the feet of gods?
> not sure what you mean - once people already are on my site with their > mobile phone, I'm guessing they don't need the special mobile phone > version to get to a next page?
> I was in /accessibilty/ mode. Any aggregated rss/xml would look fine, I'm > sure.
Completely lost now :\ (YGM)
-- Els http://locusmeus.com/ Sonhos vem. Sonhos vão. O resto é imperfeito. - Renato Russo - Now playing: Bananarama & Fun Boy Three - Really Saying Something
> I was in /accessibilty/ mode. Any aggregated rss/xml would look fine, I'm > sure.
Interesting, I thought it looked like an "accessible" view. (Which is a close approximation to what blind people may "see" [hear] if they use a screen reader.)
However I thought the idea of www.google.com/gwt/n was that it was a "mobile phone gateway and compressor", loosing the formatting but maintaining the content - presumably with the aim of reducing the amount of data that needed to be downloaded by a phone. -- Brian Cryer www.cryer.co.uk/brian
> Interesting, I thought it looked like an "accessible" view. (Which is > a close approximation to what blind people may "see" [hear] if they > use a screen reader.)
> However I thought the idea of www.google.com/gwt/n was that it was a > "mobile phone gateway and compressor", loosing the formatting but > maintaining the content - presumably with the aim of reducing the > amount of data that needed to be downloaded by a phone.
Yeah ... that's the ticket. I understand that well-formed html is viewable in pdas/mobiles but - for a minute - it seemed to me that the xml output of /gwt/n goes a step beyond. The first thing I noticed is that the utility broke Els single page into 5 connect pages.
Because I'm an rss freshman, I propably don't understand all the ramifications and that's okay. It's a learning process for me and I'm here more to learn than to show what I know.
I can see you made it xml, but I didn't see the connection with rss at first. I'm now guessing that you just call .xml files rss feeds?
> that I can load in my newsreader.
newsreader, or feedreader? I'm reading Usenet in my newsreader, and have no idea how to view .xml files in it...
The only thing I understood (or think I did), is that this .xml version of a page loads quicker on mobile phones, and that by splitting a long page in shorter sections, it's more suitable for a mobile phone.
> Obviously, I'm geeking out again. Pardon moi?
Pas de problème ;-)
-- Els http://locusmeus.com/ Sonhos vem. Sonhos vão. O resto é imperfeito. - Renato Russo -
Els <els.aNOS...@tiscali.nl> wrote in news:zkdm53o1qwcs.k20f4my1ss4.dlg@ 40tude.net:
> Didn't get that mail then?
I saw it after I posted here. I didn't want to take up your time twice, Els.
> newsreader, or feedreader?
> The only thing I understood (or think I did), is that this .xml > version of a page loads quicker on mobile phones, and that by > splitting a long page in shorter sections, it's more suitable for a > mobile phone.
I don't know. Maybe that's the problem. I don't have a cell phone, mobile anything, no pda or blackberry. I have nothing to go on except the assumption that shorter pages are easier to deal with on a 1 and a half inch square screen :)
I got the redirect functioning properly. Even if someone lands on an inner page, when they try to go to the index, it will redirect to your page. I've already noticed traffic dropping off the directory and usually only get a visit from an old link rather than a search result.
Fleeing from the madness of the TechnoHippie.Com jungle TechnoHippie <technohippiech...@gmail.com> stumbled into news:alt.www.webmaster and said:
> ... > I don't have a cell phone, > mobile anything, no pda or blackberry. I have nothing to go on except > the assumption that shorter pages are easier to deal with on a 1 and a > half inch square screen :)
Well there's one thing right off - I personally find it easier (on my current phone) to vertical scroll than click between different pages - cache/memory is poor on this particular phone. Horizontal scrolling is a real PITA.
I'd guess there's a considerably wider variety of capability, resources and functionality within handheld devices than there is with desk/lap-tops.
Handheld CSS is not difficult - but gathering sufficient info to do a good job seems quite a task.
> Well there's one thing right off - I personally find it easier (on my > current phone) to vertical scroll than click between different pages - > cache/memory is poor on this particular phone. Horizontal scrolling > is a real PITA.
|
