Quick survey: Multiple pages on a form

[David]

Hi,

Just a quick survey to see how you handle having too much information on a
form for the pocket device.

My current app has a lot of information. In the past (ASP.NET), I have
written many panels or user controls and switched panels on and off when
required. This is all in one page.

This app, I am doing something very similar. I have made the working area a
lot larger so that I can design the panels. I set visible to false, then on
certain events, I move the panel position and set visible to true. (I have
to move position as I have designed them away from the visible section of
the screen). (I am using CF 1.0)

How do you do your handling?

--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available

 

[chris-s]

Hi,

Just a quick survey to see how you handle having too much information on a
form for the pocket device.

My current app has a lot of information. In the past (ASP.NET), I have
written many panels or user controls and switched panels on and off when
required. This is all in one page.

This app, I am doing something very similar. I have made the working area a
lot larger so that I can design the panels. I set visible to false, then on
certain events, I move the panel position and set visible to true. (I have
to move position as I have designed them away from the visible section of
the screen). (I am using CF 1.0)

How do you do your handling?

Where I've done this I've created a custom panel control that does a
lot of the 'housekeeping' for me, like the re-positioning and 'hiding'
on creation. I also extended the 'show' method to automatically hide
the currently displayed panel and added events like 'before show',
'after show', and methods like 'DisplayPreviousPanel' and so forth.

Chris

 

[Matt Lacey]

Hi,

Just a quick survey to see how you handle having too much information on a
form for the pocket device.

My current app has a lot of information. In the past (ASP.NET), I have
written many panels or user controls and switched panels on and off when
required. This is all in one page.

This app, I am doing something very similar. I have made the working area a
lot larger so that I can design the panels. I set visible to false, then on
certain events, I move the panel position and set visible to true. (I have
to move position as I have designed them away from the visible section of
the screen). (I am using CF 1.0)

How do you do your handling?

Use a tabControl.
That way you don't have to worry about moving things around. User
navigation to various other information is also simplified.
Your solution will also become more complicated when trying to support
screens of differing sizes and screen rotation.

TabControl is designed for this situation (storing more information on
a form than can easily be displayed.)
The other alternative is to use mulitple forms.

 

[Jin Chang]

Hi,

Just a quick survey to see how you handle having too much information on a
form for the pocket device.

My current app has a lot of information. In the past (ASP.NET), I have
written many panels or user controls and switched panels on and off when
required. This is all in one page.

This app, I am doing something very similar. I have made the working area a
lot larger so that I can design the panels. I set visible to false, then on
certain events, I move the panel position and set visible to true. (I have
to move position as I have designed them away from the visible section of
the screen). (I am using CF 1.0)

How do you do your handling?

As one of the responders suggested, using a TabControl may be a good
approach if your application can allow the Tabs. If not, you might
want to look into having a Panel that houses a UserControl. That way,
you can design multiple pages/screens as individual UserControl which
gets loaded into the Panel as per your requirements. The main
advantage of doing this is that it allows for better page layout
during design time as well as separation of codes.

- Jin

 

[Simon Hart [MVP]]

I wouldn't load too many controls into one form as you might find performance
an issue. Try dividing the controls up into separate forms, this is common
behavior throughout the Windows Mobile platform.