Whoops! That should have read 'Nokia E51' - I accidentally mixed the
brand name of my previous phone with the model number of my current
phone.

>Should a Motorola E51 be able to use a stock standard wicket site with
a
>bit of AJAX? Apparently its browser has javascript support (and it is
>enabled) but I can never get any parts of our wicket website that
>require AJAX to work on this phone.
>
>Any idea why not?
>
>>-----Original Message-----
>>From: Martin Funk [mailto:[email protected]]
>>Sent: Wednesday, 16 June 2010 7:10 PM
>>To: [email protected]
>>Subject: Re: Wicket and mobile browsers
>>
>>Thank you for the hint, mobileaware wasn't on my radar so far.
>>
>>2010/6/15 Joachim F. Kainz <[email protected]>
>>
>>> Martin,
>>>
>>> WURFL is a great solution, but there are some problems with keeping
>it
>>> up-to-date for commercial applications.
>>>
>>> http://www.mobileaware.com/ is a good commercial vendor I have used
>for
>>> m.wellsfarg.com and other sites. They have an extensive
>>> device-repository and a lot of other useful features for building
>MWeb
>>> sites. Downside: $$$
>>>
>>> Best regards,
>>>
>>> Joachim
>>>
>>> On Tue, 2010-06-15 at 17:36 +0200, Martin Funk wrote:
>>>
>>> > Hi Giovanni,
>>> >
>>> > on what basis do you do the device recognition and classification?
>>> >
>>> > Currently we are looking into wurfl http://wurfl.sourceforge.net/
>>> > Any opion on tha? Or do you know of an alternative to wurfl?
>>> >
>>> > mf
>>> >
>>> > 2010/6/15 Joachim F. Kainz <[email protected]>
>>> >
>>> > > Giovanni,
>>> > >
>>> > > I am one of the developers of mobile.walmart.com. We are using
>Wicket
>>> to
>>> > > support all types of cell phones, but most of our traffic is
from
>>smart
>>> > > phones. If you point to our site using iPhone, Blackberry, and
>>Motorola
>>> > > Razor you get three different experience. All three experiences
>are
>>> > > backed by the same Java code.
>>> > >
>>> > > We have nothing to do with visural wicket (even though at first
>>glance
>>> > > it looks interesting). Our opensource components are at
>>> > > http://code.google.com/p/jolira-tools/
>>> > >
>>> > > Best regards,
>>> > >
>>> > > Joachim
>>> > > http://www.jolira.com
>>> > >
>>> > > On Sun, 2010-04-18 at 13:02 -0500, Jeremy Thomerson wrote:
>>> > >
>>> > > > There are many classes of smart phones available.  Some
support
>n
>>JS,
>>> > > some
>>> > > > very limited, while others support just about anything you can
>put
>>in
>>> a
>>> > > > regular browser.  Because of this, you may use the same java
>code
>>> with
>>> > > three
>>> > > > or four different styles of markup so that each browser class
>has
>>its
>>> own
>>> > > > markup.
>>> > > >
>>> > > > Search the list for "mobile.walmart.com" and see the post made
>by
>>> the
>>> > > guys
>>> > > > that created that site.  It talked about this.  They also
>released
>>> some
>>> > > open
>>> > > > source components - visural wicket.
>>> > > >
>>> > > > --
>>> > > > Jeremy Thomerson
>>> > > > http://www.wickettraining.com
>>> > > >
>>> > > >
>>> > > >
>>> > > > On Sun, Apr 18, 2010 at 3:17 AM, Giovanni
<[email protected]>
>>> wrote:
>>> > > >
>>> > > > > I need to write a web application which will be accessed via
>>mobile
>>> > > > > browsers from smartphones.
>>> > > > >
>>> > > > > What are the smartphone browsers which work well with
Wicket?
>>> > > > >
>>> > > > > What kind of attention should I pay during the development
of
>>> Wicket
>>> > > > > applications for mobile devices?
>>> > > > >
>>> > > > > Is there any tutorial about developing Wicket applications
>for
>>> mobile
>>> > > > > target browsers?
>>> > > > >
>>> > > > > Thanks in advance for any help.
>>> > > > >
>>> > > > > giovanni
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > >
>>> > >
>>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to