Jump to content
jgcode

PDA Design Patterns

Recommended Posts

Hi

Does anyone have any suggestions/recommendations for design patterns when using PDA type devices and LabVIEW?

Obviously screen real estate is tight, so to view data for our app I will need multiple screens (and therefore an Engine/API to manage them).

Compared to things I do in standard LabVIEW the PDA environment seems really limited - i.e. no VI Server for interacting with the screen etc...

Can any post their experiences/ideas?

And anything that would improve the usability of such a UI (i.e. from a user's perspective).

Cheers

-JG

Share this post


Link to post
Share on other sites

My experience with the mobile module (the PDA module, actually) is both limited and old, but I can say that in the past it was quite buggy. You should plan some extra time for debugging.

As for the UI design, you can either go with multiple windows scheme (where only one window appears at every one time) or try to combine everything into a single window. I'm assuming you can't use subpanels, and tabs really don't work. What I did in the past was use a tab control, hide the tabs and used a ring to control which page of the tab was visible.

You may wish to have a look at NI's UI community. Simon H. (if I remember correctly) posted a cool UI demo where the screen (a tab) slides in and out based on your selection. I assume the design is based on an app from one of the smart phones so popular these days (and I assume you can have a look at some of those to get some design ideas).

  • Like 1

Share this post


Link to post
Share on other sites

My experience with the mobile module (the PDA module, actually) is both limited and old, but I can say that in the past it was quite buggy. You should plan some extra time for debugging.

As for the UI design, you can either go with multiple windows scheme (where only one window appears at every one time) or try to combine everything into a single window. I'm assuming you can't use subpanels, and tabs really don't work. What I did in the past was use a tab control, hide the tabs and used a ring to control which page of the tab was visible.

You may wish to have a look at NI's UI community. Simon H. (if I remember correctly) posted a cool UI demo where the screen (a tab) slides in and out based on your selection. I assume the design is based on an app from one of the smart phones so popular these days (and I assume you can have a look at some of those to get some design ideas).

Thanks Yair, this is the only example I have "seen" with tabs - I will try to find Simon H's post.

Yes, there a no subpanels either.

The whole experience does not look like fun :) (compared to using standard LabVIEW)

Share this post


Link to post
Share on other sites

See here - http://decibel.ni.com/content/groups/ui/blog/2010/04/29/creating-quality-uis-with-ni-labview--developer-days-2010-presentation

The touch panel example is the relevant one.

My understanding has always been that the module converts the code to C (like the embedded module) and then uses eVC to compile it. I expect that this is the source of most of the bugs, since it's a process which is considerably different than the desktop app-builder.

Anyway, you should be happy you have tabs. If memory serves, the first version of the PDA module didn't have them.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.