1. 05 Oct, 2017 1 commit
  2. 04 Oct, 2017 6 commits
    • Friedrich W. H. Kossebau's avatar
      Add missing X-KDevelop-Category entries to plugins' metadata · 864d6dcf
      Friedrich W. H. Kossebau authored
      This entry is defined as required (cmp. IPlugin API docs) with values either
      "Global" or "Project". Having it not set and thus being treated with a value
      of empty string results e.g. in plugins not being loaded or unloaded after
      the user enabled or disabled plugins in the settings.
      Reviewers: #kdevelop, brauch
      Reviewed By: #kdevelop, brauch
      Subscribers: brauch, kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D8139
    • Friedrich W. H. Kossebau's avatar
      Always create Documentation tool view, fix it to work with no providers · 781bb47c
      Friedrich W. H. Kossebau authored
      Creating the Documentation tool view at DocumentationController
      initialization time only if the list returned by documentationProviders() is
      non-empty has some flaws:
      1) The QtHelp plugin delays initialization to after reaching the event loop.
      So if it is the only documentation provider (provider) plugin activated, it
      will return 0 providers in the beginning.
      2) It ignores the option that users can enable another documentation provider plugin
      at runtime.
      3) There is also no code for removing the tool view in case the user
      disables any documentation providers at runtime.
      4) It ignores the option of plugins like the QtHelp one allowing the user to
      disable any documentation providers at runtime.
      This patch always creates the toolview instead of magically creating/removing it
      automatically based on documentation provider availability and leaves it to
      the user to add or remove it as they prefer.
      It also prepares the Documentation tool view to properly handle the case of
      no documentation providers available (done in a way to keep the current public
      BUG: 383875
      FIXED-IN: 5.2.0
      Reviewers: #kdevelop, apol
      Reviewed By: #kdevelop, apol
      Subscribers: kdevelop-devel
      Differential Revision: https://phabricator.kde.org/D8140
    • Aleix Pol Gonzalez's avatar
      Make cmake-server output forwarding a qCDebug · b1bcf4dd
      Aleix Pol Gonzalez authored
      CCBUG: 384724
    • Kevin Funk's avatar
      Revert "cmake: Degrade warning to normal debug msg" · 73f2759f
      Kevin Funk authored
      Note: We should explicitly state the "ignored" messages in the code
      instead. Let's keep the warning for unknown + unhandled messages.
      Also, the 'progress' message is already handled properly now, so this
      unhandled message type is gone already.
      CCBUG: 384724
      This reverts commit 7c4e09c2.
    • Kevin Funk's avatar
      cmake: Remove spammy debug messages · a1869f3a
      Kevin Funk authored
      This wasn't intended to be committed in the first place
      BUG: 384724
    • Kevin Funk's avatar
      cmake: Degrade warning to normal debug msg · 7c4e09c2
      Kevin Funk authored
      Patch by RJVB, thanks!
      BUG: 384724
      FIXED-IN: 5.2.0
  3. 03 Oct, 2017 1 commit
  4. 02 Oct, 2017 1 commit
  5. 01 Oct, 2017 3 commits
    • Friedrich W. H. Kossebau's avatar
      Ensure setting of custom app language is seen on start-up · 5cba8f47
      Friedrich W. H. Kossebau authored
      The custom language setting is read in from the config in a method hooked
      up to the QApp instance creation (see KXMLGUI's kswitchlanguagedialog_p.cpp
      sources), which deploys the custom setting by setting the LANGUAGE env var.
      For this to work, the respective init code of KLocalizedString static
      data, which contains the set of languages as read from the env vars,
      needs to be only triggered after the QApp instance creation.
      Which includes calling KLocalizedString::setApplicationDomain() only then,
      which this patch cares for.
    • René J.V. Bertin's avatar
      complete the optional import timing · 48487d5d
      René J.V. Bertin authored
      This prints the timing needed for dirwatcher deletion when TIME_IMPORT_JOB
      is defined (see filemanagerlistjob.cpp). Output is only generated when
      a dirwatcher was actually deleted (= once per project).
    • Script Kiddy's avatar
      SVN_SILENT made messages (.desktop file) - always resolve ours · 44de6d6b
      Script Kiddy authored
      In case of conflict in i18n, keep the version of the branch "ours"
      To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
  6. 29 Sep, 2017 17 commits
  7. 28 Sep, 2017 9 commits
  8. 25 Sep, 2017 2 commits
    • Friedrich W. H. Kossebau's avatar
    • René J.V. Bertin's avatar
      Document how to determine which optional dependencies are used (e.g. QtWebKit... · 69548771
      René J.V. Bertin authored
      Document how to determine which optional dependencies are used (e.g. QtWebKit instead of QtWebEngine
      As long as QtWebKit remains a supported option for documentation rendering users might want an option to build KDevelop against that library even if QWE is present on their system.
      KDevelop uses enough resources of its own, so an option to avoid using the additional resource-hungry QWE is very welcome (after all, many will probably already have a chrome-based browser running).
      This patch is the simplest possible implementation, and doesn't advertise itself by creating an option variable in the toplevel CMake file. I'd be happy to add that possibility though.
      Test Plan: It would be nice if CMake's summary printed a list of optional dependencies that were disabled explicitly.
      Reviewers: #kdevelop, apol, kfunk
      Reviewed By: #kdevelop, kfunk
      Subscribers: kfunk, apol, kdevelop-devel
      Tags: #kdevelop
      Differential Revision: https://phabricator.kde.org/D7950