StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11538668
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-07-18T09:50:37.277
FavoriteCount
0
LastActivityDate
2012-07-18T09:50:37.277
LastEditDate
LastEditorUserId
0
OwnerUserId
1301197
ParentId
7318396
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
For your own strings (not talking about native touch component) you could do something like this. 1) In your index.html in the head section, load a LocaleManager.js file (whatever the name) before the <code><script id="microloader" type="text/javascript" src="sdk/microloader/development.js"></script></code> In your localeManager, depending on your browser's language load the resource file corresponding to your language (myStrings-fr.js | myStrings-en.js ) You can do something like this to get the language in the browser: <pre><code>window.navigator.language || window.navigator.userLanguage || window.navigator.browserLanguage || window.navigator.systemLanguage </code></pre> 2) Create your resources files with your translated string It should look like this for the english version (myStrings-en.js) : <pre><code>var myStrings = { MyPackage1: { myString1: 'Seach...' }}; </code></pre> It should look like this for the french version (myStrings-fr.js) for example : <pre><code>var myStrings = { MyPackage1: { myString1: 'Recherchez...' }}; </code></pre> 3) In your sencha touch code, for example for a searchfield place holder value <pre><code>xtype: 'searchfield', id: 'searchToolbarItem', placeHolder: myStrings.MyPackage1.myString1 </code></pre> Hope it will help. Another solution could be to modify the build process of your sencha touch app and create localized versions of your app when building it. So there would be one version per language. Then depending on the brower language you would load the right version of your app when loading the app in the browser.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POsencha touch i18n basics
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRonan Quillevere
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. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.