Try out the new way to configure launches

August 9, 2009 at 12:35 am | Posted in KDevelop | 6 Comments

I’ve just finished a rework of the GUI to configure launches. This is mostly based on feedback I gathered via bugreports, irc chats and mailinglists. Apparently a combobox to just add/remove tabs to an existing tabwidget isn’t working well and suggests to users a completely different thing to configure. Also people expected the selected combobox value (i.e. the launch mode) to be saved across invocations of the dialog.

So this was just confusing people that didn’t write the gui themselves and lead to me explaining how things work over and over again. With recent svn (and this will be in the next beta too) you’ll now get a bit different view:
New Launch Configuration Dialog

As you can see for each launch mode supported by a launch configuration there’s a separate subitem under it to configure the specific things for that launch mode. This of course depends on the actual launcher used for the mode (i.e. which debugger is used for the Debug mode). The generic pages for a launch configuration are available from the launch-config item itself. In the example shot above you can see this includes the actual application to execute, configuration of the dependencies and so on. These settings are used by all the launch modes.

Feedback would be appreciated, preferably via our mailinglist or bugs.kde.org, but if you’re too lazy just add a comment🙂

6 Comments

  1. Nice. This is very much an improvement. Thanks.

  2. I think you should put the + and – buttons below the list, not above. Other than that, great!

  3. This dialogue is a launch-item editor/application, I think the + and – buttons (I assume they are for insert and delete) should be in a tool bar, perhaps with other buttons: cut, copy, paste, undo, redo, etc., although there is a case for having the buttons close to where the mouse last was. The properties on the right should somehow belong to the item selected in the tree view to the left, because the right side overflows it looks like the tree view is part of the properties sheet.
    The window/panel could do with a title to say what type of thing we are editing/configuring, as well as the name of the thing – in fact a slash address bar could reflect the item selected in the tree view, surely different sub-projects could all have a “test” launch-item.

    • This is not an _application_ its a dialog inside kdevelop and as such doesn’t have its own toolbar. Copy/Paster could be added at a later version, I don’t see the need to have redo/undo here.

      Actually the right side doesn’t overflow the left side, but you’ll only see that if you use it. The title (naming the launch) will always stay the same, even if you select the Debug or Profile items.

      Title of the window is already fixed in trunk, realized that only after posting the screenshot🙂

      Last but not least: There’s no “different sub-projects”, only the projects are shown and the title already includes the project if the launch is a project-stored launch.

  4. This is very much of an improvement.

    On the other hand, I think those ellipses are bad. Of course, this can never be perfect can even if you hardcode the column sizes to be suitable for the default set of launchers that KDevelop includes, that would be an better that ellipses by default.

    • Thats fixed in trunk/ already, unfortunately QTreeView’s resizeColumnToContents only looks at the top-level hierarchy, even if sub-tree’s are expanded. I’ve worked around that and you should always have the first column as wide as the initially selected tree-element needs it. So no elippsis is shown.


Sorry, the comment form is closed at this time.

Create a free website or blog at WordPress.com.
Entries and comments feeds.

%d bloggers like this: