Differences between version 5 and revision by previous author of CrossPlatform.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Friday, June 17, 2005 11:42:35 pm | by AristotlePagaltzis | Revert |
| Older page: | version 4 | Last edited on Friday, January 9, 2004 3:55:36 am | by StuartYeates | Revert |
@@ -1,7 +1,9 @@
-Able to run
on more than one platform. Differnet people have different idea's about what CrossPlatform means. Most Unix people consider CrossPlatform to mean that it will run on other Unix platforms and probably implements/uses [POSIX] interfaces. MicrosoftCorporation often say "CrossPlatform" when they mean it runs on Windows 95, Windows 2000, and maybe Windows CE
.
+Code that runs
on more than one platform.
-Almost no [
CrossPlatform] applications are not truely
[CrossPlatform
], most perform better, integrate better or are easier to use
on a particular platform, mainly because each platform makes a different set of assumptions,
and making the union of assumptions in an application requires N^2 implementation effort and making the intersection leaves you with a painfully low level of functionality
.
+Differnet people have different ideas about what
CrossPlatform means. Most
[Unix
] people mean the code will run
on other [Unix] platforms
and probably implements/uses [POSIX] interfaces when they say "CrossPlatform"
.
-[wxWindows] is a [GUI] toolkit that allows your source code to be very portable - often you only need to re-compile the source code against
a different port
of the toolkit to get native look-and-feel on GTK
, Motif, [MacOS] 9, [MacOSX], and [WIN32|MicrosoftWindows] (and
some other graphical
platforms)
. I think you can even compile and link against the windows port of GTK!
+Few applications are truly CrossPlatform. Because each platform makes
a different set
of assumptions, making
the union of assumptions in an application requires N^2 implementation effort. Making the intersection leaves you with a painfully low level of functionality. Thus
, most applications perform or integrate particularly well or badly on
some set of nominally supported
platforms.
-Many
[Java
] programs
are relatively
[CrossPlatform], including
the [Eclipse] [IDE].
+Writing CrossPlatform
[GUI]s is particularly difficult. Most ToolKit~s originating on [Unix] have been ported to many other systems: [Tk] and [GTK
] are examples.
[Qt] was designed from the very beginning to be
CrossPlatform itself, and has ports for MicrosoftWindows and [X11
]. [wxWidgets] is an attempt to provide a consistent [API] with binary-compatible binding libraries that allow code to run equally well will any ToolKit that happens to be available.
+
+[Java] programs
, even complex [GUI] ones like the
the [Eclipse] [IDE], tend to be CrossPlatform without much effort. The same is true of programs written in dynamic languages like [Perl], [Python], [Ruby] and the like
.
