From e985f7e545f4739493965aad69bbecb136dc9346 Mon Sep 17 00:00:00 2001 From: tpearson Date: Thu, 16 Jun 2011 19:02:47 +0000 Subject: TQt4 port kdewebdev This enables compilation under both Qt3 and Qt4 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdewebdev@1237029 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- kommander/Kommander-TODO.kno | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'kommander/Kommander-TODO.kno') diff --git a/kommander/Kommander-TODO.kno b/kommander/Kommander-TODO.kno index ebbe5651..d21460b5 100644 --- a/kommander/Kommander-TODO.kno +++ b/kommander/Kommander-TODO.kno @@ -16,10 +16,10 @@ \NewEntry 1 Editor

Layout of Edit Kommander Text dialog

Old ideas:

better layout

better tqlayout
replace list of widgets with tree of widgets
replace widget class with widget pixmap in combos
redesign layout
redesign tqlayout
cleanup Connections, not it is unusable, may be obsolete
find in scripts
list of non-empty scripts for current dialog
use KDE dialogs, not Qt ones if possible
some widget information on mouseover
review of event model
add more layout-handling commands (center selected widgets horizontally/vertically, fit to window width/height)
add more tqlayout-handling commands (center selected widgets horizontally/vertically, fit to window width/height)
handle middle click
carefully check defaults, choose most useful ones
add wizards? (replace current New dialogs with Kommander-based ones?)

Other GUI-related issues

cleanup slots/signals/connections interface
find out why slots are shown only for current tab

cleanup Q_SLOTS/Q_SIGNALS/connections interface
find out why Q_SLOTS are shown only for current tab

KDE4 ideas:

create a KDevelop plugin for the editor
use KFormDesigner or the new Qt Designer

Charset is sometimes incorrectly converted from/to local charset
SubDialog crashes now
Labels do not show up unless you edit their text
toolbox editing is ugly after group layout is applied. Goes back to normal if the dialog is reloaded.
toolbox editing is ugly after group tqlayout is applied. Goes back to normal if the dialog is reloaded.

detect incorrect path at shebang, allow user to choose correct one and remeber that pair

If we keep the old parser.

Make it possible to use any language with Kommander. The idea is to replace Kommander specials with language specific code in a way that it will not break conditions and loops, like now. example:
#!/bin/bash
array="1 2 3 4 5"
for i in $array do
@Label.setText($i)
done

This does not work now. The idea is to replace @Widget.method() with a language specific DCOP call.
If the language has DCOP bindings, use those bindings to execute the dcop call. If not, use the command line
DCOP application. This is slower, but always works. In the above case, Kommander would replace
@Label.setText($i)
with
dcop kmdr-executor-PID KommanderIf setText Label $i

Kommander will have description files for each supported language about how to execute DCOP calls.
If the language has DCOP bindings, this description tells the syntax of the bindings. If it doesn't have, the description gives a way how to execute external applications. This should always exists, as all languages can execute external applications.

In KDE4, of course use DBUS instead of DCOP.

If we keep the old parser.

Make it possible to use any language with Kommander. The idea is to replace Kommander specials with language specific code in a way that it will not break conditions and loops, like now. example:
#!/bin/bash
array="1 2 3 4 5"
for i in $array do
@Label.setText($i)
done

This does not work now. The idea is to tqreplace @Widget.method() with a language specific DCOP call.
If the language has DCOP bindings, use those bindings to execute the dcop call. If not, use the command line
DCOP application. This is slower, but always works. In the above case, Kommander would tqreplace
@Label.setText($i)
with
dcop kmdr-executor-PID KommanderIf setText Label $i

Kommander will have description files for each supported language about how to execute DCOP calls.
If the language has DCOP bindings, this description tells the syntax of the bindings. If it doesn't have, the description gives a way how to execute external applications. This should always exists, as all languages can execute external applications.

In KDE4, of course use DBUS instead of DCOP.

New signals for existing widgets

add signals for D&D
Requires dragContent and dragType, perhaps dragSource to be set.

New Q_SIGNALS for existing widgets

add Q_SIGNALS for D&D
Requires dragContent and dragType, perhaps dragSource to be set.

New widgets include the DatePicker, Popup Menu and Toolbox. New functions inlcude widget creation, hooking and unhooking signals and slots and full slot access as well as passing and returning parameters in scripts. WooHoo! Take that do list!

New widgets include the DatePicker, Popup Menu and Toolbox. New functions inlcude widget creation, hooking and unhooking Q_SIGNALS and Q_SLOTS and full slot access as well as passing and returning parameters in scripts. WooHoo! Take that do list!

fixed dcop functions
added indexed array functions
made color slot work in TextEdit

Executing Kommander scripts

detect and handle missing plugin widgets
cache @pid, @dcopid, @parentPid, perhaps calculate and cache @parentdcopid
cache @pid, @dcopid, @tqparentPid, perhaps calculate and cache @tqparentdcopid
handle multiple dialogs: they could be packaged in single *.tgz file, unpacked and executed internally

ChangeLog of Kommander
See ChangeLog file for details and dates

added @parentPid evaluated to parent process pid

added @tqparentPid evaluated to tqparent process pid
added @pid evaluated to current process pid
added @dcopid evaluated to current process DCOP id
significantly improved Kommander Text editor usability