Members of the KDE Community are recommended to subscribe to the kde-community mailing list at https://mail.kde.org/mailman/listinfo/kde-community to allow them to participate in important discussions and receive other important announcements

  1. 08 Jan, 2020 1 commit
  2. 13 Sep, 2017 2 commits
  3. 07 Aug, 2017 1 commit
  4. 12 May, 2017 1 commit
    • Friedrich W. H. Kossebau's avatar
      Default to disabled debug log on Q_LOGGING_CATEGORY calls · 256c5f4c
      Friedrich W. H. Kossebau authored
      This removes the need to call QLoggingCategory::setFilterRules()
      in the program code to default to disabled debug type log
      without any other settings.
      The latter has disadvantages, as it shadows any settings done
      in qtlogging.ini config files by the user
      (e.g. via kdebugsettings), thus enabling runtime control only
      via QT_LOGGING_CONF/QT_LOGGING_RULES, which is not that
      comfortable with lots of categories.
      
      Also use ECMQtDeclareLoggingCategory for less manual code
      
      While there can be some inconsistency with the default disabled
      log categories by ECMQtDeclareLoggingCategory, which
      switched to QtInfoMsg for ECM 5.26 (when KF5 5.26 has Qt 5.5
      as min dep, which is the Qt version QtInfoMsg was added),
      current KDevPlatform code has Qt 5.4 as minimum version and
      thus also does not use qCInfo, so KDevPlatform behaviour should
      be the same across used Qt versions.
      256c5f4c
  5. 09 Jan, 2016 2 commits
  6. 17 Dec, 2015 1 commit
  7. 04 Dec, 2014 1 commit
  8. 11 Nov, 2014 1 commit
    • Milian Wolff's avatar
      Refactor the custom defines and includes plugin. · eb06a177
      Milian Wolff authored
      The compiler provider is not a plugin anymore, but a library that
      is used in multiple places. In KF5, when the KCM is also not a
      plugin anymore, we can merge all three together into one single
      plugin .so.
      
      For now, this move already simplifies the logic tremendously and
      removes a lot of boilerplate code that was required to access
      the CompilerProvider/SettingsManager from various places.
      
      Note that the distinction between CompilerProvider and SettingsManager
      is also pretty artificial. I plan to merge the two classes together
      and futher clean up the code then. There is a one-to-one relation ship
      after all between these two classes.
      
      In addition to the above, I cleaned up the code wherever I noticed
      any opportunity for that. There are probably more places for that.
      
      CCMAIL: kalinichev.so.0@gmail.com
      eb06a177
  9. 18 Sep, 2014 1 commit
  10. 24 Aug, 2014 1 commit
  11. 12 Aug, 2014 1 commit
  12. 09 Jul, 2014 1 commit
  13. 22 Jun, 2014 3 commits
  14. 04 Jun, 2014 7 commits