initalize memeber vars

[lyx.git] / src / frontends / kde / dlg / README

diff --git a/src/frontends/kde/dlg/README b/src/frontends/kde/dlg/README
index 43145094bcfb936846615d69ea576c84a54afeab..74ffca9de0ab7f66d1485d4b5a397d71e568397d 100644 (file)
--- a/src/frontends/kde/dlg/README
+++ b/src/frontends/kde/dlg/README
@@ -1,12 +1,15 @@
-These files are generated with qtarch-1.4-6 which can be downloaded
+These files are generated with qtarch-1.4-5 which can be downloaded
 from 
 
 http://qtarch.sourceforge.net/
 
-Currently you also need this patch : 
+Currently you also need this patch :
 http://www.movement.uklinux.net/patches/lyx/qtarch-1.4.6.diff
- 
-Note this is *not* the latest version, as they only support Qt 2.0.
+
+Eventually the intent is to fold this patch into the official qtarch and
+release a qtarch-1.4-6 tarball.
+
+Note this is *not* the latest version, as they only support Qt 2.
 
 You should compile in the KDE module when you compile qtarch-1.4.
 For me this was just a case of a make in the module/kde/ directory,
@@ -31,8 +34,22 @@ className field, though, has a special meaning. If it is blank, then qtarch
 will assume there is no derived class defined at all. Currently this has the effect
 of making mapped variables public access. If there is a name, then it assumes that
 a derived class exists, and leaves mapped variables protected. It's done like
-this to avoid the rat's nest of friend declarations and un-necessary derived classes.
-
+this to avoid the rat's nest of friend declarations and un-necessary derived classes,
+and because the new MVC architecture needs direct access to buttons etc.
+
+There is a naming scheme for any variabled widgets, similar to the xforms frontend :
+
+buttons        - button_
+spinboxen      - spin_
+tabstack       - tabstack 
+comboboxen     - combo_
+checkboxen     - check_ 
+lengthentry    - length_ 
+radio buttons  - radio_
+line edits     - line_ 
+emptytable     - table 
+list box       - list_ 
+ 
 Some tips and guidelines for qtarch and the KDE frontend :
 
 o the default button should be the one that causes least harm, unless
@@ -67,10 +84,14 @@ o do the geometry layouts last. you cannot alter the geometry of widgets
   whilst they're being managed which makes any settings a pain, which
   are useful mainly while editing the dialog in qtarch
   
+o remember tab order, and keyboard access in general. Tab order is decided by
+  instantation order of each widget, NOT the heirarchical layout. This translates
+  to ordering the widget descriptions in the qtarch .dlg file correctly.
+ 
 o when doing layout, add all the layouts before any of the widgets otherwise
   qtarch has a tendency to get confused
 
-o qtarch often produces code that initialises stuff in the wrong order. 
+o qtarch can produce code that initialises stuff in the wrong order. 
   This is nasty, but usually dumps core so is noticable. Either way, the 
   cheesy perl script checkinitorder.pl will verify the produced files for 
   you - if it complains you need to hack the .dlg file to re-arrange the order.