D14288: Initial version of Clazy analyzer plugin

Anton Anikin noreply at phabricator.kde.org
Mon Jul 23 11:20:40 BST 2018


antonanikin added a comment.


  In D14288#296131 <https://phabricator.kde.org/D14288#296131>, @kossebau wrote:
  
  > And one more request (from me personally, no idea about current kdevelop maintainers' POV): could you consider doing the UI in ui files?
  >
  > Myself used to write all QWidget UI setup also directly in code, though big projects like also KDevelop have teached me that it improves maintainability if concerns are separated where possible, including moving the declaration of (static) UI into the prepared infrastructure, i.e. the UI files. While it adds to build time, it does not add that much to runtime/codesize, if at all.
  >
  > And even if done for consistency with code of (most) existing plugins :)
  
  
  Ok. I will convert `GlobalConfigPage` and `ProjectConfigPage` into `.ui`-based widgets. I also prefer "hand-written" UI but you are right about better maintainability of `.ui` files for big community projects.
  
  `ChecksWidget` is special non-static widget for `KConfig` so I think it should not be changed. What are you think about `CommandLineWidget`? It simple but I also can convert it into `.ui`-form if this will be better in maintainability perspective.

REPOSITORY
  R32 KDevelop

REVISION DETAIL
  https://phabricator.kde.org/D14288

To: antonanikin, #kdevelop
Cc: kossebau, kdevelop-devel, antismap, iodelay, vbspam, njensen, geetamc, Pilzschaf, akshaydeo, surgenight, arrowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20180723/14f5e6c1/attachment-0001.html>


More information about the KDevelop-devel mailing list