[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: Test plugin
From:       David Nolden <zwabel () googlemail ! com>
Date:       2011-02-18 13:17:47
Message-ID: AANLkTinrCwKcEtzfS9HC1aWFEBBM=X0AF-EXAT2V-0J4 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


This shouldn't be moved back to kdevplatform/kdevelop so quickly.

It first has to be "finished", well-integrated, and maintained well for a
while.

Apart from that, the kdereview step can be skipped, because noone except for
a few kdevelop-devs will look at this anyway (if at all).

@Miha: You're welcome finishing up and polishing the plugin. My feeling was,
that it wasn't integrated in the UI very well, and was using some
inconsistent UI concepts that were used nowhere else in kdevelop (especially
in the tree-view).

Overall though, I'm not sure whether the KDevelop team is able to properly
maintain this beast, especially considering that the plugin deals with
ever-changing external programs.

Greetings, David

Am 18.02.2011 12:59 schrieb "Milian Wolff" <mail@milianw.de>:

On 02/18/11 10:50, Miha Čančula wrote:
>
> 2011/2/16 Miha Čančula<miha@noughmad.eu>
>
>> 2011/2/16 M...
imo:

- push patch to svn
- push svn to git playground
- polish
- kdereview
- kdevplatform (library) / kdevelop (ctest)




-- 
Milian Wolff
http://milianw.de

-- 
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
h...

[Attachment #5 (text/html)]

<p>This shouldn&#39;t be moved back to kdevplatform/kdevelop so quickly.</p>
<p>It first has to be &quot;finished&quot;, well-integrated, and maintained well for \
a while.</p> <p>Apart from that, the kdereview step can be skipped, because noone \
except for a few kdevelop-devs will look at this anyway (if at all).</p> <p>@Miha: \
You&#39;re welcome finishing up and polishing the plugin. My feeling was, that it \
wasn&#39;t integrated in the UI very well, and was using some inconsistent UI \
concepts that were used nowhere else in kdevelop (especially in the tree-view).</p>

<p>Overall though, I&#39;m not sure whether the KDevelop team is able to properly \
maintain this beast, especially considering that the plugin deals with ever-changing \
external programs.</p> <p>Greetings, David</p>
<p><blockquote type="cite">Am 18.02.2011 12:59 schrieb &quot;Milian Wolff&quot; \
&lt;<a href="mailto:mail@milianw.de">mail@milianw.de</a>&gt;:<br><br><p><font \
color="#500050">On 02/18/11 10:50, Miha Čančula wrote:<br>&gt;<br> &gt; 2011/2/16 \
Miha Čančula&lt;<a \
href="mailto:miha@noughmad.eu">miha@noughmad.eu</a>&gt;<br>&gt;<br>&gt;&gt; 2011/2/16 \
M...</font></p> imo:<br>
<br>
- push patch to svn<br>
- push svn to git playground<br>
- polish<br>
- kdereview<br>
- kdevplatform (library) / kdevelop (ctest)<p><font color="#500050"><br><br><br>-- \
<br>Milian Wolff<br><a href="http://milianw.de">http://milianw.de</a><br><br>-- \
<br>KDevelop-devel mailing list<br><a \
href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br> \
h...</font></p></blockquote></p>



-- 
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel


[prev in list] [next in list] [prev in thread] [next in thread]