Re: [Qt-creator] Submitting a plugin that does not follow the coding style

2015-06-01 Thread Carel Combrink
Dear Oswald,

Regarding this issue, is there a quick way to do a dry run on a plugin to
see how much a plugin conforms (or does not conform) to the coding style?

Regards,

-- Check out my SpellChecker Plugin for Qt Creator @
https://github.com/CJCombrink/SpellChecker-Plugin


On Mon, Jun 1, 2015 at 10:40 AM, Oswald Buddenhagen 
oswald.buddenha...@theqtcompany.com wrote:

 On Sat, May 30, 2015 at 05:40:36PM +0200, Jochen Becher wrote:
  (1) A static library that implements the modelling backend (entities,
  persistence, diagrams, UI components)
 
  (2) A plugin that links the modelling backend with QtCreator (mostly a
  new editor for diagrams)
 
  (3) A tool to export diagrams to image files
 
  (4) A patch of projectexplorer supporting more dragdrop
 

  I can update (2) and (3) following the coding style guide ((4) already
  does).
 
 yes, please.

  But (1) is pretty large and I want to avoid all those changes. Is that
  acceptable if I submit the library in src/libs/3rdparty?
 
 size as such isn't an argument (the process can be mostly automated).
 but if you are indeed maintaining that library independently of
 qtcreator's existence, then it's by definition 3rdparty.
 ___
 Qt-creator mailing list
 Qt-creator@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/qt-creator

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator


Re: [Qt-creator] Submitting a plugin that does not follow the coding style

2015-06-01 Thread Oswald Buddenhagen
On Sat, May 30, 2015 at 05:40:36PM +0200, Jochen Becher wrote:
 (1) A static library that implements the modelling backend (entities,
 persistence, diagrams, UI components)
 
 (2) A plugin that links the modelling backend with QtCreator (mostly a
 new editor for diagrams)
 
 (3) A tool to export diagrams to image files
 
 (4) A patch of projectexplorer supporting more dragdrop
 

 I can update (2) and (3) following the coding style guide ((4) already
 does).

yes, please.

 But (1) is pretty large and I want to avoid all those changes. Is that
 acceptable if I submit the library in src/libs/3rdparty?
 
size as such isn't an argument (the process can be mostly automated).
but if you are indeed maintaining that library independently of
qtcreator's existence, then it's by definition 3rdparty.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator