KDevelop4/Tips og tricks

    From KDE UserBase Wiki
    Revision as of 11:02, 12 August 2012 by Claus chr (talk | contribs) (Importing a new version from external source)

    Tips og tricks

    Kodefuldførelse

    Selvom du har automatisk kodefuldførelse er det ofte en god ide at starte det manuelt. Tast Ctrl + Mellemrum, så får du en detaljeret liste til kodefuldførelse. Navigér med piletasterne (Op og Ned) og hold Alt-tasten nedtrykket for at vise dokumentationen for det punkt, der har fokus. Tast Enter for at indsætte punktet.

    Assistent til C++-typer

    Antag at du har noget i retning af:

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

    Nu ønsker du at iterere over indholdet, så istedet for at skrive iteratorens type skriver du blot:

      it = vector.begin();
    

    Vent nu et øjeblik indtil assistenten dukker op nederst i editoren. Tast Alt + 1 for at udføre assistenten, så ender du med:

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

    Rart, megen tid sparet. Og dette skulle virke med de fleste eller alle udtryk, når blot højresiden kan evalueres skulle du få en assistent, der tilføjer den rigtige type på venstre side.

    Assistent til C++-signaturer

    Eksempel kode:

    class foo {
      int bar();
    };
    
    int foo::bar()
    {
    }
    

    Prøv nu de følgende punkter; vent et kort øjeblik efter hver skridt og anvend den assistent, der dukker op nederst i editoren ved at taste Alt + 1:

    1. tilføj en parameter, fx. int foo enten til signaturen af definitionen eller erklæringen.
    2. gør en signatur const
    3. lav en parameters type om
    4. fjern en parameter

    Igen, en meget praktisk og tidsbesparende!

    Assistent til manglende erklæringer i C++

    Eksempelkode:

    class foo {
      int bar();
    };
    
    foo::bar()
    {
    }
    

    Skriv nu dette i implementationen af bar:

      myVar = 1;
    

    Du skulle nu få en assistent, som giver dig tre valgmuligheder:

    1. erklær en lokal int myVar (se typeassistenten ovenfor)
    2. erklær en public int myVar, som tilføjer erklæringen til klasses
    3. erklær en private int myVar, som gør det samme som ovenstående, men i afsnittet private.

    Dette virker også for funktioner:

    class foo {
    };
    
    int main() {
      foo f;
    
    }
    

    Skriv nu dette under foo f;:

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

    Assistenten tilbyder dig nu at erklære funktionen; du vil få følgende:

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

    Cool .


    Hjælp til overloading

    Eksempel kode:

    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

    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).

    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.

    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.

    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.