@ -325,7 +325,7 @@ The examples are installed to <command>$TDEDIR/share/apps/kmdr-editor/editor</co
<para>
The little dialog that grew into a Mainwindow. As &kommander; does not have a native MainWindow widget it has been assumed it only does dialogs. In fact only dialogs are officially supported... but you can run MainWindows in &kommander;. This is an example editor. If you want to create a MainWindow application in &kommander; just open Qt Designer and make one, save it and rename the *.ui file to a *.kmdr file. Now open it in &kommander; and do what you would do normally.
</para>
<note><para>As of this writing what is known not to work on the &kommander; side is the settings read and write. There is no Initialize or Destroy section as there is no &kommander; Text, however there are signals for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any actions via DCOP as these are QActions from Designer and KActions are not derived from QActions in KDE 3.x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Even though this is not a &kommander; widget, or officicially supported, it seems suitable for many small application uses.</para></note>
<note><para>As of this writing what is known not to work on the &kommander; side is the settings read and write. There is no Initialize or Destroy section as there is no &kommander; Text, however there are signals for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any actions via DCOP as these are QActions from Designer and TDEActions are not derived from QActions in KDE 3.x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Even though this is not a &kommander; widget, or officicially supported, it seems suitable for many small application uses.</para></note>
<para>
There is a quick help dialog this editor launches that discusses in depth what is happening inside.
@ -132,7 +132,7 @@ A ListBox has only one state, default.
The widget text for a ListBox is the items contained in the ListBox. @selectedWidgetText will return only the items that are currently selected.
</para>
<para>
See the KListBox documentation to learn more about it.
See the TDEListBox documentation to learn more about it.
</para>
</listitem>
</varlistentry>
@ -172,7 +172,7 @@ TreeWidget
A widget that provides a list in the form of a tree structure. You can add child items and multi-column data. The current limitation is that you cannot modify columns. To add a child node use <quote>/</quote> as a separator. To add column data use the escaped tab <quote>\t</quote> character between columns.
</para>
<para>
See the KListView documentation to learn more about it.
See the TDEListView documentation to learn more about it.
</para>
</listitem>
@ -316,7 +316,7 @@ RadioButton has 2 states checked and unchecked.
There is no widget text associated with a RadioButton.
</para>
<para>
See the KRadioButton documentation to learn more about it.
See the TDERadioButton documentation to learn more about it.
<string>Displays the connections between the sender and the receiver.</string>
</property>
</widget>
<widget class="KListBox" row="1" column="1">
<widget class="TDEListBox" row="1" column="1">
<property name="name">
<cstring>slotBox</cstring>
</property>
@ -119,7 +119,7 @@
<string><b>A list of Q_SLOTS for the receiver.</b><p>The Q_SLOTS that are displayed are only those which have arguments that correspond with the arguments of the signal that is currently selected in the Signal-list.</b></string>
actionEditLower->setToolTip(i18n("Lowers the selected widgets"));
actionEditLower->setWhatsThis(i18n("Lowers the selected widgets"));
actionEditLower->setEnabled(false);
actionEditFindGlobal=newKAction(i18n("Find in Form..."),CTRL+ALT+Key_F,TQT_TQOBJECT(this),TQT_SLOT(editFindGlobal()),actionCollection(),"edit_find_global");
actionEditFindGlobal=newTDEAction(i18n("Find in Form..."),CTRL+ALT+Key_F,TQT_TQOBJECT(this),TQT_SLOT(editFindGlobal()),actionCollection(),"edit_find_global");
actionEditFindGlobal->setToolTip(i18n("Search for a text in the whole form."));
actionEditFindGlobal->setWhatsThis(whatsThisFrom("Edit|Find in Form"));
<string>@Array.setValue(help, "Proof of concept", "&lt;center&gt;&lt;h2&gt;Kommander MainWindow frames!&lt;/h2&gt;&lt;/center&gt;&lt;p&gt;As Kommander took on functionality an attempt was made to make a MainWindow Kommander widget. Sadly it was a huge time loss for two developers who both gave up after days of trying. The problem was with the editor. However you can use a Qt Designer generated UI file renamed to a *.kmdr file. Into this frame you can place your widgets and make a working application where nearly everything works.&lt;/p&gt;")
@Array.setValue(help, "Known limitations", "&lt;center&gt;&lt;h2&gt;Known limitations&lt;/h2&gt;&lt;/center&gt;&lt;p&gt;As of this writing what is known not to work on the Kommander side is the settings read and write. There is no Initialize or Destroy section as there is no Kommander Text, however there are Q_SIGNALS for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any Actions as these are QActions from Designer and KActions are not derived from QActions in KDE 3x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Given that this is an unsupported use of Kommander it everything that does work makes it suitable for probably most small application uses.. &lt;/p&gt;")
@Array.setValue(help, "Known limitations", "&lt;center&gt;&lt;h2&gt;Known limitations&lt;/h2&gt;&lt;/center&gt;&lt;p&gt;As of this writing what is known not to work on the Kommander side is the settings read and write. There is no Initialize or Destroy section as there is no Kommander Text, however there are Q_SIGNALS for this on the window, so the functionality is intact. On the MainWindow side it is not possible to talk to any Actions as these are QActions from Designer and TDEActions are not derived from QActions in KDE 3x. This means a DCOP call to list actions or set states will not work. It is also not possible to talk to the Statusbar. Also submenus on the menubar and dropdown actions on the Toolbar will not work. Given that this is an unsupported use of Kommander it everything that does work makes it suitable for probably most small application uses.. &lt;/p&gt;")
@Array.setValue(help, "Rolling your own", "&lt;center&gt;&lt;h2&gt;Rolling your own&lt;/h2&gt;&lt;/center&gt;&lt;p&gt;It is our intention to have a template in the 1.3 release of a MainWindow, but if you have Qt Designer for Qt 3x you can easily start a window design, save it, rename to *.kmdr and open in Kommander. Remember not to add widgets in Designer as Kommander will not recognize them.&lt;/p&gt;")
@Array.setValue(help, "Using Actions", "&lt;center&gt;&lt;h2&gt;Using Actions&lt;/h2&gt;&lt;/center&gt;&lt;p&gt;If you want to get the goodies, menus, toolbars and accelerator keys, you need to use actions. Kommander has an Action editor on the window menu under Views. There you can add actions and there is a shortcut to connecting them with Q_SIGNALS and Q_SLOTS. To get everything working select an Action and look in the properties menu for settings like name, text and icon. For menus and toolbars try right clicking on them for context menus. Now from the Action View drag an Action to the menu or toolbar. See the visual feedback? Just connect your Action to a script and you have three different ways to call it.&lt;/p&gt;
newaction->setToolTip(i18n("Executes the rest of the commands in the current function/file and pauses when it is done (when it reaches a higher level in the backtrace)"));
newaction->setToolTip(i18n("Pauses the scripts if it is running or tracing. If a script is currently not being debugged, it will start in paused mode when started"));
<UML:Class stereotype="" package="" xmi.id="274" abstract="0" documentation="The document handling class. This is somewhat weird, as the Document class should handle all the document related things. The job is distrivute now between this the QuantaView and the QuantaApp class. This must be clearly seperated...
See the operations in order to get a picture what's here." name="QuantaDoc" static="0" scope="200" >
@ -278,7 +278,7 @@ See the operations in order to get a picture what's here." name="QuantaDoc" stat
<UML:Class stereotype="" package="" xmi.id="1211" abstract="0" documentation="KListViewItem specific for the structure tree." name="StructTreeTag" static="0" scope="200" >
<UML:Class stereotype="" package="" xmi.id="1211" abstract="0" documentation="TDEListViewItem specific for the structure tree." name="StructTreeTag" static="0" scope="200" >
<UML:Class stereotype="" package="" xmi.id="1267" abstract="0" documentation="A treeview which has some common file managing methods. It inherits from KListView." name="FileManage" static="0" scope="200" >
<UML:Class stereotype="" package="" xmi.id="1267" abstract="0" documentation="A treeview which has some common file managing methods. It inherits from TDEListView." name="FileManage" static="0" scope="200" >
newKAction(i18n("&Report Bug..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotReportBug()),TQT_TQOBJECT(ac),"help_reportbug");//needed, because quanta_be bugs should be reported for quanta
newTDEAction(i18n("&Report Bug..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotReportBug()),TQT_TQOBJECT(ac),"help_reportbug");//needed, because quanta_be bugs should be reported for quanta
newTDEAction(i18n("Save as &Local Toolbar..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotSaveLocalToolbar()),TQT_TQOBJECT(ac),"toolbars_save_local");
newTDEAction(i18n("Save as &Project Toolbar..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotSaveProjectToolbar()),TQT_TQOBJECT(ac),"toolbars_save_project");
newTDEAction(i18n("&New User Toolbar..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotAddToolbar()),TQT_TQOBJECT(ac),"toolbars_add");
newTDEAction(i18n("&Remove User Toolbar..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotRemoveToolbar()),TQT_TQOBJECT(ac),"toolbars_remove");
newTDEAction(i18n("Re&name User Toolbar..."),0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotRenameToolbar()),TQT_TQOBJECT(ac),"toolbars_rename");
newTDEAction(i18n("Send Toolbar in E&mail..."),"mail_send",0,TQT_TQOBJECT(m_quanta),TQT_SLOT(slotSendToolbar()),TQT_TQOBJECT(ac),"toolbars_send");
(void)newKAction(i18n("&Save Strings List to File..."),"filesaveas",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsSave()),actionCollection(),"strings_save");
(void)newKAction(i18n("&Load Strings List From File..."),"unsortedList",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsLoad()),actionCollection(),"strings_load");
(void)newTDEAction(i18n("&Save Strings List to File..."),"filesaveas",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsSave()),actionCollection(),"strings_save");
(void)newTDEAction(i18n("&Load Strings List From File..."),"unsortedList",0,TQT_TQOBJECT(this),TQT_SLOT(slotStringsLoad()),actionCollection(),"strings_load");
Timothy Pearson
12 years ago