I started off this tutorial series on mobile value picker with a discussion about some key differences between desktop browser development and mobile browser development. One of the key differentiators I discussed was connectivity. That was why this series has so far focussed on an approach that predominantly used Client-Side JavaScript and avoided interaction with the server as much as possible. But when I first discussed the approach with David Leedy many weeks ago, his requirement was somewhat different. The users of his mobile application would always be connected; they would not be roaming; so connectivity was not an issue and ...
From some feedback to yesterday's post, that code works fine if all you want to do is create a new document. So, I've gone away and come up with some amendments and improvements. First of all, I've moved the New User button into the Page Heading control's action facet. Again I use the Move to Application Page simple action, setting targetPage to "user" and setting forceFullRefresh to "true". It's important to do this. Otherwise, the user will be editing the previous contact instead of creating a new one. The code for this button will look very familiar:
In Part One I talked in generic terms about the differing approaches when developing for mobile browsers compared to desktop browsers. Screen sizes make dialog boxes for pickers less desirable than in desktop browsers. Connectivity concerns mean typeahead and partial refresh functionality could perform worse on mobile devices and impact the user experience. Smaller resolutions can also make it harder to select from a standard Edit Box with typeahead enabled or ComboBox. In this part I will demonstrate a predominantly client-side approach, picking options from a view. But the same technique could equally be used to select from a static ...
Over the last week I've come across a couple of requests for some sort of typeahead or Name Picker or Value Picker for mobile. There was a question on Stack Overflow and another query came from an alternate discussion. I will outline my preferred option in my next post, but first I want to add some background on what I consider are the differences between browser and mobile browser development methodologies. Pickers and typeahead functionality work well in a browser environment, which is heavily reliant on server-side functionality. Partial refreshes abound in XPages and one of its major strengths as ...
Our Clients
