Discussion on "add to new target" wizard for CMake

[Milian Wolff]

Aleix Pol, 14.05.2010:
> On Thu, May 13, 2010 at 11:37 PM, Milian Wolff <mail at milianw.de> wrote:
> > please read: https://bugs.kde.org/show_bug.cgi?id=237535
> > 
> > I'd be interested in more feedback, what do you guys think? Why would
> > this be
> > a bad idea to take this burden off a developer?
> > 
> > And having different templates for "add to new target" would imo still
> > better
> > than designated wizards for "new app", "new unit test", "new class", "new
> > library", ... or what do you think?
> > 
> > How would we add something like "qt unit test", "kde unit test" only to
> > projects that actually use that? Has CMake the knowledge about that?
> > --
> > Milian Wolff
> > mail at milianw.de
> > http://milianw.de
> > 
> > --
> > KDevelop-devel mailing list
> > KDevelop-devel at kdevelop.org
> > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> 
> I think you're not talking about a "add to target" wizard but "add new
> target" wizard. Add to target is working already in the end.
> Add new target wizard would be needed for sure (I'm not sure if "add new
> target" or just some submenus like "add new..." executable/test/...)

Well the "add to target" should imo offer the user a way to create a new 
target. Either by context menu or somehow differently (more discoverable) - I 
don't really care :)

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100514/16209dec/attachment.sig>