Development/Tutorials/Using KActions - Revision history

AnneW at 15:18, 13 July 2012

2012-07-13T15:18:25Z

2011-11-05T01:49:28Z

‎XMLGUI: Remove link to developer.kde.org

2011-11-05T01:48:15Z

‎Adding the action to menus and toolbars: XMLGUI was never removed, remove note instead.

2011-09-27T07:10:41Z

dead link--

2011-09-18T13:58:22Z

‎Moving On

2011-06-30T11:45:25Z

‎CMake: Fix syntax highlighting.

2011-06-27T12:30:11Z

Fix syntax highlighting.

2011-01-13T02:59:38Z

ah, it was the equals sign...*kicks wikis*

2011-01-13T02:54:01Z

fucking quotes

2011-01-13T02:52:25Z

make the "aaaggh versions can't be decimals" warning...an actual warning. hopefully nobody else falls into this trap.

← Older revision		Revision as of 15:18, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Tutorials/Using_KActions}}~~

	{{TutorialBrowser\|		{{TutorialBrowser\|

← Older revision		Revision as of 01:49, 5 November 2011
Line 180:		Line 180:

	The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class\|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.		The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class\|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.
−
−	~~''See also'' [http://developer.kde.org/documentation/library/kdeqt/kde3arch/xmlgui.html developer.kde.org] which still provides valid information for KDE4.~~

	==''appname''ui.rc File==		==''appname''ui.rc File==

@@ Line 171: / Line 171: @@
 ==Adding the action to menus and toolbars==
 At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.
 ==Defining your own help menu==

@@ Line 175: / Line 175: @@
 ==Defining your own help menu==
-The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, go [http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/widgets/khelpmenu.h?revision=1002779&view=markup here] and search for the explanation around showAboutApplication().
+The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, search for the explanation around showAboutApplication() in kdelibs.
 ==XMLGUI==

@@ Line 262: / Line 262: @@
 ==Moving On==
 Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].
 [[Category:C++]]

@@ Line 226: / Line 226: @@
 Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
 ===CMakeLists.txt===
-<pre>
+<syntaxhighlight lang="cmake">
 project(tutorial3)
@@ Line 244: / Line 244: @@
 install(FILES tutorial3ui.rc
          DESTINATION  ${DATA_INSTALL_DIR}/tutorial3)
-</pre>
+</syntaxhighlight>
 This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.
@@ Line 252: / Line 252: @@
 To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
-<pre>
+<syntaxhighlight lang="bash">
 mkdir build && cd build
 cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
 make install
 $HOME/bin/tutorial3
-</pre>
+</syntaxhighlight>
 which will create a KDE-like directory structure in your user's home directory and will install the executable to {{path|$HOME/bin/tutorial3}}.

@@ Line 211: / Line 211: @@
 Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '
-{{Warning|The version attribute must be an integer number, if you type in version=1.2 it will dispose of your kittens  (but not eat them).}}
+{{Warning|The version attribute must be an integer number, if you type in version<nowiki>=</nowiki>"1.2" it will dispose of your kittens  (but not eat them).}}
 Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.

@@ Line 209: / Line 209: @@
 Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.
-Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '''Note:''' The version attribute must be an integer number, i.e. it may not contain dots or other non-digits like an application version number.
+Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '
 Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.