[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-13 6:18:10
Message-ID: 1202883490.472531.5712.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 774372 by sequitur:

minor clean up, remove excess and repetitive text and add web site link

 M  +4 -1      basics.docbook  
 M  +2 -2      index.docbook  


--- branches/KDE/3.5/kdewebdev/doc/kommander/basics.docbook #774371:774372
@@ -124,8 +124,11 @@
 For security reasons we introduced the executable bit requirement in version 1.3. \
Some will applaud this as long overdue. Others will consider it a terrible annoyance \
or even too scarey to use. Unfortunately there is no perfect solution. The problem is \
that you can download a Kommander dialog from anywhere or get one in your email and \
click on it and run it by accident. Because Kommander can run shell scripts it is \
sort of in an odd place. While other applications don't nag you this way you actually \
had to install them so clearly you felt safe and intended to run them. A single line \
of shell scripting could permanently wipe out your home directory. Our intent is to \
eliminate an accidental click on an untrusted dialog. We aplogize for any \
inconvenience, but there is no way to do this to even the developer's satisfaction \
that it will not annoy you while keeping you safe.   </para>
 <para>
-You are not prevented from running a dialog, just nagged. You can make it go away by \
using a file manager or the shell to set the executable bit. Right click on the \
dialog in Konqueror, select properties from the menu, choose the permissions tab and \
check the <quote>is executable</quote> checkbox. Now the nag will be gone from this \
dialog forever. Check our web site for a tool that searchesfor &kommander; dialogs \
and allows you to review them and choose whether any or all of them should have the \
bit set. To use the shell and make all the &kommander; dialogs in a directory \
executable use this command. <command>chmod u+x *.kmdr</command> +You are not \
prevented from running a dialog, just nagged. You can make it go away by using a file \
manager or the shell to set the executable bit. Right click on the dialog in \
Konqueror, select properties from the menu, choose the permissions tab and check the \
<quote>is executable</quote> checkbox. Now the nag will be gone from this dialog \
forever. Check our web site for a tool that searchesfor &kommander; dialogs and \
allows you to review them and choose whether any or all of them should have the bit \
set. To use the shell and make all the &kommander; dialogs in a directory executable \
use this command.   </para>
+<screen>
+chmod u+x *.kmdr
+</screen>
 <warning><para>Do not set dialogs as executable if you are not confident of their \
origin.</para></warning>  </sect1>
 
--- branches/KDE/3.5/kdewebdev/doc/kommander/index.docbook #774371:774372
@@ -88,9 +88,9 @@
 <!-- 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>These docs have been partially complete for \
years, but not always available or easy to find. Since around 2002 little spurts of \
effort on &kommander; have produced dramtic results. &kommander; is a new approach to \
development and 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 web site at <ulink \
url="http://kommander.kdewebdev.org">http://kommander.kdewebdev.org</ulink> for up to \
date information, news on KDE4 development, new tools, plugins, tips and \
tutorials.</para>  <para>
-&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 extentions 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 e  xposes \
much of it, and with some work everything to any DCOP enabled language. So if you \
like Rexx you can use it in &kommander;. +&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 extentions 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. &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. We welcome anyone \
wishing to enhance support for any scripting language.  </para>
 </abstract>
 


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