KDevelop4/TipsAndTricks: Difference between revisions

From KDE UserBase Wiki
(Created page with "= Tips And Tricks = === Code Completion === While you have automatic code completion, requesting it manually is often a very good idea. Press <tt>Ctrl + Space</tt> and you'll ge...")
 
m (separate bold italic because from this point, message is rendered all in bold in the translation interface)
 
(11 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Tips And Tricks =
<languages />
=== Code Completion ===
<translate>
== Tips And Tricks == <!--T:1-->


While you have automatic code completion, requesting it manually is often a very good idea. Press <tt>Ctrl + Space</tt> and you'll get a detailed code completion list. Navigate with the arrow buttons (Up/Down) and press (and keep pressed) Alt to show documentation of the focused item. Press Enter to insert the item.
=== Code Completion === <!--T:2-->


=== C++ Type Assistant ===
<!--T:3-->
While you have automatic code completion, requesting it manually is often a very good idea. Press <keycap>Ctrl + Space</keycap> and you'll get a detailed code completion list. Navigate with the arrow buttons (<keycap>Up</keycap>/<keycap>Down</keycap>) and press (and keep pressed) <keycap>Alt</keycap> to show documentation of the focused item. Press <keycap>Enter</keycap> to insert the item.


=== C++ Type Assistant === <!--T:4-->
<!--T:5-->
Assume you have something similar to this:
Assume you have something similar to this:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
#include <vector>
#include <vector>
void myFunc(const std::vector<int>& v) {
void myFunc(const std::vector<int>& v) {


}
}
</pre>
</syntaxhighlight>}}
 
<translate>
<!--T:6-->
Now you want to iterate over the contents, instead of writing the type of the iterator, you just write:
Now you want to iterate over the contents, instead of writing the type of the iterator, you just write:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
   it = vector.begin();
   it = vector.begin();
</pre>
</syntaxhighlight>}}
 
<translate>
Now wait a second until the assistant pops up at the bottom of the editor. Press <tt>Alt + 1</tt> to execute the assistant and you end up with:
<!--T:7-->
 
Now wait a second until the assistant pops up at the bottom of the editor. Press <keycap>Alt + 1</keycap> to execute the assistant and you end up with:
<pre>
</translate>
{{Input|<syntaxhighlight lang="cpp">
   std::vector< int >::iterator it = v.begin();
   std::vector< int >::iterator it = v.begin();
</pre>
</syntaxhighlight>}}
 
<translate>
Nice, lots of time saved :) And this should work with most/all expressions, as long as the right side can be evaluated, you should get an assistant that adds the correct type to the left side.
<!--T:8-->
Nice, lots of time saved. {{Smiley}} And this should work with most/all expressions, as long as the right side can be evaluated, you should get an assistant that adds the correct type to the left side.


=== C++ Signature Assistant ===
=== C++ Signature Assistant === <!--T:9-->


<!--T:10-->
Example code:
Example code:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
class foo {
class foo {
   int bar();
   int bar();
Line 41: Line 50:
{
{
}
}
</pre>
</syntaxhighlight>}}
 
<translate>
Now try the following things and after each step wait shortly and apply the assistant that pops up at the bottom of the editor with <tt>Alt + 1</tt>:
<!--T:11-->
Now try the following things and after each step wait shortly and apply the assistant that pops up at the bottom of the editor with <keycap>Alt + 1</keycap>:


# add a parameter, e.g. <tt>int foo</tt> to either signature in the definition or the declaration.
<!--T:12-->
# make one signature <tt>const</tt>
# add a parameter, e.g. <code>int foo</code> to either signature in the definition or the declaration.
# make one signature <code>const</code>
# change a type of a parameter
# change a type of a parameter
# remove a parameter
# remove a parameter


<!--T:13-->
Again, a very handy time saver!
Again, a very handy time saver!


=== C++ Missing Declaration Assistant ===
=== C++ Missing Declaration Assistant === <!--T:14-->


<!--T:15-->
Example Code:
Example Code:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
class foo {
class foo {
   int bar();
   int bar();
Line 64: Line 77:
{
{
}
}
</pre>
</syntaxhighlight>}}
 
<translate>
<!--T:16-->
Now write this into the implementation of bar:
Now write this into the implementation of bar:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
   myVar = 1;
   myVar = 1;
</pre>
</syntaxhighlight>}}
 
<translate>
<!--T:17-->
You should get an assistant that offers you three options:
You should get an assistant that offers you three options:


# declare local <tt>int myVar</tt> (see type assistant above)
<!--T:18-->
# declare public <tt>int myVar</tt>, adds the declaration to the class body
# declare local <code>int myVar</code> (see type assistant above)
# declare private <tt>int myVar</tt>, same as above, but in private section.
# declare public <code>int myVar</code>, adds the declaration to the class body
# declare private <code>int myVar</code>, same as above, but in private section.


<!--T:19-->
This even works for functions:
This even works for functions:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
class foo {
class foo {
};
};
Line 88: Line 105:


}
}
</pre>
</syntaxhighlight>}}
 
<translate>
Now write this below <tt>foo f;</tt>:
<!--T:20-->
 
Now write this below <code>foo f;</code>:
<pre>
</translate>
{{Input|<syntaxhighlight lang="cpp">
   f.someFunction(1, true, "asdf");
   f.someFunction(1, true, "asdf");
</pre>
</syntaxhighlight>}}
 
<translate>
<!--T:21-->
The assistant now offers you to declare that function, you'll end up with:
The assistant now offers you to declare that function, you'll end up with:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
class foo {
class foo {
public:
public:
   void someFunction( int arg1, bool arg2, const char* arg3 );
   void someFunction( int arg1, bool arg2, const char* arg3 );
};
};
</pre>
</syntaxhighlight>}}
 
<translate>
Cool :)
<!--T:22-->
Cool {{Smiley}}.




=== Overload Helper ===
=== Overload Helper === <!--T:23-->


<!--T:24-->
Example code:
Example code:
 
</translate>
<pre>
{{Input|<syntaxhighlight lang="cpp">
class A {
class A {
public:
public:
Line 120: Line 141:


};
};
</pre>
</syntaxhighlight>}}
 
<translate>
Inside the class body of <tt>B</tt> press <tt>Ctrl + Space</tt> to bring up code completion. You should notice an item to overload <tt>foo(int something);</tt>. Execute it with enter and you should get:
<!--T:25-->
 
Inside the class body of <code>B</code> press <keycap>Ctrl + Space</keycap> to bring up code completion. You should notice an item to overload <code>foo(int something);</code>. Execute it with <keycap>Enter</keycap> and you should get:
<pre>
</translate>
{{Input|<syntaxhighlight lang="cpp">
class B : public A {
class B : public A {
public:
public:
   virtual A* foo(int something);
   virtual A* foo(int something);
};
};
</pre>
</syntaxhighlight>}}
 
<translate>
Cool :)
<!--T:26-->
Cool {{Smiley}}.


=== Implementation Helper ===
=== Implementation Helper === <!--T:27-->


Continue where we left of in the Overload Helper:
<!--T:28-->
 
Continue where we left of in the '''Overload Helper''':
<pre>
</translate>
{{Input|<syntaxhighlight lang="cpp">
class B : public A {
class B : public A {
public:
public:
   virtual A* foo(int something);
   virtual A* foo(int something);
};
};
</pre>
</syntaxhighlight>}}
 
<translate>
Place your cursor below the class context, request code completion with <tt>Ctrl + Space</tt>, you should notice an item to implement <tt>B::foo(int something);</tt>. Execute it with enter and you should get:
<!--T:29-->
 
Place your cursor below the class context, request code completion with <keycap>Ctrl + Space</keycap>, you should notice an item to implement <code>B::foo(int something);</code>. Execute it with <keycap>Enter</keycap> and you should get:
<pre>
</translate>
{{Input|<syntaxhighlight lang="cpp">
A* B::foo(int something)
A* B::foo(int something)
{
{
   A::foo(something);
   A::foo(something);
}
}
</pre>
</syntaxhighlight>}}
<translate>
<!--T:30-->
Awesome {{Smiley}}.


Awesome :)
=== Quick Open === <!--T:31-->


=== Quick Open ===
<!--T:32-->
<menuchoice>Quick Open</menuchoice> is probably one of ''the'' features in '''KDevelop''' that increases productivity:


Quick Open is probably one of ''the'' features in KDevelop that increases productivity:
<!--T:33-->
* Quick Open Files
Press <keycap>Ctrl + Alt + O</keycap> and type part of a filepath, press <keycap>Enter</keycap> and the selected file gets opened. The search is separated by forward slashes, i.e. you can write this: <code>/a/.cpp</code> and the list will only show paths that have a folder starting with <code>a</code> and files that end on <code>.cpp</code>. Try it out.


* Quick Open Files
<!--T:34-->
Press <tt>Ctrl + Alt + O</tt> and type part of a filepath, press return and the selected file gets opened. The search is separated by forward slashes, i.e. you can write this: <tt>/a/.cpp</tt> and the list will only show paths that have a folder starting with <tt>a</tt> and files that end on <tt>.cpp</tt>. Try it out.
* Quick Open Classes
* Quick Open Classes
<tt>Ctrl + Alt + C</tt> and input (parts) of the qualified class identifier, press return and jump to the declaration of that class.
<keycap>Ctrl + Alt + C</keycap> and input (parts) of the qualified class identifier, press <keycap>Return</keycap> and jump to the declaration of that class.
 
<!--T:35-->
Also make sure to explore the other advanced features in <menuchoice>Quick Open</menuchoice>.
 
=== Outline === <!--T:36-->
 
<!--T:37-->
Similar to quick open, pressing <keycap>Ctrl + Alt + N</keycap> gives you an outline of the current document with the ability to search for an identifier and quickly jump to its declaration.


Also make sure to explore the other advanced features in Quick Open.
=== Context Browsing === <!--T:38-->


=== Outline ===
<!--T:39-->
Hover a use, declaration or definition and you'll get a popup with information about it. You can also move your cursor in there and press (and keep pressed) the <keycap>Alt</keycap> button to show that popup without using the mouse. Use the arrow keys to navigate between the links in the popup, use <keycap>Enter</keycap> to jump to the destination of a link.


Similar to quick open, pressing <tt>Ctrl + Alt + N</tt> gives you an outline of the current document with the ability to search for an identifier and quickly jump to its declaration.
<!--T:40-->
When inside a use, press <keycap>Meta + Left</keycap> or <keycap>Meta + Right</keycap> to jump to the previous/next use. Press <keycap>Ctrl + .</keycap> or <keycap>Ctrl + ,</keycap> to jump to the declaration or definition of the symbol under the cursor. Alternatively click on a symbol with <keycap>Ctrl</keycap> button pressed to do the same.


=== Context Browsing ===
<!--T:41-->
Also take a look at the <menuchoice>Navigation</menuchoice> menu and it's various shortcuts. Context browsing is awesome!


Hover a use, declaration or definition and you'll get a popup with information about it. You can also move your cursor in there and press (and keep pressed) the <tt>Alt</tt> button to show that popup without using the mouse. Use the arrow keys to navigate between the links in the popup, use enter to jump to the destination of a link.
=== How to work with autotools: automake, autoconf and libtool === <!--T:42-->


When inside a use, press <tt>Meta + Left</tt> or <tt>Meta + Right</tt> to jump to the previous/next use. Press <tt>Ctrl + .</tt> or <tt>Ctrl + ,</tt> to jump to the declaration or definition of the symbol under the cursor. Alternatively click on a symbol with <tt>Ctrl</tt> button pressed to do the same.
<!--T:43-->
'''KDevelop 4''' does not support very well the autotools. I suggest using [[Special:myLanguage/Konsole|Konsole]] to run configure scripts to build makefile. The custom makefile support works quite well. I suggest using separate building folder (say <tt>project/build</tt>).


Also take a look at the Navigation menu and it's various shortcuts. Context browsing is awesome!
<!--T:44-->
After the custom makefiles are in place (say in <tt>build</tt>-directory) one can add that to build list by clicking the {{Plus}} button on lower left corner '''Project selection''' while build directory is selected. This causes command '''make''' to be run when pressing <menuchoice>Build</menuchoice>. One can also directly run say '''make install''' on specific directory by right clicking the folder and selecting '''make install'''. This is nice if you have lots of projects in working set.


=== How to work with autotools: automake, autoconf and libtool ===
<!--T:45-->
'''Libtool''' also causes problems if you try to debug application that has been linked with '''libtool''': the program that you see in for example <tt>src/bin/program</tt> is not the executable, but a script that handles the libraries.


Kdevelop4 does not support very well the autotools. I suggest using konsole to run configure scripts to build makefile. The custom makefile support works quite well. I suggest using separate building folder (say project/build).
<!--T:46-->
Problem is properly solved in console by running {{Input|1=libtool --mode=execute'' '''<dst_binary>''' ''}} but at least currently '''KDevelop4''' does not work good (at all) with other console than default. I have been stuck of using the real binary (found usually from  <tt>src/bin/.libs/<exec></tt>) that might use wrong libraries, so do '''make install''' before every run.


After the custom makefiles are in place (say in 'build'-directory) one can add that to build list by clicking '+' button on lower left corner 'Project selection' while build directory is selected. This causes command 'make' to be run when pressing 'Build'. One can also directly run say 'make install' on specific directory by right clicking the folder and selecting 'make install'. This is nice if you have lots of projects in working set.
=== KDE Classes Documentation === <!--T:47-->


Libtool also causes problems if you try to debug application that has been linked with libtool: the program that see in for example src/bin/program is not the executable, but a script that handles the libraries.  
<!--T:48-->
Using the '''Qt Documentation''' plugin you may integrate KDE documentation along with Qt documentation. Point your browser at [http://api.kde.org/ KDE API Reference] and download the desired <tt>.qch</tt> file (not all modules provide one). Then configure the '''Qt Documentation''' plugin by adding the downloaded files. That's it! Whenever you hover a KDE class you can see a link <menuchoice>Show documentation for KFooClass</menuchoice> which points to KFooClass documentation. Enjoy.


Problem is properly solved in console by running 'libtool --mode=execute <dst_binary>' but at least currently kdevelop4 does not work good (at all) with other console than default i have been stuck of using the real binary (found usually from  src/bin/.libs/<exec> ) that might use wrong libraries, so do 'make install' before every run.
<!--T:49-->
[[Category:Development]]
</translate>

Latest revision as of 11:42, 30 July 2018

Tips And Tricks

Code Completion

While you have automatic code completion, requesting it manually is often a very good idea. Press Ctrl + Space and you'll get a detailed code completion list. Navigate with the arrow buttons (Up/Down) and press (and keep pressed) Alt to show documentation of the focused item. Press Enter to insert the item.

C++ Type Assistant

Assume you have something similar to this:

#include <vector>
void myFunc(const std::vector<int>& v) {

}

Now you want to iterate over the contents, instead of writing the type of the iterator, you just write:

  it = vector.begin();

Now wait a second until the assistant pops up at the bottom of the editor. Press Alt + 1 to execute the assistant and you end up with:

  std::vector< int >::iterator it = v.begin();

Nice, lots of time saved. And this should work with most/all expressions, as long as the right side can be evaluated, you should get an assistant that adds the correct type to the left side.

C++ Signature Assistant

Example code:

class foo {
  int bar();
};

int foo::bar()
{
}

Now try the following things and after each step wait shortly and apply the assistant that pops up at the bottom of the editor with Alt + 1:

  1. add a parameter, e.g. int foo to either signature in the definition or the declaration.
  2. make one signature const
  3. change a type of a parameter
  4. remove a parameter

Again, a very handy time saver!

C++ Missing Declaration Assistant

Example Code:

class foo {
  int bar();
};

foo::bar()
{
}

Now write this into the implementation of bar:

  myVar = 1;

You should get an assistant that offers you three options:

  1. declare local int myVar (see type assistant above)
  2. declare public int myVar, adds the declaration to the class body
  3. declare private int myVar, same as above, but in private section.

This even works for functions:

class foo {
};

int main() {
  foo f;

}

Now write this below foo f;:

  f.someFunction(1, true, "asdf");

The assistant now offers you to declare that function, you'll end up with:

class foo {
public:
  void someFunction( int arg1, bool arg2, const char* arg3 );
};

Cool .


Overload Helper

Example code:

class A {
public:
  virtual A* foo(int something){}
};
class B : public A {

};

Inside the class body of B press Ctrl + Space to bring up code completion. You should notice an item to overload foo(int something);. Execute it with Enter and you should get:

class B : public A {
public:
  virtual A* foo(int something);
};

Cool .

Implementation Helper

Continue where we left of in the Overload Helper:

class B : public A {
public:
  virtual A* foo(int something);
};

Place your cursor below the class context, request code completion with Ctrl + Space, you should notice an item to implement B::foo(int something);. Execute it with Enter and you should get:

A* B::foo(int something)
{
  A::foo(something);
}

Awesome .

Quick Open

Quick Open is probably one of the features in KDevelop that increases productivity:

  • Quick Open Files

Press Ctrl + Alt + O and type part of a filepath, press Enter and the selected file gets opened. The search is separated by forward slashes, i.e. you can write this: /a/.cpp and the list will only show paths that have a folder starting with a and files that end on .cpp. Try it out.

  • Quick Open Classes

Ctrl + Alt + C and input (parts) of the qualified class identifier, press Return and jump to the declaration of that class.

Also make sure to explore the other advanced features in Quick Open.

Outline

Similar to quick open, pressing Ctrl + Alt + N gives you an outline of the current document with the ability to search for an identifier and quickly jump to its declaration.

Context Browsing

Hover a use, declaration or definition and you'll get a popup with information about it. You can also move your cursor in there and press (and keep pressed) the Alt button to show that popup without using the mouse. Use the arrow keys to navigate between the links in the popup, use Enter to jump to the destination of a link.

When inside a use, press Meta + Left or Meta + Right to jump to the previous/next use. Press Ctrl + . or Ctrl + , to jump to the declaration or definition of the symbol under the cursor. Alternatively click on a symbol with Ctrl button pressed to do the same.

Also take a look at the Navigation menu and it's various shortcuts. Context browsing is awesome!

How to work with autotools: automake, autoconf and libtool

KDevelop 4 does not support very well the autotools. I suggest using Konsole to run configure scripts to build makefile. The custom makefile support works quite well. I suggest using separate building folder (say project/build).

After the custom makefiles are in place (say in build-directory) one can add that to build list by clicking the button on lower left corner Project selection while build directory is selected. This causes command make to be run when pressing Build. One can also directly run say make install on specific directory by right clicking the folder and selecting make install. This is nice if you have lots of projects in working set.

Libtool also causes problems if you try to debug application that has been linked with libtool: the program that you see in for example src/bin/program is not the executable, but a script that handles the libraries.

Problem is properly solved in console by running

libtool --mode=execute <dst_binary> 

but at least currently KDevelop4 does not work good (at all) with other console than default. I have been stuck of using the real binary (found usually from src/bin/.libs/<exec>) that might use wrong libraries, so do make install before every run.

KDE Classes Documentation

Using the Qt Documentation plugin you may integrate KDE documentation along with Qt documentation. Point your browser at KDE API Reference and download the desired .qch file (not all modules provide one). Then configure the Qt Documentation plugin by adding the downloaded files. That's it! Whenever you hover a KDE class you can see a link Show documentation for KFooClass which points to KFooClass documentation. Enjoy.