diff --git a/doc/en/index.docbook b/doc/en/index.docbook index deced89..c7a3ca4 100644 --- a/doc/en/index.docbook +++ b/doc/en/index.docbook @@ -1,555 +1,63 @@ -Guidance"> - - + - - - - + ]> - +
+The &kappname; Handbook - - - - - - - - - - - -The &guidance; Handbook + +The &kappname; Handbook - - - -Simon Edwards - -
simon@simonzone.com
- - +&tde-authors; + - +&tde-release-version; +Reviewed: &tde-release-date; -1999 -%{YEAR} -Simon Edwards +&tde-copyright-date; +&tde-team; - - -&FDLNotice; - - -2001-10-18 -0.1 - - +&FDLNotice; -&guidance; is an application specially designed to do nothing you would -ever want. +&kappname; is a collection of system administration tools for &tde;. - - -KDE -testapp -nothing -nothing else +TDE +guidance +system +administratrion - - - - - -Introduction - - - - -&guidance; is a program that lets you do absolutely nothing. Please report -any problems or feature requests to the &kde; mailing lists. - - - - -Using &guidance; - - - - - - - - -Here's a screenshot of &guidance; - - - - - - - - - Screenshot - - - - - - - -More &guidance; features - -It slices! It dices! and it comes with a free toaster! - -The Squiggle Tool - - - - - - - - Squiggle - - is used to draw squiggly lines all over -the &guidance; main window. It's not a bug, it's a feature! - - - - - - -Command Reference - - - - -The main &guidance; window - - -The File Menu - - - - - -&Ctrl;N - -File -New - -Creates a new document - - - - -&Ctrl;S - -File -Save - -Saves the document - - - - -&Ctrl;Q - -File -Quit - -Quits &guidance; - - - + - + +We Apologize +No documentation has yet been written for &kappname;. - -The <guimenu>Help</guimenu> Menu +If you need help, please check The &tde; +web site, submit questions to the +&tde; mail lists, or file a bug report at the +&tde; bug tracker. - - - - +If you are interested in helping, please consider writing the help file. +Submitting a basic text file is acceptable as the &tde-team; will convert the text. -&help.menu.documentation; +Thank you for helping and thank you for your patience. - +&underFDL; - - - -Developer's Guide to &guidance; - - - - -Programming &guidance; plugins is a joy to behold. Just read through the next -66 pages of API's to learn how! - - - - - - -XtUnmanageChildren -Xt - Geometry Management - - -XtUnmanageChildren - -remove a list of children from a parent widget's managed -list. -widgetsremoving -XtUnmanageChildren - - - - - -4 March 1996 - - -void XtUnmanageChildren(children, num_children) - WidgetList children; - Cardinal num_children; - - - -Inputs - - -children - - -Specifies an array of child widgets. Each child must be of -class RectObj or any subclass thereof. - - - - -num_children - - -Specifies the number of elements in children. - - - - - - - -Description - -XtUnmanageChildren() unmaps the specified widgets -and removes them from their parent's geometry management. -The widgets will disappear from the screen, and (depending -on its parent) may no longer have screen space allocated for -them. - -Each of the widgets in the children array must have -the same parent. - -See the “Algorithm” section below for full details of the -widget unmanagement procedure. - - - - -Usage -Unmanaging widgets is the usual method for temporarily -making them invisible. They can be re-managed with -XtManageChildren(). - -You can unmap a widget, but leave it under geometry -management by calling XtUnmapWidget(). You can -destroy a widget's window without destroying the widget by -calling XtUnrealizeWidget(). You can destroy a -widget completely with XtDestroyWidget(). - -If you are only going to unmanage a single widget, it is -more convenient to call XtUnmanageChild(). It is -often more convenient to call XtUnmanageChild() -several times than it is to declare and initialize an array -of widgets to pass to XtUnmanageChildren(). Calling -XtUnmanageChildren() is more efficient, however, -because it only calls the parent's change_managed() -method once. - - - - -Algorithm - -XtUnmanageChildren() performs the following: - - - -- - - -Ignores the child if it already is unmanaged or is being -destroyed. - - - - -- - - -Otherwise, if the child is realized, it makes it nonvisible -by unmapping it. - - - - - - - - - -Structures -The WidgetList type is simply an array of widgets: - -typedef Widget *WidgetList; - - - - - - - -Questions and Answers - - - -&reporting.bugs; -&updating.documentation; - - - - -My Mouse doesn't work. How do I quit &guidance;? - - -You silly goose! Check out the Commands -Section for the answer. - - - - -Why can't I twiddle my documents? - - -You can only twiddle your documents if you have the foobar.lib -installed. - - - - - - - - - -Credits and License - - -&guidance; - - -Program copyright %{YEAR} Simon Edwards simon@simonzone.com - - -Contributors: - -Konqui the KDE Dragon konqui@kde.org - -Tux the Linux Penguin tux@linux.org - - - - - -Documentation copyright %{YEAR} Simon Edwards simon@simonzone.com - - - - -&underFDL; - - - -&underGPL; -&underBSDLicense; -&underArtisticLicense; -&underX11License; - - - - -Installation - - -How to obtain &guidance; - - - -&install.intro.documentation; - - - - -Requirements - - - - -In order to successfully use &guidance;, you need &kde; 1.1. Foobar.lib is -required in order to support the advanced &guidance; features. &guidance; uses -about 5 megs of memory to run, but this may vary depending on your -platform and configuration. - - - -All required libraries as well as &guidance; itself can be found -on The &guidance; home page. - - - - -You can find a list of changes at http://apps.kde.org/testapp. - - - - -Compilation and Installation - - - - - -&install.compile.documentation; - - - - -Configuration - -Don't forget to tell your system to start the dtd -dicer-toaster daemon first, or &guidance; won't work ! - - - - - -&documentation.index; - - - +