< Events‎ | Akademy/2010
Revision as of 14:06, 5 July 2010 by Dymo (talk | contribs)

Events/Akademy/2010/KDevelopBoF

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This workshop is for advanced KDevelop3/Kate/Emacs/Vi/Eclipse/QtCreator/etc. users who would like to get deep and detailed information about KDevelop 4 first hands.

Topics covered are:

  • usage patterns
    • kdevelop as improved kate
    • kdevelop as 1-project ide
    • kdevelop as an ultimate work tool - many projects, sessions, etc.
    • which usage patterns are best supported right now and why
  • what are sessions: intended use, scope, limitations
  • projects
    • idea behind multiple projects
    • multiple projects and buildiing
    • multiple projects and other plugins
  • what happens behind the hood in UI
    • what are areas: intended use, limitations
    • what are workingsets: intended use, limitations
    • concept of views, saving/closing views, views and areas
  • what happens behind the hood in c++ support
    • how includes are found
              - when automatic resolver is used
              - which buildsystems and when can do
    • how and when completion, assistant hints, refactoring etc. work
    • what is duchain and what it does
    • how to tune performance
  • how to create and use snippets
  • how to customize the IDE
    • customizing editor (modelines, kateconfig)
    • creating a custom shortcut scheme
    • kdeveloprc - what's there, what to change
    • quick overview of the extension architecture
    • writing language support plugins: very brief intro
  • best workflows
    • quickopen instead of class view
    • navigation explained
      • what is context, what context navigation do
      • all other navigation features
      • tab/notab view management
  • Q/A

This page was last edited on 5 July 2010, at 14:08. Content is available under Creative Commons License SA 4.0 unless otherwise noted.