[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    branches/KDE/3.5/kdewebdev/doc/kommander
From:       Eric Laffoon <sequitur () kde ! org>
Date:       2008-02-08 23:56:23
Message-ID: 1202514983.446517.28019.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 772537 by sequitur:

updating docs to reflect changes

 M  +5 -4      index.docbook  
 M  +26 -3     introduction.docbook  


--- branches/KDE/3.5/kdewebdev/doc/kommander/index.docbook #772536:772537
@@ -51,7 +51,7 @@
 <firstname>Eric</firstname>
 <surname>Laffoon</surname>
 <affiliation>
-<address><email>sequitur@kde.org</email></address>
+<address><email>eric@kdewebdev.org</email></address>
 </affiliation>
 </author>
 
@@ -60,7 +60,7 @@
 </authorgroup>
 
 <copyright>
-<year>2004</year>
+<year>2008</year>
 <holder>&kommander; Development Team</holder>
 </copyright>
 
@@ -74,13 +74,14 @@
 Do NOT change these in the translation. -->
 
 <date>2004-05-03</date>
-<releaseinfo>3.2.90</releaseinfo>
+<releaseinfo>3.2.95</releaseinfo>
 
 <!-- Abstract about this handbook -->
 
 <abstract>
+<para>These docs have been partially complete for years, but not always available. \
Ironically given the nature of Kommander dialogs not having a help menu you may not \
have seen them. Over the years since this was worked on there has not been that much \
of the time consistently coding on Kommander, but the results have been dramatic. \
Because Kommander is inherently a new approach to development there have been \
modifications in approach and features. Consequently much of this documentation is \
out of date, however still useful due to legacy support. Please refer to our new \
parser docs and other references on the Kommander subdomain at kdewebdev.org for more \
information on Kommander.</para>  <para>
-&kommander; is a set of tools that allow you to create dynamic &GUI; dialogs that \
generate, based on their state, a piece of text.  The piece of text can be a command \
line to a program, any piece of code, business documents that contain a lot of \
repititious or templated text and so on.  The resulting generated text can then be \
executed as a command line program (hence the name <quote>&kommander;</quote>), \
written to a file, passed to a script for extended processing, and literally anything \
else you can think of.  The best part of it all?  You aren't required to write a \
single line of code! +&kommander; is a set of tools that allow you to create dynamic \
&GUI; windows that has been used as a front end for command line programs, database \
front ends, simple program extntions and much more. The best part of it all?  You \
aren't required to write a single line of code! Okay, that was old text... You can \
actually use the function browser and even with the new parser write almost none of \
the code. The inherent difference between &kommander; and other &GUI; scripting tools \
is that &kommander; doesn't care about how the window gets drawn, syntax holy wars or \
mapping C++ classes. &kommander; only cars about what your widgets have to say to \
each other. &kommander; was designed from the GUI down to the language elements and \
can embrace multiple languages. &kommander; does not use scripting to draw a window \
on the screen like other &GUI; scripting tools. As Kommander matures it will expose \
all it's internals to any scripting language people want to enable, and presently it \
ex  poses much of it, and with some work everything to any DCOP enabled language. So \
if you like Rexx you can use it in &kommander;.  </para>
 </abstract>
 
--- branches/KDE/3.5/kdewebdev/doc/kommander/introduction.docbook #772536:772537
@@ -20,13 +20,36 @@
 <title>Introduction</title>
 
 <para>
-&kommander; is a visual dialog building tool which may be expanded to create
-full mainwindow applications. The primary objective is to create as much
-functionality as possible without using any scripting language. This is
+&kommander; is a visual dialog building tool which can be used to create
+full mainwindow applications, provided the window is initially created in Qt \
Designer  +or from a template in &kommander;. The primary objective is to create as \
much +functionality as possible with the absolute minimum use of scripting. This is
 provided by the following features:
 </para>
+<note>Please note this document includes legacy documentation for compatibility \
reasons. In a nutshell Kommander offers extremely rapid development and extensive \
abilities and capabilities. Following is a new list, followed by the legacy \
content.</note>  
 <itemizedlist>
+<listitem>
+<emphasis>Capable internal scripting</emphasis> - Kommander now offers nested logic \
structures, simple arrays and useful functions  +</listitem>
+<listitem>
+<emphasis>Function Browsers</emphasis> - One never need know exact syntax for any \
function or command, just click the button and point and click your way to a \
functional program. Even the project lead finds it easier than typos much of the \
time. +</listitem>
+<listitem>
+<emphasis>Extensive widgets</emphasis> - Kommander now has a tree/detail widget, \
spreadsheet like table widget, font dialog, color dialog, about dialog, timer, tab \
widgets, toolbox, popup menus, date picker and a lot more.  +</listitem>
+<listitem>
+<emphasis>Plugins</emphasis> - Kommander can run easy to creat plugins. Plugins as \
of this writing are a database plugin offering a set of non visual tools, an HTTP \
plugin offering HTTPS and access to password protected areas and a KPart loader. \
+</listitem> +<listitem>
+<emphasis>Scripting language support</emphasis>The ability to run multiple scripting \
langauge in Komamnder scripts, inside your dialog +</listitem>
+<listitem>
+<emphasis>KPart creation</emphasis> - the ability to make your own plugins... and \
stranger yet you can even make a Kommander window load a dialog as a KPart and \
directly access it with Kommander functions! +</listitem>
+</itemizedlist>
+<para>Look for documentation on tips and tricks like how to make Kommander fake \
programming techniques like including a file, creating and using custom widgets, \
making collapsable panels in windows and other unexpected tricks. Below is our legacy \
list.</para> +<itemizedlist>
 
 
   <listitem><para>Specials are prefaced with an <quote>@</quote> like @widgetText. \
The offer


[prev in list] [next in list] [prev in thread] [next in thread]