I think wince disscussion are very important for lazarus,as it can become
the only development tool in this field which is a real rad tool.
Currently the only alternative is evc3 for 2002 oses,evc4 and visual
studio 4 for higher versions.Or bds 2005/bds 2006 for .netcf
If not choosing .net(.net compact),in win32 or native code,you have lots
of difficulties to program any good ui.
On Fri, 28 Apr 2006 03:04:12 +0330, Felipe Monteiro de Carvalho
<[EMAIL PROTECTED]> wrote:
Problem 1 - We want the same application to run on everything. Like
Skype and Opera run on desktops, run on PDAs and run on telephones. And
in this case we will want to reuse the non-visual code.
My solution: Have a way to create various versions for the same form. We
could have the Desktop version, the PDA version and the Phone version.
And then I can choose which one to link to my executable.
Another option is to create a new project for each new GUI set. If
project groups are implemented then this becomes a good solution.
Problem 2 - The Screen size varies greatly with manufacturer.
Solution: Ummm .... don�t know .... maybe create various versions of the
form again???
Another possible solution is to have positions on the form as
percentages % instead of hard numbers.
Both solutions are good.
With visual studio,for supporting different resolutions,diffrent resources
are used within the program,and being choosed depending on what os or
resolution it has.
I think we can have some kind of mirror forms,which is designed for
different resolution or user interfaces(maybe even created by lazarus)and
simply assign events to the original form.Although it can also be achieved
by user code for now.
Percentage wont work,becouse in 240x320 you can barely fit anything,so how
you going to fit that to 176x220 of smartphones!
I think smartphones have to always have different desings,but somehow we
can do something to not require programmer to write event codes twice.
Problem 3 - Some things only exist on Phones, like a 2 options menu to
be clicked and various communication things.
Solution: Create a Telephone Tab with components that only exist on
telephones.
Yes we really need that.
Problem 4 - Various things don�t exist on a device without touchscreen
or have no use on them. Phones and some PDAs don�t have pointing devices
and this makes many widgets created with a mouse in mind completely
useless. Some examples are: Huge main Menus, Notebooks, spin edit, etc.
Solution: Just don�t support those widgets for phones.
Problem 5 - The whole interface on a device without touchscreen must be
navigatable with only the limited keys on a phone. And worse. The
available keys varie a lot with the manufacturer!
If you use those uis stated in windows user interface desing it wont be a
problem.
For more infos:
Developing Orientation and dpi Aware Applications:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/developing_orientation_and_resolution_aware_apps.asp
Developing Screen Orientation-Aware Applications:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/screen_orientation_awareness.asp
Introduction to User Interface Controls in a Windows Mobile-based
Smartphone:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/installation_with_dpi-specific_resources.asp
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
