Next Live Event: NamePros Live Auction, May 23rd at 6PM EDT
Results from the May 8th live auction are here.
15 members in the live chat room. Join Chat!
You should be able to push xml/rss feeds straight to a mobile, there are 3rd party utils as well for the end user like http://www.mobilerss.net/ and many others which allow you to sync with your mobile the feeds you require. Since Vbulletin has a pda version then it is possible to read these forums directly if you know the url and they publish the pda/archive versions. It should be something like http://www.domain.com/archive/index.php/
Here is a great tutorial if anybody is interested. Plenty of code examples are given in the WML tutorial to help you understand the concepts and techniques.
I found some templates that helped me get some simple pages up quickly.
That's neat. But how do you go about putting the RSS feeds onto a site? I have no idea if someone could share, I have a site that would be good with this.
If it is a forum like vbulletin, then its just a matter of flicking a switch in the admin to turn on the use of pda's able to read the board.
Wordpress and similar blog software can have them going in and going out via a program called 'magpie rss' which you install on the server along with the blog. There are a couple of others which make rss feeds into posts on the main page as well.
If you want a site that has no rss functionality then you can create them manually although they won't change content unless you physically update the feed, which isn't too much work since its all text. Something along these lines http://www.devx.com/xml/Article/10790
Ok thanks very much for your reply, I read some of that page and it's a bit too much for my foggy brain to compute right now. Hopefully later I'll understand it better.
As for the how games can be XHTML served up question, they can be served up easily, and streamed with Java.Java would also be a good alternative to using RSS feeds for a chat room/live board.
GD.
Still have some testing to do with it and probably will change some stuff but I'm glad the mandatory registrant requirements (valid profile and code, no frames and name.ext resolution) are out of the way.
thx for info, guys! just try to use wurfl with my blog.
__________________ SEO Freelancer keywords optimization, redesign, site analysis, reports / consultancy, search engine submission, link building, link baiting, link popularity enhancement, search terms analytics, targeted traffic, competitor analysis, monthly ranking reports, mobile seo, mobile redesign.
You want the size of the page to be small - at least the page that is delivered to mobile devices. This way its a fast download and won't take much bandwidth which costs the phone user more. Actually, keeping the page size small is always a good idea to insure fast browser resolution so people don't just leave your site waiting for it to load.
is wap in any way superior to xhtml ?
can it do things that xhtml can't (is it worth learning)
my html skills are 1.5 on a scale of 10, meaning i can look at page source and understand most of it)
second, do i understand right that any good html software would be acceptable as long as i can change the header and then validate and fix erros for mobi compliance?
I wouldn't create any pages larger the 125-150px wide unless you are using dynamic device detection based on the user_agent and still its not 100% reliable.
And max. data load should be 10k or less. Most mobile plans that say unlimted browsing still limit the max data transfer to 500k a day (50 Pages.)
Good old html will do fine Works on nearly all Internet-capable gsm's.
Take a look at 4x4mobile, and You will understand a few things.
Anyway, .mobi is too long and is considered by me to be a deadborn child.
Unless the SLD is very short.
3-char. (.com, .net, etc.) and 2-char. (.tv, .cc, .tc, .be, etc.) shall stay.
Most domain traders and appraisers seem to not know it, but cell phone users do:
Type-in length/time is SLD + dot + TLD and not just SLD.
That's important for phone users, not the extension.
But we can agree or disagree on this.
as you know the mobi tld has mandated second level domain siting to eliminate the need to type www
with browser defaults which i am more certain are going to be implemented, the user merely types hamburger into the address bar and he goes immediately to hamburger.mobi
