Bug 384955 - Use project name set in import wizard in more place throughout the KDevelop UI
Summary: Use project name set in import wizard in more place throughout the KDevelop UI
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: shell (other bugs)
Version First Reported In: git master
Platform: Compiled Sources All
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL: https://phabricator.kde.org/D9344
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-22 10:46 UTC by RJVB
Modified: 2018-04-05 12:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-09-22 10:46:39 UTC
When importing (creating) a new project the import wizard proposes a name that can be changed into something potentially more meaningful than the directory name. This custom name is used in the project toolview, but nowhere else.

That's confusing.

I'd like to see that name being used as widely as possible:
1. name of the $project.kdev4 and .kdev4/$project.kdev4 files
2. name used in the titlebar, for tagging files that have homonyms in other open projects
3. name used in the session overview dialog (`kdevelop --ps`)

Points 1 and 2 may justify adding the concept of an abbreviated/simplified name.
Comment 1 RJVB 2017-12-14 10:59:57 UTC
I've started looking into the relevant code searching for a single, central, lowlevel location where the .kdev4 filename(s) is/are determined when importing a project for the 1st time. For now I only found what's probably the level just below that: ProjectConfigSkeleton.
It's used from a template class ProjectConfigPage, which appears to be used directly from all individual projectmanager types.

Am I looking for something that doesn't exist?