Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

*** empty log message ***

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@30072 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Kevin Hock
2004-10-22 19:15:35 +00:00
parent 119af81b23
commit dbd94b7501
42 changed files with 260 additions and 257 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/tech/index.txt
View File

@@ -1,4 +1,4 @@
All wxWidgets techincal notes at a glance
All wxWidgets technical notes at a glance
=========================================
tn0001.txt How to add a new sample
@@ -18,7 +18,7 @@ tn0014.txt XRC resources format specification
tn0015.txt How to add new bitmaps to wxWidgets UI elements
tn0016.txt How to add new files and libraries to wxWidgets build system (Bakefile)
tn0017.txt How to write unit tests for wxWidgets classes
tn0018.txt How to add a new font encoding/charset to wxWidgets?
tn0018.txt How to add a new font encoding/charset to wxWidgets
Version: $Id$

5
docs/tech/tn0002.txt
View File

@@ -12,7 +12,7 @@ First of all, here is what you will need:
mirror (RPMs and DEBs are also available from the usual places)
b) for Windows you can download the precompiled binaries from
www.wxwidgets.org or install PoEdit (poedit.sourceforge.org) and
www.wxwidgets.org or install PoEdit (poedit.sourceforge.net) and
add <installdir>/poEdit/bin to your path (so it can find xgettext).
2. A way to run a program recursively on an entire directory from the command
@@ -65,6 +65,9 @@ Author: VZ
Version: $Id$
$Log$
Revision 1.5 2004/10/22 19:12:59 KH
*** empty log message ***
Revision 1.4 2004/05/04 08:26:58 JS
Name change replacements

18
docs/tech/tn0014.txt
View File

@@ -89,8 +89,8 @@ and "subclass". "class" must always be present, it tells XRC what wxWidgets
object should be created in this place. The other two are optional. "name" is
ID used to identify the object. It is the value passed to the XRCID() macro and
is also used to construct wxWindow's id and name attributes and must be unique
among all children of the neareset container object (wxDialog, wxFrame,
wxPanel, wxNotebook) upside from the object in XML nodes hiearchy (two distinct
among all children of the nearest container object (wxDialog, wxFrame,
wxPanel, wxNotebook) upside from the object in XML nodes hierarchy (two distinct
containers may contain objects with same "name", though). "subclass" is
optional name of class whose constructor will be called instead of the
constructor for "class". Subclass must be available in the program that loads
@@ -109,10 +109,10 @@ is allowed to register new object handlers within XRC and extend it to accept
new <object> classes (and therefore different <object>'s child nodes).
<object_ref> node is identical to <object>, except that it does _not_ have
"class" property and has additonal required property "ref". It's concept is
"class" property and has additional required property "ref". It's concept is
similar to Unix symlinks: value of the "ref" property is equal to the value of
"name" property of some existing node (called referred node) in the resources
(not neccessary top-level). Referred node's "class" property and all subnodes
(not necessary top-level). Referred node's "class" property and all subnodes
are copied in place of the referee <object_ref> node which is then processed as
regular <object> node. If the <object_ref> node itself has child nodes, then
these nodes _override_ any nodes from the referred node.
@@ -154,7 +154,7 @@ by XRC parser according to this table:
"__" -> "_"
"\n" -> line break (C character '\n')
"\r" -> carriage return (C character '\r')
"\t" -> tabelator (C character '\t')
"\t" -> tab (C character '\t')
"\\" -> "\"
(introduced in version 2.5.3.0, not done in earlier versions)
@@ -196,7 +196,7 @@ Style[wxSomeClass]
------------------
List of style flags that can be passed to wxSomeClass' constructor. Flags are
written in same way as in C++ code (e.g. "wxSUNKEN_BORDER",
"wxHW_SCROLLBAR_NEVER") and are delimined with any combination of whitespaces
"wxHW_SCROLLBAR_NEVER") and are delimited with any combination of whitespaces
and '|'. Possible flags are class-dependent and are not described in this
technote. Please refer to wxWidgets manual for all styles that given class can
accept; if XRC does not accept a flag listed in wxWidgets documentation, it is
@@ -209,7 +209,7 @@ Attribute value is interpreted as filename (either absolute or relative to
the location of XRC resource file). In addition, attribute node may have
"stock_id" and "stock_client" properties. Their values may be any of wxArtID (or
wxArtClient respectively) values as used by wxArtProvider (because the user may
define own constants, efectively any string is legal here). Examples are
define own constants, effectively any string is legal here). Examples are
"wxART_FILE_OPEN" (id) or "wxART_MENU" (client).
Any of "stock_id" or "stock_client" properties or the filename may be omitted.
@@ -321,8 +321,8 @@ orientation "horizontal"|"vertical" horizontal
wxSplitterWindow must have at least one and at most two children objects.
If there's only one child object, it is passed to wxSplitterWindow::Initialize
and the splitter is created unsplitted. If there are two children, the
splitter is created splitted, either horizontally or vertically depending
and the splitter is created unsplit. If there are two children, the
splitter is created split, either horizontally or vertically depending
on the value of "orientation" attribute.
wxStatusBar

2
docs/tech/tn0015.txt
View File

@@ -80,7 +80,7 @@ It is highly desirable to let the users know what stock bitmaps are available
in wxWidgets. The "artprov" sample serves this purpose: it contains a browser
dialog that displays all available art resources.
It has to be updated to accomodate for new bitmaps. Fortunately, this is
It has to be updated to accommodate for new bitmaps. Fortunately, this is
trivial: open $(wx)/samples/artprov/artbrows.cpp in text editor and
ART_ICON(wxART_MY_BITMAP) line to the FillBitmaps() function.

6
docs/tech/tn0016.txt
View File

@@ -83,11 +83,11 @@ All files used by main libraries are listed in files.bkl. The file is
organized into variables for toolkits, platforms and libraries. The variables
come in pairs: there's always FOO_SRC for source files and FOO_HDR for header
files. Platform or toolkit specific files are grouped together in variable
with platform or tookit name in them, e.g. BASE_WIN32_SRC, BASE_UNIX_SRC,
with platform or toolkit name in them, e.g. BASE_WIN32_SRC, BASE_UNIX_SRC,
GTK_SRC, MOTIF_SRC.
Note: A side effect of this toolkit-centric organization is that one file may
be present several times in files.bkl in different contenxt.
be present several times in files.bkl in different contexts.
When you are adding a file, you must put it into appropriate variable. This is
easy if you are adding the file to library that is always built from same
@@ -194,7 +194,7 @@ f) Update configure.in and wx-config.in to contain information about
the library and needed linker flags:
* Add "foo" to either CORE_BASE_LIBS or CORE_GUI_LIBS in configure.in so
that wxFoo is not treated as contrib library in monolithic build.
* If wxFoo links against additional libraries, add neccessary linker
* If wxFoo links against additional libraries, add necessary linker
flags and libraries to ldflags_foo and ldlibs_foo variables in
wx-config.in (both are optional).