srhartone
Mon May 05 04:33:02 CDT 2008
As geometric modeling is not yet a reality on devices we have to make do with
conventional methods. This is a major problem with device app development and
I have *generally* one principle, design your forms to target the smallest
screen size that you'll need to support. So in this case 176x220.
There is a free orientation aware control (oac) that the p&p team created -
but the issue with this is you have to target each screen factor. Because of
this I usally make do with (my own geometric modeling approach) and anchoring
and docking as pointed out by Christopher using CF 2.0 and onwards.
See if this helps: there is a video link on this page which explains the oac.
http://simonrhart.blogspot.com/2007/05/smart-client-software-factory.html
--
Simon Hart
Visual Developer - Device Application Development MVP
http://simonrhart.blogspot.com
"juvi" wrote:
> Hello,
>
> Which ways can you recommend to support the most of the resolutions known
> from WM6.0?
>
> 176x220
> 240x240
> 240x320/320x240
> 240x400/440x240
> 320x320
> 480x480
> 640x480/480x640
> 480x800
>
> Is it recommended to create separate projects for each resolution or to
> support a whole resolution group in one project. If whole groups which are
> recommended to support in one application ? (because it is really hard work
> to expand or edit the windows forms designer code for each resolution!? -
> maybe there is a better way)
>
> Hope that there is a good solution for this resolution-problem...
>
> thx
> juvi