Kdevelop4/Manual/Meet KDevelop: Difference between revisions

From KDE UserBase Wiki
No edit summary
m (formatting++)
Line 1: Line 1:
[http://www.KDevelop.org KDevelop] is a modern integrated development
[http://www.KDevelop.org KDevelop] is a modern integrated development environment (IDE) for C++ (and other languages) that is part of the [http://www.kde.org KDE desktop environment] project. As such it runs on Linux (even if you run one of the other desktops, such as GNOME) but it is also available for most other variants of Unix as well as on Windows.
environment (IDE) for C++ (and other languages) that is part of the
[http://www.kde.org KDE desktop environment] project. As such it runs on Linux
(even if you run one of the other desktops, such as GNOME) but it is
also available for most other variants of Unix as well as on Windows.


KDevelop offers all amenities of modern IDEs. For large projects and applications, the most important feature is that KDevelop
'''KDevelop''' offers all amenities of modern IDEs. For large projects and applications, the most important feature is that '''KDevelop''' <tt>understands C++</tt>: it parses the entire source base and remembers which classes have which member functions, where variables are defined, what their types are, and many other things about your code. For example, let's say one of your project's header files declares a class
'''understands C++''': it parses the entire source base and remembers which classes
 
have which member functions, where variables are defined, what their types are, and many other things about your code. For example, let's say one of your project's header files declares a class
{{Input|<syntaxhighlight lang="cpp">
<code><pre>
class Car {
class Car {
   // ...
   // ...
Line 14: Line 9:
     std::string get_color () const;
     std::string get_color () const;
};
};
</pre></code>
</syntaxhighlight>}}
 
and later on in your program you have
and later on in your program you have
<code><pre>
 
{{Input|<syntaxhighlight lang="cpp">
Car my_ride;
Car my_ride;
// ...do something with this variable...
// ...do something with this variable...
std::string color = my_ride.ge
std::string color = my_ride.ge
</pre></code>
</syntaxhighlight>}}
it will have remembered that <code>my_ride</code> in the last line is a variable of type
 
<code>Car</code> and offer you to complete <code>ge</code> as
it will have remembered that <code>my_ride</code> in the last line is a variable of type <code>Car</code> and offer you to complete <code>ge</code> as <code>get_color()</code> since this is the only member function of the <code>Car</code> class that starts like this. Instead of continuing to type you just hit enter to get the full word; this saves typing, avoids typos, and doesn't require you to remember the exact names of the hundreds or thousands of functions and classes that make up large projects.  
<code>get_color()</code> since this is the only member function of the
<code>Car</code> class that starts like this. Instead of continuing to type
you just hit enter to get the full word; this saves typing, avoids typos, and
doesn't require you to remember the exact names of the hundreds or thousands of functions and classes that make up large projects.  


As a second example, assume you have code like this:
As a second example, assume you have code like this:
<code><pre>
 
{{Input|<syntaxhighlight lang="cpp">
double foo ()
double foo ()
{
{
Line 41: Line 35:
   return var * var * var;
   return var * var * var;
}
}
</pre></code>
</syntaxhighlight>}}
 
If you hover the mouse over the symbol <code>var</code> in function <code>bar</code> you get the option to see all uses of this symbol. Clicking on it will only show you the uses of this variable in function <code>bar</code> because KDevelop understands that the variable <code>var</code> in function <code>foo</code> has nothing to do with it. Similarly, right clicking on the variable name allows you to rename the variable; doing so will only touch the variable in <code>bar</code> but not the one with the same name in <code>foo</code>.
If you hover the mouse over the symbol <code>var</code> in function <code>bar</code> you get the option to see all uses of this symbol. Clicking on it will only show you the uses of this variable in function <code>bar</code> because KDevelop understands that the variable <code>var</code> in function <code>foo</code> has nothing to do with it. Similarly, right clicking on the variable name allows you to rename the variable; doing so will only touch the variable in <code>bar</code> but not the one with the same name in <code>foo</code>.


But KDevelop is not just an intelligent code editor;
But '''KDevelop''' is not just an intelligent code editor; there are other things '''KDevelop''' does well. Obviously, it highlights the source code in different colors; it has a customizable indenter; it has an integrated interface to the GNU debugger '''gdb'''; it can show you the documentation for a function if you hover the mouse over a use of this function; it can deal with different kinds of build environments and compilers (e.g. with <code>make</code> and <code>cmake</code> based project), and many other neat things that are discussed in this manual.
there are other things KDevelop does well. Obviously, it highlights the source
 
code in different colors; it has a customizable indenter; it has an integrated
[[Category:Development]]
interface to the GNU debugger gdb; it can show you the documentation for a
function if you hover the mouse over a use of this function; it can deal with different kinds of build environments and compilers (e.g. with <code>make</code> and <code>cmake</code> based project), and many other
neat things that are discussed in this manual.

Revision as of 15:25, 14 May 2011

KDevelop is a modern integrated development environment (IDE) for C++ (and other languages) that is part of the KDE desktop environment project. As such it runs on Linux (even if you run one of the other desktops, such as GNOME) but it is also available for most other variants of Unix as well as on Windows.

KDevelop offers all amenities of modern IDEs. For large projects and applications, the most important feature is that KDevelop understands C++: it parses the entire source base and remembers which classes have which member functions, where variables are defined, what their types are, and many other things about your code. For example, let's say one of your project's header files declares a class

class Car {
  // ...
  public:
    std::string get_color () const;
};

and later on in your program you have

Car my_ride;
// ...do something with this variable...
std::string color = my_ride.ge

it will have remembered that my_ride in the last line is a variable of type Car and offer you to complete ge as get_color() since this is the only member function of the Car class that starts like this. Instead of continuing to type you just hit enter to get the full word; this saves typing, avoids typos, and doesn't require you to remember the exact names of the hundreds or thousands of functions and classes that make up large projects.

As a second example, assume you have code like this:

double foo ()
{
  double var = my_func();
  return var * var;
}

double bar ()
{
  double var = my_func();
  return var * var * var;
}

If you hover the mouse over the symbol var in function bar you get the option to see all uses of this symbol. Clicking on it will only show you the uses of this variable in function bar because KDevelop understands that the variable var in function foo has nothing to do with it. Similarly, right clicking on the variable name allows you to rename the variable; doing so will only touch the variable in bar but not the one with the same name in foo.

But KDevelop is not just an intelligent code editor; there are other things KDevelop does well. Obviously, it highlights the source code in different colors; it has a customizable indenter; it has an integrated interface to the GNU debugger gdb; it can show you the documentation for a function if you hover the mouse over a use of this function; it can deal with different kinds of build environments and compilers (e.g. with make and cmake based project), and many other neat things that are discussed in this manual.