.Net CF Design Approach

[Rohit Kaushal]

I am developing a Pocket PC application using .Net compact
framework with C#.There are 4-5 sub-applications ,each
having 7-8 different screens.

Now i have some doubts regarding optimized design
approach :

1. Is it suggestive to have one form for whole application
and then adding the controls on run-time for various
screens? ( i.e. I have one Form class and from that class,
I derive various classes to populate my different
screens)
2.How to design the screen navigation in the application?(
Will Form Stack be a good option?)

Please do respond.
Thanx,
Kaushal

 

[Bardak]

I have seen many developers use tab based view that toggles between
different modes.
--------------------

 

[Hollywood]

What about one Form that represents each application, and then using a Panel
for each screen and of course implementing a Form Stack?

 

[Venue]

What will you gain from using panel if using form stack anyway?

 

[Hollywood]

Form Stack is for use with the individual forms that represent the
sub-applications. Using a form stack you only need to load the form once
and can easily switch between visible forms. Same goes for using panels
within the form. I've done this in an app and its worked pretty slick. I
found that using the tab control just took up vital UI space I wasn't
willing to trade, so by implementing a panelable form and putting a menu
item in the main menu I was able to conserve as much UI space as possible
but yet still allow the user to easily navigate.

 

[Venue]

Since both panels or form can be made visible when needed. Is there any
benefit in using panels over forms in stack. Is loading 1 form with 10
panels is overall a better idea than say loading 10 individual forms?

 

[Hollywood]

Not particularly, its a matter of perference.

If I was doing something of the sort the original poster was talking about
I'd logically group the by sub-program using the Form as a base. This any
common code to be grouped together and so forth. Actually I'd probably use
a sub-program object that knows how to show or hide the relavent UI for that
sub-program.

Its also a matter of what you feel gives the best user experience and what
your users give you feedback on. If you load up 10 forms, one at a time as
needed there will be a slightly delay each time you initially go to that
form. You could also just preload all the forms at start-up of the
application and take a hit there. Alternately, you could do load up a Form
with its 10 panels when the user calls up that sub-program. Slightly longer
delay, but now you have the entire sub-program UI loaded and the users
notices no further delay in switching between UI areas with exception of
data changes or other code. You could also just load up the sub-program
form with the first panel only and then the other panels only when accessed,
this should be very similiar to the loading of 1 form out of the 10 total
forms. So there are multiple ways of approaching it.