Share your Editors

[Sarah Mitchell]

Re: Share you Editors

In doing audits, I routinely need to show whether or not something was OK or not. Default is always "Yes" for OK because auditors then only need to click on the items that were Not OK for some reason speeding up data entry.

The way I do it now (which I will improve upon in the tablet app) for the desktop application uses a drop-down and the choices are: Y, N, D, A, X. Y for Yes, N for No, D for No Detail Provided, A for No Applicable and X for Not Examined. If the choices are either N or D the selection is red because that is a defect.

I am trying to think of the best way to do this is a tablet app and I know I won't use a drop-down control. People will be using their finger and making the selection. We are also going to discontinue using the "D" option.

So basically I will ask the user to select with their finger: Yes, No, N/A, N/E


[ATTACH]41230[/ATTACH]
[ATTACH]41231[/ATTACH]

Forgot to add that I was thinking of using a green checkmark for Yes/OK, red X for No, and probably just small text for NA and NE.

Have you looked at the Switch Editor? This could be a good way to capture the information easily with minimal interface elements. They can be created as HTML elements. They support more than two states, as well.

[RussSoftware]

Re: Share you Editors

In doing audits, I routinely need to show whether or not something was OK or not. Default is always "Yes" for OK because auditors then only need to click on the items that were Not OK for some reason speeding up data entry.

The way I do it now (which I will improve upon in the tablet app) for the desktop application uses a drop-down and the choices are: Y, N, D, A, X. Y for Yes, N for No, D for No Detail Provided, A for No Applicable and X for Not Examined. If the choices are either N or D the selection is red because that is a defect.

I am trying to think of the best way to do this is a tablet app and I know I won't use a drop-down control. People will be using their finger and making the selection. We are also going to discontinue using the "D" option.

So basically I will ask the user to select with their finger: Yes, No, N/A, N/E


OK.jpg
OK-dropdown.jpg

Forgot to add that I was thinking of using a green checkmark for Yes/OK, red X for No, and probably just small text for NA and NE.

[RussSoftware]

Re: Share you Editors

In doing audits, I routinely need to show whether or not something was OK or not. Default is always "Yes" for OK because auditors then only need to click on the items that were Not OK for some reason speeding up data entry.

The way I do it now (which I will improve upon in the tablet app) for the desktop application uses a drop-down and the choices are: Y, N, D, A, X. Y for Yes, N for No, D for No Detail Provided, A for No Applicable and X for Not Examined. If the choices are either N or D the selection is red because that is a defect.

I am trying to think of the best way to do this is a tablet app and I know I won't use a drop-down control. People will be using their finger and making the selection. We are also going to discontinue using the "D" option.

So basically I will ask the user to select with their finger: Yes, No, N/A, N/E


OK.jpg

[Sarah Mitchell]

Have you built an Editor or Editor Set using the Tablet Optimized Forms? Have you modified existing Editors to meet your needs? Share them with us!

Post images, code, whatever you feel is the best way to share your Editor.

What's an Editor?

Don't know what an Editor is? Check out these resources and start building one today! We have a number of videos available covering everything from the basics to building fully-customized editors using ViewBoxes (ViewBoxes were used to create the keypads and checklist item Editors in the Sample Tablet App.)

• Introduction to the FormView Control: Learn the basics of the FormView control, Editors and Editor sets.
• Editors: Using a Dropdown Box: Discover how a dropdown box can be used in an Editor
• Editors: Cascading Dropdown Boxes: A continuation of a previous thread, Editors: Using a Dropdown Box, which covers how to implement cascading dropdown boxes within the context of tablet form Editors and Editor Sets.
• Editors: Cascading List Control: Learn how to create a cascading List control Editor.
• Editors: Populating a List from a SQL Query: Lists can be populated from a variety of sources. Discover how the onDialogInitialize event can be used to cache data to populate a List control Editor.
• Editors: Pre-Defined List Control Editor: Dropping in a list control for editing data is made easier with the Editor-List. Learn how to leverage this control in your mobile apps.
• Introduction to Group Editors: Learn how to edit a group of controls together using a Group Editor.
• Tablet Sample App: Custom Keypads: Discover how the custom keypads in the sample tablet application were created.
• Tablet Sample App: Checklist Items: Learn how the checklist item in the sample tablet app works and how you could use it in your own applications.
• ViewBoxes: Build a Star Rating: Learn how to build a star rating control from scratch using ViewBoxes.

Too Busy to Build?

If you're too busy to put together an Editor but have one you'd like to see, Let us know! Send your feedback to tabletbeta[at]alphasoftware.com or post your suggestions here in the Tablet Beta Forum.