| Summary: | merge File Selector & File Tree functionality | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Andreas Koepfle <andreas.koepfle> |
| Component: | file tree | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | esigra |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Andreas Koepfle
2003-08-15 03:28:08 UTC
Exelent whish!!!! I'm not quite convinced. The File Selector (FS) and File Tree (FT) serve quite different purposes. FT is a way to interact with and browse the files of the current project. FS is a general purpose network transparent file browser utility. Deletion of project files should happen in the project manager, not in the file system, or the makefiles will get upset. I guess "remove from project / delete" could be safely added to FT, however. Anything else really missing from FT? i like the idea of a merged file selecter and file tree, too. It's confusing atm. I would like to see an even more generalized form of file/project management in the future. There should be a way to easily navigate and restructure a project. Currently restructuring is awkward at best, once the project has only grown big enough. A drag and drop approach would be optimal. And having only one do-it-all panel for all this, too. It is just the way users of the IDE tend to think. Alas, this needs severe replanning. Something for the (not-too-far, I hope) future. > The usability at the moment is not very good: for example you have to use File > Tree to open a file in an external editor or update it from CVS, but File Selector > to delete it. This is partially fixed. I've added KDevelop context menus to the context menu of the File Selector. But I doubt merging is possible. There are technical and conceptual reasons. Jens has already stated conceptual reasons - FS is not applicable for a project management but FT is. Recent commits to FT by Mario prove this (I mean new vcs features of FT). > A drag and drop approach would be optimal. And having only one do-it-all panel > for all this, too. It is just the way users of the IDE tend to think. > Alas, this needs severe replanning. Something for the (not-too-far, I hope) > future. I beleive this can be done using generic project manager. Currently project management in KDevelop consists of 9 parts. We simply can't add all features to all of them. But alas I don't have enough time atm to implement that. Nevertheless, it will be implemented after 3.0 for sure. Merging both the File Selector and the File Tree will be definetely something to do for the 3.1 release since it is late for 3.0 imho. How the merging could be worked out? I'd like to have the cool multi-look of the file selector (adding an additional "vcs view" similar to the "detail view") but which is jailed on the project dir (that is, the user cannot travel all the way through the file system ;-) and have the ability to drag and drop files using standard DND. Hmmm ... this is something to considere looking for kdevelop-cervisia integration but as said before it is stuff for the 3.1 release :-) I would mark this as "LATER" (for a next release), ok? Changing component. I still hate it, btw.. ;) kdev4 has only 1 file-manager, so I guess this can be closed and a new wish opened against kdelibs to provide a tree-like view in the KDirOperator class. |