Re: [lazarus] Lazarus and DOT Net

[George Birbilis]

>small size of the screen limit quantity of controls you can put on the screen >and lack of rad for wince is not really a problem yet.   even without using .NET Compact Framework, MS recently provided integration of the C and _vbscript_ WinCE tools it had as separate products (don't remember how they called them) to Visual Studio.net. Haven't tried it yet though, most of my experience with programming WinCE is with VB (arround year 2000) where the compiler was converting to _vbscript_ to run at WinCE2.x and lost error handling support etc. Working (got GPS data using COM ActiveX control for WinCE and transferred via cellphone card and TCP/IP [using Socket ActiveX control or something for WinCE] to a host PC that translated the GPS strings and plotted route on a map), but not something for really complex projects (I guess it would have be a nightmare to debug back then). "Native" WinCE tools have evolved, but prefer .NET Compact Framework instead of using WinCE system calls and ActiveX controls on WinCE >recents thrunks are excellent quality, it's simple, can't found a bug :) >fpc arm-wince compiler, is REAL KILLER FEATURE :-)   are there FPC class libraries specially for WinCE features or do you use WinCE ActiveX controls? E.g. with that old VB tools for WinCE you'd drop an ActiveX control on a form for say SerialPort and at compile time the compiler would detect it and see if there's a matching ActiveX control for WinCE, changing the GUID in the form design resource so that on WinCE you'd use the SerialPort ActiveX control for WinCE (that had the same properties/methods/events [maybe also they supported mapping between properties etc. for known controls if not the same API existed on WinCE for a control]) >I guess the only way to make fpc compiling CIL is to wait >that MS release a native .NET CPU and then no more JIT ? You mean the only incentive? Cause it's independent thing. btw, .NET JIT isn't like Java VM JITs, you can run the convertion beforehand, either at app loading (and cache by the system), or preconvert by the installer once, or even include the various IL->native version in the .EXE (portable executable format allows one to have IL, x386, PPC or whatever code in the same .exe I think, similar to Apple's Universal Binaries [in fact before Apple came out with Intel CPU usage and Universal Binaries I had suggested them at Apple QuickTime mailing lists])   ======================== George Birbilis ([EMAIL PROTECTED]) Microsoft MVP J# 2004-2006 Borland "Spirit of Delphi" http://www.kagi.com/birbilis