StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POTargeting Mobile and Desktop Browsers - ASP.NET MVC2 with MS Web Application Toolkit and Sencha Touch
primarykey
Id
3274123
data
AcceptedAnswerId
0
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-07-18T02:42:47.957
FavoriteCount
2
LastActivityDate
2010-08-01T22:00:40.733
LastEditDate
2010-07-18T07:46:08.300
LastEditorUserId
142437
OwnerUserId
142437
ParentId
0
PostTypeId
1
Score
0
ViewCount
1850
LastEditorDisplayName
text
Body
I'm building a web app that I'd like to: <ul> <li>Use the native UI capabilities of mobile devices (e.g. iPhone, Windows Mobile, Android phones) when rendered on those devices</li> <li>Render nicely on non-web toolkit browsers (i.e. desktop browsers) such as IE, Firefox, Opera</li> </ul> My research so far has brought me to using the following technologies: <ul> <li>ASP.NET MVC 2 for my dev framework (writing different views for each target device)</li> <li>Sencha Touch (previously called ExtJS) for rendering in each different mobile device's browser</li> <li>The Microsoft Web Application Toolkit for distinguishing between the requesting device / browser type</li> </ul> I have no experience in either of the 3 technologies specifically (I've done plenty of C# server-side, WinForms and ASP.NET 2 development), so I'm really basing this decision on what info I've been able to dig up on the web. Can anyone can think of a reason that this combo of technologies wouldn't work? My main concern is how I can wedge Sencha Touch into this solution alongside the MS Web App Toolkit. In fact, whether both of them are even necessary in this case. Any suggestions or feedback greatly appreciated. Ash
Tags
<asp.net-mvc-2><mobile-website><sencha-touch>
Title
Targeting Mobile and Desktop Browsers - ASP.NET MVC2 with MS Web Application Toolkit and Sencha Touch
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAshby
UserOwnerUserId
1. USAshby
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POTargeting Mobile and Desktop Browsers - ASP.NET MVC2 with MS Web Application Toolkit and Sencha Touch
 UserUserId
 USk25
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POTargeting Mobile and Desktop Browsers - ASP.NET MVC2 with MS Web Application Toolkit and Sencha Touch
 UserUserId
 UScoolcake
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.