mobile geocaching australia - beta testing
-
- Posts: 1329
- Joined: 29 March 03 6:04 pm
- Location: Gladesville, Sydney
- Contact:
tolmh, can you please try opening the page http://mobile.geocaching.com.au/tolmh so we can see what type of request your phone is making. there's no page there, so you'll get an error in any event. thanks
- The Spindoctors
- Posts: 1767
- Joined: 08 October 03 8:00 pm
- Location: Sydney
- Contact:
OK, I've gone to http://mobile.geocaching.com.au/tolmh. I got a 'HTTP status 404' message. The phone is supposed to do GPRS - maybe I don't have it set up properly. I'll have a look around Vodafone's site.
-
- Posts: 1329
- Joined: 29 March 03 6:04 pm
- Location: Gladesville, Sydney
- Contact:
GPRS isn't the problem, that's just a different means of getting to the internet, analagous to using a dial up modem vs a cable modem. I think the lack of a HTML browser on your phone is the problem. WAP, which your phone does have, reads a "language" called WML. It may be possible to create a wap.geocaching.com.au or similar, just need a different content type (not text/html) and write out wml files which look something like:
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "/wap/wml.xml">
<wml>
<card id="first_card" newcontext="true">
<p align="center">
<a href="/wap/mainmenu.wml"><img src="images/logo.wbmp" /></a>
</p>
</card>
</wml>
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "/wap/wml.xml">
<wml>
<card id="first_card" newcontext="true">
<p align="center">
<a href="/wap/mainmenu.wml"><img src="images/logo.wbmp" /></a>
</p>
</card>
</wml>
thanks guys
we've added rough locations derived from postcodes. so now when you list caches within a state or near other caches, it tells you what suburb or area they are in. we think it's useful, but perhaps it takes up too much screen real-estate. comments?
we've also added indications for archived and temporarily unavailable caches. please treat this data with a grain of salt (this is still in beta!) - these flags are not as up-to-date as the rest of the data. it's best to look at the latest logs to work out what's what. we will soon be writing a routine which will interpret the logs to work out more accurately the status of an individual cache.
we've added rough locations derived from postcodes. so now when you list caches within a state or near other caches, it tells you what suburb or area they are in. we think it's useful, but perhaps it takes up too much screen real-estate. comments?
we've also added indications for archived and temporarily unavailable caches. please treat this data with a grain of salt (this is still in beta!) - these flags are not as up-to-date as the rest of the data. it's best to look at the latest logs to work out what's what. we will soon be writing a routine which will interpret the logs to work out more accurately the status of an individual cache.
we've just tagged a few hundred more caches as archived, so you should be able to find a few now
the problem with identifying archived caches is that once they are archived, they disappear from some of the feeds. so we adopted a quick-n-dirty approach based on when we last heard about the cache. if it was too long, we archived it. if we got some wrong, the next time that cache appears in a feed, it will be automatically unarchived.
the problem with identifying archived caches is that once they are archived, they disappear from some of the feeds. so we adopted a quick-n-dirty approach based on when we last heard about the cache. if it was too long, we archived it. if we got some wrong, the next time that cache appears in a feed, it will be automatically unarchived.