find tdeio plugin
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

556 lines
16KB

  1. <?xml version="1.0" ?>
  2. <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
  3. <!ENTITY find "<application>find 0.1</application>">
  4. <!ENTITY kappname "&find;"><!-- Do *not* replace kappname-->
  5. <!ENTITY package "kde-module"><!-- tdebase, tdeadmin, etc -->
  6. <!ENTITY % addindex "IGNORE">
  7. <!ENTITY % English "INCLUDE"><!-- change language only here -->
  8. <!-- Do not define any other entities; instead, use the entities
  9. from kde-genent.entities and $LANG/user.entities. -->
  10. ]>
  11. <!-- kdoctemplate v0.8 October 1 1999
  12. Minor update to "Credits and Licenses" section on August 24, 2000
  13. Removed "Revision history" section on 22 January 2001
  14. Changed to Installation/Help menu entities 18 October 2001
  15. Other minor cleanup and changes 18 October 2001 -->
  16. <!--
  17. This template was designed by: David Rugge davidrugge@mindspring.com
  18. with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
  19. and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
  20. of the KDE DocBook team.
  21. You may freely use this template for writing any sort of KDE documentation.
  22. If you have any changes or improvements, please let us know.
  23. Remember:
  24. - in XML, the case of the <tags> and attributes is relevant ;
  25. - also, quote all attributes.
  26. Please don't forget to remove all these comments in your final documentation,
  27. thanks ;-).
  28. -->
  29. <!-- ................................................................ -->
  30. <!-- The language must NOT be changed here. -->
  31. <book lang="&language;">
  32. <!-- This header contains all of the meta-information for the document such
  33. as Authors, publish date, the abstract, and Keywords -->
  34. <bookinfo>
  35. <title>The &find; Handbook</title>
  36. <authorgroup>
  37. <author>
  38. <firstname></firstname>
  39. <othername></othername>
  40. <surname>Andreas Eckstein</surname>
  41. <affiliation>
  42. <address><email>andreas.eckstein@gmx.net</email></address>
  43. </affiliation>
  44. </author>
  45. </authorgroup>
  46. <!-- TRANS:ROLES_OF_TRANSLATORS -->
  47. <copyright>
  48. <year>1999</year>
  49. <year>2007</year>
  50. <holder>Andreas Eckstein</holder>
  51. </copyright>
  52. <!-- Translators: put here the copyright notice of the translation -->
  53. <!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
  54. and in the FDL itself on how to use it. -->
  55. <legalnotice>&FDLNotice;</legalnotice>
  56. <!-- Date and version information of the documentation
  57. Don't forget to include this last date and this last revision number, we
  58. need them for translation coordination !
  59. Please respect the format of the date (YYYY-MM-DD) and of the version
  60. (V.MM.LL), it could be used by automation scripts.
  61. Do NOT change these in the translation. -->
  62. <date>2001-10-18</date>
  63. <releaseinfo>0.1</releaseinfo>
  64. <!-- Abstract about this handbook -->
  65. <abstract>
  66. <para>
  67. &find; is an application specially designed to do nothing you would
  68. ever want.
  69. </para>
  70. </abstract>
  71. <!-- This is a set of Keywords for indexing by search engines.
  72. Please at least include KDE, the KDE package it is in, the name
  73. of your application, and a few relevant keywords. -->
  74. <keywordset>
  75. <keyword>KDE</keyword>
  76. <keyword>find</keyword>
  77. <keyword>nothing</keyword>
  78. <keyword>nothing else</keyword>
  79. </keywordset>
  80. </bookinfo>
  81. <!-- The contents of the documentation begin here. Label
  82. each chapter so with the id attribute. This is necessary for two reasons: it
  83. allows you to easily reference the chapter from other chapters of your
  84. document, and if there is no ID, the name of the generated HTML files will vary
  85. from time to time making it hard to manage for maintainers and for the CVS
  86. system. Any chapter labelled (OPTIONAL) may be left out at the author's
  87. discretion. Other chapters should not be left out in order to maintain a
  88. consistent documentation style across all KDE apps. -->
  89. <chapter id="introduction">
  90. <title>Introduction</title>
  91. <!-- The introduction chapter contains a brief introduction for the
  92. application that explains what it does and where to report
  93. problems. Basically a long version of the abstract. Don't include a
  94. revision history. (see installation appendix comment) -->
  95. <para>
  96. &find; is a program that lets you do absolutely nothing. Please report
  97. any problems or feature requests to the &kde; mailing lists.
  98. </para>
  99. </chapter>
  100. <chapter id="using-find">
  101. <title>Using &find;</title>
  102. <!-- This chapter should tell the user how to use your app. You should use as
  103. many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
  104. your application. -->
  105. <para>
  106. <!-- Note that all graphics should be in .png format. Use no gifs because of
  107. patent issues. -->
  108. <screenshot>
  109. <screeninfo>Here's a screenshot of &find;</screeninfo>
  110. <mediaobject>
  111. <imageobject>
  112. <imagedata fileref="screenshot.png" format="PNG"/>
  113. </imageobject>
  114. <imageobject>
  115. <imagedata fileref="screenshot.eps" format="EPS"/>
  116. </imageobject>
  117. <textobject>
  118. <phrase>Screenshot</phrase>
  119. </textobject>
  120. </mediaobject>
  121. </screenshot>
  122. </para>
  123. <sect1 id="find-features">
  124. <title>More &find; features</title>
  125. <para>It slices! It dices! and it comes with a free toaster!</para>
  126. <para>
  127. The Stquiggle Tool <guiicon><inlinemediaobject>
  128. <imageobject>
  129. <imagedata fileref="stquiggle.png" format="PNG"/>
  130. </imageobject>
  131. <imageobject>
  132. <imagedata fileref="stquiggle.eps" format="EPS"/>
  133. </imageobject>
  134. <textobject>
  135. <phrase>Stquiggle</phrase>
  136. </textobject>
  137. </inlinemediaobject></guiicon> is used to draw stquiggly lines all over
  138. the &find; main window. It's not a bug, it's a feature!
  139. </para>
  140. </sect1>
  141. </chapter>
  142. <chapter id="commands">
  143. <title>Command Reference</title>
  144. <!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
  145. application windows and their menubar and toolbar commands for easy reference.
  146. Also include any keys that have a special function but have no equivalent in the
  147. menus or toolbars. This may not be necessary for small apps or apps with no tool
  148. or menu bars. -->
  149. <sect1 id="find-mainwindow">
  150. <title>The main &find; window</title>
  151. <sect2>
  152. <title>The File Menu</title>
  153. <para>
  154. <variablelist>
  155. <varlistentry>
  156. <term><menuchoice>
  157. <shortcut>
  158. <keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
  159. </shortcut>
  160. <guimenu>File</guimenu>
  161. <guimenuitem>New</guimenuitem>
  162. </menuchoice></term>
  163. <listitem><para><action>Creates a new document</action></para></listitem>
  164. </varlistentry>
  165. <varlistentry>
  166. <term><menuchoice>
  167. <shortcut>
  168. <keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo>
  169. </shortcut>
  170. <guimenu>File</guimenu>
  171. <guimenuitem>Save</guimenuitem>
  172. </menuchoice></term>
  173. <listitem><para><action>Saves the document</action></para></listitem>
  174. </varlistentry>
  175. <varlistentry>
  176. <term><menuchoice>
  177. <shortcut>
  178. <keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
  179. </shortcut>
  180. <guimenu>File</guimenu>
  181. <guimenuitem>Quit</guimenuitem>
  182. </menuchoice></term>
  183. <listitem><para><action>Quits</action> &find;</para></listitem>
  184. </varlistentry>
  185. </variablelist>
  186. </para>
  187. </sect2>
  188. <sect2>
  189. <title>The <guimenu>Help</guimenu> Menu</title>
  190. <!-- Assuming you have a standard help menu (help, what's this, about -->
  191. <!-- &find;, about KDE) then the documentation is already written. -->
  192. <!-- The following entity is valid anywhere that a variablelist is -->
  193. <!-- valid. -->
  194. &help.menu.documentation;
  195. </sect2>
  196. </sect1>
  197. </chapter>
  198. <chapter id="developers">
  199. <title>Developer's Guide to &find;</title>
  200. <!-- (OPTIONAL) A Programming/Scripting reference chapter should be
  201. used for apps that use plugins or that provide their own scripting hooks
  202. and/or development libraries. -->
  203. <para>
  204. Programming &find; plugins is a joy to behold. Just read through the next
  205. 66 pages of API's to learn how!
  206. </para>
  207. <!-- Use refentries to describe APIs. Refentries are fairly complicated and you
  208. should consult the docbook reference for further details. The example below was
  209. taken from that reference and shortened a bit for readability. -->
  210. <refentry id="re-1007-unmanagechildren-1">
  211. <refmeta>
  212. <refentrytitle>XtUnmanageChildren</refentrytitle>
  213. <refmiscinfo>Xt - Geometry Management</refmiscinfo>
  214. </refmeta>
  215. <refnamediv>
  216. <refname>XtUnmanageChildren
  217. </refname>
  218. <refpurpose>remove a list of children from a parent widget's managed
  219. list.
  220. <indexterm id="ix-1007-unmanagechildren-1"><primary>widgets</primary><secondary>removing</secondary></indexterm>
  221. <indexterm id="ix-1007-unmanagechildren-2"><primary>XtUnmanageChildren</primary></indexterm>
  222. </refpurpose>
  223. </refnamediv>
  224. <refsynopsisdiv>
  225. <refsynopsisdivinfo>
  226. <date>4 March 1996</date>
  227. </refsynopsisdivinfo>
  228. <synopsis>
  229. void XtUnmanageChildren(<replaceable class="parameter">children</replaceable>, <replaceable class="parameter">num_children</replaceable>)
  230. WidgetList <replaceable class="parameter">children</replaceable>;
  231. Cardinal <replaceable class="parameter">num_children</replaceable>;
  232. </synopsis>
  233. <refsect2 id="r2-1007-unmanagechildren-1">
  234. <title>Inputs</title>
  235. <variablelist>
  236. <varlistentry>
  237. <term><replaceable class="parameter">children</replaceable>
  238. </term>
  239. <listitem>
  240. <para>Specifies an array of child widgets. Each child must be of
  241. class RectObj or any subclass thereof.
  242. </para>
  243. </listitem>
  244. </varlistentry>
  245. <varlistentry>
  246. <term><replaceable class="parameter">num_children</replaceable>
  247. </term>
  248. <listitem>
  249. <para>Specifies the number of elements in <replaceable class="parameter">children</replaceable>.
  250. </para>
  251. </listitem>
  252. </varlistentry>
  253. </variablelist>
  254. </refsect2></refsynopsisdiv>
  255. <refsect1 id="r1-1007-unmanagechildren-1">
  256. <title>Description
  257. </title>
  258. <para><function>XtUnmanageChildren()</function> unmaps the specified widgets
  259. and removes them from their parent's geometry management.
  260. The widgets will disappear from the screen, and (depending
  261. on its parent) may no longer have screen space allocated for
  262. them.
  263. </para>
  264. <para>Each of the widgets in the <replaceable class="parameter">children</replaceable> array must have
  265. the same parent.
  266. </para>
  267. <para>See the &ldquo;Algorithm&rdquo; section below for full details of the
  268. widget unmanagement procedure.
  269. </para>
  270. </refsect1>
  271. <refsect1 id="r1-1007-unmanagechildren-2">
  272. <title>Usage</title>
  273. <para>Unmanaging widgets is the usual method for temporarily
  274. making them invisible. They can be re-managed with
  275. <function>XtManageChildren()</function>.
  276. </para>
  277. <para>You can unmap a widget, but leave it under geometry
  278. management by calling <function>XtUnmapWidget()</function>. You can
  279. destroy a widget's window without destroying the widget by
  280. calling <function>XtUnrealizeWidget()</function>. You can destroy a
  281. widget completely with <function>XtDestroyWidget()</function>.
  282. </para>
  283. <para>If you are only going to unmanage a single widget, it is
  284. more convenient to call <function>XtUnmanageChild()</function>. It is
  285. often more convenient to call <function>XtUnmanageChild()</function>
  286. several times than it is to declare and initialize an array
  287. of widgets to pass to <function>XtUnmanageChildren()</function>. Calling
  288. <function>XtUnmanageChildren()</function> is more efficient, however,
  289. because it only calls the parent's <function>change_managed()</function>
  290. method once.
  291. </para>
  292. </refsect1>
  293. <refsect1 id="r1-1007-unmanagechildren-3">
  294. <title>Algorithm
  295. </title>
  296. <para><function>XtUnmanageChildren()</function> performs the following:
  297. </para>
  298. <variablelist>
  299. <varlistentry>
  300. <term>-
  301. </term>
  302. <listitem>
  303. <para>Ignores the child if it already is unmanaged or is being
  304. destroyed.
  305. </para>
  306. </listitem>
  307. </varlistentry>
  308. <varlistentry>
  309. <term>-
  310. </term>
  311. <listitem>
  312. <para>Otherwise, if the child is realized, it makes it nonvisible
  313. by unmapping it.
  314. </para>
  315. </listitem>
  316. </varlistentry>
  317. </variablelist>
  318. <para>
  319. </para>
  320. </refsect1>
  321. <refsect1 id="r1-1007-unmanagechildren-4">
  322. <title>Structures</title>
  323. <para>The <type>WidgetList</type> type is simply an array of widgets:
  324. </para>
  325. <screen id="sc-1007-unmanagechildren-1">typedef Widget *WidgetList;
  326. </screen>
  327. </refsect1>
  328. </refentry>
  329. </chapter>
  330. <chapter id="faq">
  331. <title>Questions and Answers</title>
  332. <!-- (OPTIONAL but recommended) This chapter should include all of the silly
  333. (and not-so-silly) newbie questions that fill up your mailbox. This chapter
  334. should be reserved for BRIEF questions and answers! If one question uses more
  335. than a page or so then it should probably be part of the
  336. "Using this Application" chapter instead. You should use links to
  337. cross-reference questions to the parts of your documentation that answer them.
  338. This is also a great place to provide pointers to other FAQ's if your users
  339. must do some complicated configuration on other programs in order for your
  340. application work. -->
  341. &reporting.bugs;
  342. &updating.documentation;
  343. <qandaset id="faqlist">
  344. <qandaentry>
  345. <question>
  346. <para>My Mouse doesn't work. How do I quit &find;?</para>
  347. </question>
  348. <answer>
  349. <para>You silly goose! Check out the <link linkend="commands">Commands
  350. Section</link> for the answer.</para>
  351. </answer>
  352. </qandaentry>
  353. <qandaentry>
  354. <question>
  355. <para>Why can't I twiddle my documents?</para>
  356. </question>
  357. <answer>
  358. <para>You can only twiddle your documents if you have the foobar.lib
  359. installed.</para>
  360. </answer>
  361. </qandaentry>
  362. </qandaset>
  363. </chapter>
  364. <chapter id="credits">
  365. <!-- Include credits for the programmers, documentation writers, and
  366. contributors here. The license for your software should then be included below
  367. the credits with a reference to the appropriate license file included in the KDE
  368. distribution. -->
  369. <title>Credits and License</title>
  370. <para>
  371. &find;
  372. </para>
  373. <para>
  374. Program copyright 2007 Andreas Eckstein <email>andreas.eckstein@gmx.net</email>
  375. </para>
  376. <para>
  377. Contributors:
  378. <itemizedlist>
  379. <listitem><para>Kontqui the KDE Dragon <email>kontqui@kde.org</email></para>
  380. </listitem>
  381. <listitem><para>Tux the Linux Penguin <email>tux@linux.org</email></para>
  382. </listitem>
  383. </itemizedlist>
  384. </para>
  385. <para>
  386. Documentation copyright 2007 Andreas Eckstein <email>andreas.eckstein@gmx.net</email>
  387. </para>
  388. <!-- TRANS:CREDIT_FOR_TRANSLATORS -->
  389. &underFDL; <!-- FDL: do not remove -->
  390. <!-- Determine which license your application is licensed under,
  391. and delete all the remaining licenses below:
  392. (NOTE: All documentation are licensed under the FDL,
  393. regardless of what license the application uses) -->
  394. &underGPL; <!-- GPL License -->
  395. &underBSDLicense; <!-- BSD License -->
  396. &underArtisticLicense; <!-- BSD Artistic License -->
  397. &underX11License; <!-- X11 License -->
  398. </chapter>
  399. <appendix id="installation">
  400. <title>Installation</title>
  401. <sect1 id="getting-find">
  402. <title>How to obtain &find;</title>
  403. <!-- This first entity contains boiler plate for applications that are
  404. part of KDE CVS. You should remove it if you are releasing your
  405. application -->
  406. &install.intro.documentation;
  407. </sect1>
  408. <sect1 id="requirements">
  409. <title>Requirements</title>
  410. <!--
  411. List any special requirements for your application here. This should include:
  412. .Libraries or other software that is not included in tdesupport,
  413. tdelibs, or tdebase.
  414. .Hardware requirements like amount of RAM, disk space, graphics card
  415. capabilities, screen resolution, special expansion cards, etc.
  416. .Operating systems the app will run on. If your app is designed only for a
  417. specific OS, (you wrote a graphical LILO configurator for example) put this
  418. information here.
  419. -->
  420. <para>
  421. In order to successfully use &find;, you need &kde; 1.1. Foobar.lib is
  422. required in order to support the advanced &find; features. &find; uses
  423. about 5 megs of memory to run, but this may vary depending on your
  424. platform and configuration.
  425. </para>
  426. <para>
  427. All required libraries as well as &find; itself can be found
  428. on <ulink url="ftp://ftp.find.org">The &find; home page</ulink>.
  429. </para>
  430. <!-- For a list of updates, you may refer to the application web site
  431. or the ChangeLog file, or ... -->
  432. <para>
  433. You can find a list of changes at <ulink
  434. url="http://apps.kde.org/find">http://apps.kde.org/find</ulink>.
  435. </para>
  436. </sect1>
  437. <sect1 id="compilation">
  438. <title>Compilation and Installation</title>
  439. <!-- This entity contains the boilerplate text for standard -->
  440. <!-- compilation instructions. If your application requires any -->
  441. <!-- special handling, remove it, and replace with your own text. -->
  442. &install.compile.documentation;
  443. </sect1>
  444. <sect1 id="configuration">
  445. <title>Configuration</title>
  446. <para>Don't forget to tell your system to start the <filename>dtd</filename>
  447. dicer-toaster daemon first, or &find; won't work !</para>
  448. </sect1>
  449. </appendix>
  450. &documentation.index;
  451. </book>
  452. <!--
  453. Local Variables:
  454. mode: sgml
  455. sgml-minimize-attributes:nil
  456. sgml-general-insert-case:lower
  457. sgml-indent-step:0
  458. sgml-indent-data:nil
  459. End:
  460. vim:tabstop=2:shiftwidth=2:expandtab
  461. -->