[DUG] D2006 and compact framework

[Jeremy Coulter]

I have not looked at pocketstudio for a very long time and I tried going to
the url you gave, but I thnk theis project has died now....which is a real
shame as it was a great tool, BUT it was only for PalmOS not for WinCE or
Windows Smartphone devices.

Jeremy

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz] On
Behalf Of Colin/Mina
Sent: 22 November 2006 09:50
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] D2006 and compact framework

Maybe you should also consider "PocketStudio" by Winsoft. It's just like
Delphi.
www.winsoft.se

Colin R Dillicar
Colmin Associates
Ph +64 9 834 4040
colmin at ihug.co.nz

"AVAST" AV Checked


----- Original Message -----
From: "Alan Rose" <Alan at seabed.co.nz>
To: "NZ Borland Developers Group - Delphi List" <delphi at ns3.123.co.nz>
Sent: Wednesday, November 22, 2006 9:30 AM
Subject: RE: [DUG] D2006 and compact framework


> Thank you for this advice. I am very soon to begin work on a PDA project
> with WinCE 5.0
> In your opinion should I even consider using Delphi. I am assuming the
> next version of Delphi (highlander due in the first quarter of next
> year) will support CF 2.0, but probably still no IDE designer support. I
> think that's in the following release (end of 2007). I maybe wrong,
> perhaps Richard can confirm this. I am glad you have posted this so I
> adjust my time and costs for the project.
>
>> -----Original Message-----
>> From: delphi-bounces at ns3.123.co.nz
>> [mailto:delphi-bounces at ns3.123.co.nz] On Behalf Of nodulus maximus
>> Sent: Tuesday, 21 November 2006 7:00 p.m.
>> To: delphi at ns3.123.co.nz
>> Subject: Re: [DUG] D2006 and compact framework
>>
>> For info:-
>>
>> I've just completed a commercial Pocket PC project in .NET
>> (unfortunately not in DELPHI).  Development for PDAs in the
>> compact framework is satisfying in the end, but there can be
>> considerable frustrations along the way!
>>
>> 1. Definitely use version 2 of the Compact Framework - there
>> are many additions and improvements, including the addition
>> of the serial communications class.
>>
>> 2. Make sure you apply SP1 as well - it fixes some subtle but
>> annoying bugs.
>>
>> 3. Most applications will need to do some "PInvoke" calls to
>> unmanaged code to provide the functionality that the CF Team
>> chopped out from the full framework.  Development in Win CE
>> provided access to a lot more needed functionality.
>>
>> 4. Some components like Microsoft's CF Tab control are so
>> crippled as to be near useless for a professional
>> application.  You will likely end up having
>> to either subclass and create your own controls   or buy some
>> third party
>> controls to save time (generally a better option).
>>
>> 5. Beware of the differences between PDA models and
>> manufacturers.  Make sure you develop/test on the target PDA
>> for your Client.  One example is the difference in Bluetooth
>> stacks but there are other subtle differences between devices
>> e.g. the "path" to the CF card, serial port assignments, etc.
>>
>> 6. Unless you have access to an experienced "CF Guru" then
>> allow considerably longer time for developing an application
>> than you would estimate for a .NET desktop application.  The
>> extra time is consumed in tasks like deployment via
>> ActiveSync to the device for testing, resetting the device
>> when it hangs, figuring out work-arounds for control or forms
>> issues, posting to forums to find answers, prototyping to
>> check out architectural ideas, etc.
>>
>> 7. Download one of the free PDA registry editors and use it.
>> There are also some "Pocket Tweak" programs for altering
>> things like scrollbar widths (the latter can be important
>> since screen real-estate is at a premium on a PDA).
>>
>> 8. Download a free "soft reset" program for the PDA.  You'll
>> likely find you have to do this quite often during
>> development, depending on what the application is.
>>
>> 9. There's a registry setting for ActiveSync that you can set
>> to avoid the annoying pop-up window every time you "connect"
>> to a device (i.e. plug it in to the cradle).
>>
>> 10. When looking on the web for articles relating to compact
>> framework development make sure that they are for the correct
>> version of framework (i.e. the one you are developing in).
>> Remember that there's CF1.0, CF1.x, CF2.0 plus service pack
>> variants.  There are differences between versions on things
>> like threading and changing controls on the main thread from
>> a background thread, etc.
>>
>> 11. If you post to one of the Microsoft compact framework or
>> mobile device forums don't expect a quick response!
>>
>> Eric Apperley
>> Eric Apperley & Associates Limited
>> Consulting Engineers - Automation
>> Christchurch
>>
>>
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
> 
_______________________________________________
Delphi mailing list
Delphi at ns3.123.co.nz
http://ns3.123.co.nz/mailman/listinfo/delphi


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.12/544 - Release Date: 21/11/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.12/544 - Release Date: 21/11/2006