[Lazarus] cross platform [Re: Lazarus Goal]
Bee Jay
bee.ography at gmail.com
Fri Nov 13 04:18:34 CET 2009
> Well the understanding of cross platform is quite varying. The base
> obviously is that "one source code" can be executed on all of the
> supported platforms.
In my understanding, there are 3 kinds of cross platform implementation:
1. Cross platform is implemented within an virtual environment both
the binary and the widgets. The application is run on top of it. The
example is Java.
2. Cross platform is implemented in full native ways both in the
binary and the widgets. The application is truly native application on
each platform. The example is FPC/Lazarus.
3. Cross platform is implemented natively on the binary but not on the
widgets. The application execute natively without any virtual
environment but it losses its native look-and-feel (or at best,
emulated). The example is fpGUI, mseGUI, Qt, etc.
Since FPC/Lazarus in on the second type of implementation, we (both
the developers and users) should be aware (and understood) of
consequences of the approach. Expecting FPC/Lazarus to act like the
first type of implementation is ridiculous. This is what the thread
starter didn't understand on the first place, and blaming it on
approach taken by FPC/Lazarus.
> 1) is what the LCL aims for. It is more enduser friendly, but
> requires more work by the developper
Yes. Ideally, again I said ideally which mean it hardly can be
achieved, we (developers) should fullfil anything our users want.
Whether it's difficult or not, it should be our problems, not theirs,
because the users who pay the bill. Sometimes we and our users make
some compromises for whatever reasons. :)
--
-Bee-
...making buzzes at http://twitter.com/beezing
...writing stories at http://beeography.wordpress.com
More information about the Lazarus
mailing list