From 114a878c64ce6f8223cfd22d76a20eb16d177e5e Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdevelop@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- doc/kdevelop/nutshell.docbook | 242 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 242 insertions(+) create mode 100644 doc/kdevelop/nutshell.docbook (limited to 'doc/kdevelop/nutshell.docbook') diff --git a/doc/kdevelop/nutshell.docbook b/doc/kdevelop/nutshell.docbook new file mode 100644 index 00000000..1c5395dd --- /dev/null +++ b/doc/kdevelop/nutshell.docbook @@ -0,0 +1,242 @@ + +In a Nutshell — Tips and Tricks + + + + +The information in this chapter is meant as a quick reference for a head start or if you (momentarily) forgot about some basic concept. There are also short hints on how to solve some common problems when working with &kdevelop;. + + +If you want more information on a topic, just follow the link in the title starting that advice. + + +Information on these topics is availabe: + + + Look and Feel + Projects + Compilation + &automanag; + Compile/Make Problems + Other Topics + + + +Look and Feel + + +Force +smaller tool view tabs in IDEAl Mode + +By default &kdevelop; starts with large text-based tool tip tabs +around the work area. You may change this look to ⪚ save space in the +&kdevelop; configuration dialog (Settings +Configure KDevelop... User +Interface). +If you use an older &kdevelop; 3 version, this configuration dialog +may not be available. To change the toolview tabs display manually, place a + entry under the + tag in your +$KDEHOME/share/config/kdeveloprc configuration file as +follows: + + +: icons only +: text only (default) + +: icons and text + + + + + +Weird colored characters and/or display +style + +If you notice random colored letters everywhere (&ie; on tabs, on tool +bars, etc.) and the &kdevelop; window seemingly uses a wrong display style, +this may help: + + +In your +$KDEHOME/share/config/kdeveloprc +configuration file find the line containing +Style=Checked and remove +it. Then restart &kdevelop;. + + + +(This behaviour does sometimes occur after you left clicked a .ui file +in one of the file navigators and &kdevelop; did load +KUIViewer to show the &GUI; which was produced +from this file.) + + + + +Full +screen mode + +Select ViewFull-Screen +Mode from the menus or press +&Ctrl;&Shift;F. + + + + +Hide/Unhide +the menubar + +To hide the menubar select +SettingsShow +Menubar from the menus or press +&Ctrl;M. To redisplay the menubar only +&Ctrl;M is available. + + + + + +Projects + +Create New Project + +ProjectNew +Project... will start the &appwizard;. + + + + +Create a custom project + +There is no direct way to create a custom project (&ie; a project +which does use its own makefiles). Use +Project Import Existing +Project instead. Remember to set the appropriate +Project Type, labeled by an additional (Custom +Makefiles), in the dialog. + + + + +Use project options early + +Whenever you start a new project do not forget to set the +Project Project +Options... to your needs. + + + + + +Compilation + +Missing detail in compilation +messages + +If during compilations you notice some valuable information is missing +in the Messages Output View window, it may be that the +level of message detail is set too low. &RMB; click in the window and select +another detail level from the context menu. + + + + + + + + +<link linkend="automake-manager">&automanag;</link> + + +Create new files in a project + +Select the sub-project in the upper half of the &automanag;, then +&RMB; click in the lower half on the groups title you want to have the files +added and select Create New File.... + + + + +Add existing files to a project + +Select the sub-project in the upper half of the &automanag;, then +&RMB; click in the lower half on the groups title you want to have the files +added and select Add Existing Files.... + + + + +Remove a file from a project + +Select the sub-project in the upper half of the &automanag;, then in +the lower half open the groups list you want to have the file removed from, +&RMB; click on the file in this list and select +Remove. + + + + + +Compile/Make Problems + +Project does not build again after switching +to/from default target + +There is a problem with the &automake;/&autoconf; machinery. If + Project Build +Configuration provides to select from three build +directories: default, +optimized, and debug, +by all means stick to either the default +or the debug/optimized targets. + + +Once you configured your project with default it will no longer build +with debug or optimzed. + + +Once you configured your project with debug or optimzed it will no +longer build with default. + + + + + + +Wrong +autoconf version &etc; Error + +There are several error messages concerning too old versions of +autoconf &etc; prohibiting +configure to work properly. Run +autoreconf in the directory tree where the +configure.in files in question are. This command will +try to update the information in the &GNU; Build System files. See +man autoreconf for more information. + + + + + +Other Topics + +Configuration +Files used by &kdevelop; + +Usually you should not need to care, but this is very useful to know +in case something went wrong with your setup. + + + + + -- cgit v1.2.3