X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/c6900c006b669c92ba6b0c5df9fd12b7da437a6f..61c213fe224da24ce33c9187263e75a17ca83a04:/docs/html/faqgen.htm diff --git a/docs/html/faqgen.htm b/docs/html/faqgen.htm index 25fc5d82b4..90f2c41d1a 100644 --- a/docs/html/faqgen.htm +++ b/docs/html/faqgen.htm @@ -1,4 +1,3 @@ - @@ -54,7 +53,7 @@ so your program will take on the native 'look and feel' that users are f Although GUI applications are mostly built programmatically, there are several dialog editors to help build attractive dialogs and panels. Robert Roebling's wxDesigner -and Anthemion Software's DialogBlocks +and Anthemion Software's DialogBlocks are two commercial examples, but there are others: see the Useful Tools page.

You don't have to use C++ to use wxWidgets: there is a Python interface for wxWidgets 2, @@ -277,29 +276,29 @@ from Java, and the level of interest in wxWidgets is as high as ever.

Microsoft is spending a lot on promoting the .NET initiative, which is a set of languages, APIs and web service components for Windows. Ximian has started an open source version of .NET, mostly for Linux. -C# is Microsoft's alternative to Java, supporting 'managed code', +C# is Microsoft's alternative to Java, supporting 'managed code', garbage collection and various other Java-like language features.

Although this may be attractive to some developers, there is a variety of reasons why the .NET/Mono combination is unlikely to make wxWidgets redundant. Please note that the following comments -are Julian Smart's opinions.

+are Julian Smart's opinions.

  1. Not everyone wants or needs net services.
  2. C++ will be used for a long time to come; compared with C++, C# is a recent development and its future is not certain.
  3. Mono Forms may only target Winelib (at least to begin with), so the end result is not as native as -wxWidgets (I'm aware there is GTK# for use with the C# language). +wxWidgets (I'm aware there is GTK# for use with the C# language).
  4. C# is usually byte-compiled and therefore slower. Plus, .NET adds a layer of overhead to the client computer that wxWidgets does not require. -
  5. Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now. +
  6. Mono hasn't proven its long-term viability yet (it's a complex system of components); wxWidgets is ready now.
  7. You may not wish to buy into Microsoft marketing spin and APIs.
  8. Microsoft may at some point sue developers of non-Microsoft .NET implementations. After all, -platform-independence is not in Microsoft's interest. +platform-independence is not in Microsoft's interest.
  9. .NET might never be implemented on some platforms, especially Mac and embedded variants of Linux.
  10. wxPython and other language variants provide further reasons for wxWidgets to continue. -
  11. The same issue exists for Qt: if Qt sales remain strong, it's a good indication that -the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!) +
  12. The same issue exists for Qt: if Qt sales remain strong, it's a good indication that +the market for a C++-based approach is still there. (Either that, or everyone's turning to wxWidgets!)
There is nothing to stop folk from developing a C# version of the wxWidgets API; @@ -322,7 +321,7 @@ has specific suggestions. Also please read the coding sta

Each port consists of a platform-specific part (e.g. src/msw, include/wx/msw), -a generic set of widgets and dialogs for when the port doesn't support +a generic set of widgets and dialogs for when the port doesn't support them natively (src/generic, include/wx/generic) and the common code that all ports use (src/common, include/wx). By browsing the source you should get a good idea of the general pattern.

@@ -335,7 +334,7 @@ Perhaps it will still save you time to clean up wxStubs, and others may benefit from this too.

You will need to define a symbol for the new port, e.g. __WXXBOX__. -Look at files such as wx/defs.h, wx/wxchar.h for areas where you'll +Look at files such as wx/defs.h, wx/wxchar.h for areas where you'll need to add to existing conditionals to set up wide character support and other issues. If the GUI runs on a Unix variant, define the __UNIX__ variable in your makefile.

@@ -357,7 +356,7 @@ wxMGL, and wxMSW/Univ for sample wxUniversal ports.

To begin with, you can use whatever makefiles or project files work for you. Look at existing makefiles to see what -generic/common/Unix files need to be included. Later, you'll want to integrate support +generic/common/Unix files need to be included. Later, you'll want to integrate support for your port into configure (Unix-like systems and gcc under Windows), and bakefile (for other makefiles on Windows).