See the original post:
Google Gains, Apple Stays Steady, And Palm Loses In Smartphone Share
Check out the hot deal on the ASUS Eee PC with Windows at $285.Here are the last two tips for this series to help you build quick and clean survey questionnaires in mobile survey software.
Include few or no hard coded strings in scripting
In general, scripting should be as compact and clean as possible, and you should avoid putting literal strings in the script. This is for two reasons:
Literal strings make it extremely cumbersome to run a multilingual survey questionnaires as translations need to be hard-coded as well. Note that scripting is never included in translation files, so any survey translations sent to translators from Entryware will not include these strings
Scripts need to be parsed on each client every time they are run. That means if you include an especially long string in your scripting, the mobile devices will need to parse over it character-by-character. With sufficient strings in scripting, this can result in a noticeable slowdown in performance.
It is often safer and more elegant to use dummy categorical type of questions for these literal strings and text piping to accommodate scripted strings.
Simplify conditions used in multiple questions by using flag variables
Sometimes you have a few “classes” of respondent which are asked very specific questions. Rather than create multiple copies of projects or questions, common sense tells you to use scripting in the prequestion of relevant questions to skip past if the respondent doesn’t need to answer the question. This is exactly the correct way to program the survey, but there are shortcuts you can use to reduce large numbers of conditional statements in multiple questions by using flag variables to simplify conditions.
A flag variable, in its simplest form, is a variable you define to have one value until some condition is true, in which case you change the variable's value. It is a variable you can use to control the flow of a function or statement, allowing you to check for certain conditions while your function progresses. The idea is to use the flag variable mainly as a memory of other conditions which the function checks earlier in its execution.
It is easy to see how the amount of scripted logic can snowball when you have multiple preconditions or you need to combine the original logic with additional constraints. By creating a temporary “flag” variable, small bits of logic can be stored and frequently reused. The best place for this is in the postquestion of the last question that affects the logic. The scripting for each of the relevant questions is, obviously, much simpler.
Take care in using flag variables. They can quickly become overly complex if you create too many or don’t use clear names.

In the world of mobile surveys there is a high demand for a rugged device that can withstand the many changing conditions and environments surveys are conducted in. Finding that perfect device at the right price point is no easy task. Add in the fact that it must have a full keyboard be lightweight and provide a touch screen narrows your choices down even more.
Well just so happened that a client was on the hunt for such a device. At first I was not very optimistic this devices existed, but after some Googling and talking with my colleagues I found just the device. The CTL 2GO Convertible Classmate PC!
It’s a touchscreen Netbook with Intel’s latest Atom processor and comes with two modes, tablet mode and traditional laptop mode. Built with carrying handle that is lightweight and a durable construction with a rugged outer case. Certified drop test of 50cm and a Water-resistant keyboard allowing for maximum protection. All of this for under $600 U.S. with a 6 cell battery and Windows XP.
If you are looking for a low cost tablet pc that can take a beating for your survey needs look no further!
Here are two more tips to help you build quick and clean survey questionnaires in mobile survey software.
Use sections to group related questions
Sections are most commonly used to start and end question groups where you want to use rostering or looping, randomization, or rotation (Enterprise-only). Since sections are never displayed to the user, you can use them sparingly to help you organize groups of questions in your project.
Avoid using “goto this” on prequestion
The command “goto this” is used to reference the current question. Using “goto this” is easier and more reusable than referring to an explicit question name. It forces the current question to be reloaded. This is useful when you are doing additional validation in postquestion scripting.
You can also use this command in a prequestion script, BUT you must be extremely careful! If you allow for a scenario where the prequestion goto this always fires, you will send Entryware Mobile into an infinite loop and lock up the device!
More tips next time!
Creating a survey questionnaire in Entryware is easy. However, it can be incredibly frustrating. The difference is in how you design your survey questionnaire. Here are two tips to help you build quick and clean survey questionnaires in mobile survey software. This will give Entryware programmers a feel of how to use Entryware to quickly build clean survey questionnaires.
Use meaningful, unambiguous question and response names and aliases
If you are working off a prepared script (for example, a provided Word document), it only makes sense to use the same question names as the source document. This aids in communicating changes or problem areas in the survey (be it in the source document or the Entryware project).
Avoid using especially long or unhelpful question and alias names. Q1, Q2, Q3 are short and to the point, but if you arbitrarily chose these names you will have trouble finding your gender question if you forgot it was called Q94. Likewise, overly wordy names are problematic because they take up a great deal of screen space in both the question list and the script editor.
if ((Q51_Age.Person1 < 21 ) | ( Q51_Age.Person1 > 40 ) ) & ( Q50_Gender = Male ) )
message “The first person cannot be a male between the ages of 21 and 40”
endif
This example provides a blend of readability and conciseness. The scripting can be read and understood by any reader even if the reader didn’t write the script to begin with. It isn’t so wordy that it scrolls far off the screen.
Use project-level question properties when appropriate
There are many question properties that you want to set for the entire survey questionnaire (e.g. auto advance, minimum responses, turning on or off the tool bar). It is possible to select all of the questions in the survey questionnaire and set them using the Question Properties frame, however this becomes clumsy to set (and change) in very large surveys and opens the very real risk that questions added at the last minute will not have the properties the rest of the survey questionnaire does.
Project level settings can be done in OnStart or on the prequestion of first the question. Always remember, project level settings override the question properties widow and question level settings script override project level settings.
More tips next time!
Unlocked Palm Centros are on sale for over 50% off at TigerDirect.ca. 