Bug 78478 - creating new project (in existing dir.), and ...
Summary: creating new project (in existing dir.), and ...
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.1
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-26 09:35 UTC by ivan
Modified: 2008-06-29 18:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ivan 2004-03-26 09:35:04 UTC
Version:           3.0.1 (using KDE 3.2.1, Gentoo)
Compiler:          gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
OS:          Linux (i686) release 2.6.3-gentoo-r1

1.When user want to create new project, and path /<Location>/<Application Name>/ exists its should be like warning not error, (error should be when file /<Location>/<Application Name>/<Application Name>.kdevelop exists).
2.There are no saved tree tool views positions.
3.There could be same one type of small project with Makefile, and .c/.cpp/.h etc files (without automake,configure and so on)
4.There could be Find In Open Files in find dialog, and this same with replace dialog.
5.The status line (in kdevelop) could be like toolbar.
6.Expand One Local Level works like Expand Toplevel , but only from keyb. (Ctrl++ for one local level and shift+ctrl++ for toplevel)
7.Could be shorts keys like for example "double esc" (like dblclick) ?

thanks :]
Comment 1 Amilcar do Carmo Lucas 2004-07-18 21:56:52 UTC
Some comments,

1. You are wrong, <Application Name>.kdevelop is not the only file that kdevelop overwrites, so we would have o check many files (complicated) or not allow you to put it there at all (easy, safe and current solution already)
2. Completly unrelated and already reported.
3. Again, this is a already reported point.
4. good point, open a new bug report for it please.
5. ????
6. file a treeview bug report.
7. ??? what would be the use of it? 

So basicaly you should file separate bug reports for each item.
Comment 2 Jens Dagerbo 2004-07-19 00:39:00 UTC
Like Amilcar stated, this is not the proper way of opening wishlist reports. Mixing several different topics into the same report just makes discussion and followup that much harder. If you feel you don't have the energy to open several different reports, then please don't bother at all. That said..

2. Fixed.
5. I think I know what you mean and I have made a prototype. Won't be in 3.1, but perhaps in 3.2
6. I think Amilcar got you wrong here. You are talking about editor folding, right? Take it up with the Kate devs.
Comment 3 Andreas Pakulat 2008-06-29 18:46:32 UTC
closing this as invalid as its impossible to follow multiple items in one report.