Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Mobile / June 2006

Tip: Looking for answers? Try searching our database.

migrating aspx forms app to mobile forms

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jeremy Chapman - 15 Jun 2006 06:26 GMT
I've got a small application using asxp forms controls like gridview, label
etc.  It is formated to display on a 320x240 display so it looks fine on a
pocket pc.  I recently discovered issues with long hidden fields used by the
viewstate and the eventvalidation.  Currently I changed the viewstate to
store in the session, and turned of the eventvalidation to avoid the long
hidden fields. Will my solution cause other issues?  I'm also concidering
moving to mobile forms, but I don't see any gridview equilavents.  It
doesn't seem you can even do some of the rudamentary html tags like
div,span, etc.  Is it possibly to do this stuff with mobile forms or should
I stick with the standard aspx forms and just put viewstate in the session?
Christoph Richter [AT] - 18 Jun 2006 18:14 GMT
Hi,

we also evaluated using mobile forms, but they have some missing
features that we want to use. (the badest thing is, that the with is
fixed by one control)

now, we have all complete .net2.0 support with masterpages, themes and
all controls from asp. and our engine draw this also in wml, xhtml,
multipart and pml. but it was a really long way.

if you only need xhtml, its much easier.
the first thing, you should think about is how much handsets you need
to support.

the most problems are only on 1-10 handsets. but in most times really
popular one. (razr, nokia 6310,...)

there are:
problems with the "$" Seperator (some handsets dow't allow them in
postback names, and stop there) , e.g. 6310
http://www.code4ward.net/cs2/blogs/cmn/archive/2006/05/17/TheOdysseeOfChangingTh
eIdSeperatorInAspNet2.aspx


problems with ssl  and bigger pages. they stop loading, presenting the
user timeouts, e.g. samsung z500 (all samsung umts phones currently)

what you should do, is changing the xhtml doctype to its mobile type
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN"
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd">
since the most mobiles have some simple transform so they can view all
pages. but your pages are done for mobiles, so say that to them.

also its better to use the more complex xhtml tags like the lists (li,
lu,...) instead of the tables and control them per style. thats most
times easier for the handsets and it looks better.

its not easy, to satisfy all handsets, but its makeable.
if you have furter questions, just ask.

cheers,
christoph

>I've got a small application using asxp forms controls like gridview, label
>etc.  It is formated to display on a 320x240 display so it looks fine on a
[quoted text clipped - 6 lines]
>div,span, etc.  Is it possibly to do this stuff with mobile forms or should
>I stick with the standard aspx forms and just put viewstate in the session?

Cheers,
Christoph

Vienna/Austria

www.code4ward.net/blogs/cmn

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.