[kdevplatform] a5caf03: Make it possible to add pre-configured launch conf

[Milian Wolff]

On Friday 22 October 2010 09:03:05 Andreas Pakulat wrote:
> On 21.10.10 21:51:02, Aleix Pol wrote:
> > diff --git a/plugins/execute/nativeappconfig.cpp
> > b/plugins/execute/nativeappconfig.cpp index 5edb957..7aadbfc 100644
> > --- a/plugins/execute/nativeappconfig.cpp
> > +++ b/plugins/execute/nativeappconfig.cpp
> > @@ -395,5 +395,64 @@ void
> > NativeAppConfigType::configureLaunchFromCmdLineArguments ( KConfigGroup
> > cfg
> > 
> >      cfg.sync();
> >  
> >  }
> > 
> > +QList<KDevelop::ProjectTargetItem*>
> > targetsInFolder(KDevelop::ProjectFolderItem* folder) +{
> > +    QList<KDevelop::ProjectTargetItem*> ret;
> > +    foreach(KDevelop::ProjectFolderItem* f, folder->folderList())
> > +        ret += targetsInFolder(f);
> > +
> > +    ret += folder->targetList();
> > +    return ret;
> > +}
> > +
> > +QList<QAction*> NativeAppConfigType::launcherSuggestions()
> > +{
> > +    static QList<QAction*> ret;
> > +    if(!ret.isEmpty())
> > +        return ret;
> > +

Hijacking thread:

Sorry to say Aleix, but what you implemented there does not scale. Open more 
projects and the dropdown will easily fill your whole screen.

I also dislike the place where this is implemented.

Imo we should make the launch config dialog a real wizard and keep the current 
thingy to edit exiting configs.

I imagine a big fat easy to understand button "add new config" that then asks 
me:

a) what project
b) what executable
c) dependencies
d) optional debugger settings

bye
-- 
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/20101024/16da6287/attachment.sig>