Bug 384955

Summary: Use project name set in import wizard in more place throughout the KDevelop UI
Product: [Developer tools] kdevplatform Reporter: RJVB <rjvbertin>
Component: shellAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: git master   
Target Milestone: ---   
Platform: Compiled Sources   
OS: All   
URL: https://phabricator.kde.org/D9344
Latest Commit: https://phabricator.kde.org/R32:a44554ef038aca23f803e693bc01284ab099e04e Version Fixed/Implemented In: 5.3.0
Sentry Crash Report:

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?