Bug 65348

Yes there is. Do you really think that we would use such an IDE (one that 
wouldn't allow to add files) :) 
 
Just take a better look on the automake manager on the rigth side of your 
screen. 
 
Have fun :) 
 
PS: VC++ is not "the dreaded competitor"! We are better than VC++ :) 
 

Aha!!! There is the problem. I am not using automake!!!  
  
I am working on an embedded project for which I have my own makefiles. I  
imported it using the import project option, which worked excellently.  
  
However, any features which are located in the automake menu, like  
(apparently) project file management don't exist for me.  
  
I apparently have no way to re-open this bug. Should I open another? 
 
(No I am not a *complete* moron, although I often sound like one!;-)) 

This time I was able to re-open. (Figured out that I had to be logged in.) 
 
> Aha!!! There is the problem. I am not using automake!!!  
  
> I am working on an embedded project for which I have my own makefiles. I  
> imported it using the import project option, which worked excellently.  
  
> However, any features which are located in the automake menu, like  
> (apparently) project file management don't exist for me.  
  
> I apparently have no way to re-open this bug. Should I open another?  
  
> (No I am not a *complete* moron, although I often sound like one!;-)) 

Custom project needs a maintainer. Are you up to it? 

What are you asking?

By 'custom project', do you mean the embedded project I am working on? Well I
hope so, I am getting paid a fairly decent salary for it.

If by 'custom project' you mean the custom project portion of kdevelop. I'd have
to answer no for the short term since I am on some fairly heavy deadlines for
the aforementioned embedded project. However, in a couple of months I might be
able to get into it. Maybe before then I'll try and get the kdevelop build
envornment set up and see if I can figure out the code enough to implement some
feature additions.

Meantime, I can work around by just running 'find' to recreate the filelist file.

By 'custom project' I mean the custom project part of kdevelop.

There are context menu entries in the file tree and file seclector popup menus that allow you to add/remove files to a custom makefile project.
I think this bug could be closed. 

Found it and it works. Thanks.

One additional comment: The menu item in question is slightly deceptive to me (which is probably why I missed it).

The menu item says:

	'Add to Project: $FileName$'

where $FileName$ is the filename. However, I took the text of this to mean "Add the file to a new project named '$FileName$'". Admittedly, I am sometimes a bit slow, but there are bound to be others who are just as slow.

The thing that got me was that the menu item takes the trouble to name the particular file that will be added in a menu where you can't select multiple files and which already implies that the filename in question is what you are acting on. This reminds me of the windows zip shortcuts that say things like 'add to zip' and 'add to new zip called $something_similar_to_the_filename$' I therefore expected a similar behavior.

You have a point there. Given that its a context menu, "Add file to project" should be sufficient. 
(rewording it to 'Add $FileName$ to project' would be an option too)

should I re-open the bug? or open a new change request?

Subject: kdevelop/buildtools

CVS commit by aclu: 

Usability fix

CCMAIL: 65348@bugs.kde.org


  M +2 -2      ant/antprojectpart.cpp   1.19
  M +2 -2      custommakefiles/customprojectpart.cpp   1.65


--- kdevelop/buildtools/ant/antprojectpart.cpp  #1.18:1.19
@@ -554,5 +554,5 @@ void AntProjectPart::contextMenu(QPopupM
   if (inProject)
   {
-    int id = popup->insertItem( i18n("Remove From Project: %1").arg(popupstr),
+    int id = popup->insertItem( i18n("Remove %1 from project").arg(popupstr),
                        this, SLOT(slotRemoveFromProject()) );
     popup->setWhatsThis(id, i18n("<b>Remove from project</b><p>Removes current file from the project."));
@@ -560,5 +560,5 @@ void AntProjectPart::contextMenu(QPopupM
   else
   {
-    int id = popup->insertItem( i18n("Add to Project: %1").arg(popupstr),
+    int id = popup->insertItem( i18n("Add %1 to project").arg(popupstr),
                        this, SLOT(slotAddToProject()) );
     popup->setWhatsThis(id, i18n("<b>Add to project</b><p>Adds current file from the project."));

--- kdevelop/buildtools/custommakefiles/customprojectpart.cpp  #1.64:1.65
@@ -183,5 +183,5 @@ void CustomProjectPart::contextMenu(QPop
     if (inProject)
     {
-        int id = popup->insertItem( i18n("Remove From Project: %1").arg(popupstr),
+        int id = popup->insertItem( i18n("Remove %1 from project").arg(popupstr),
                            this, SLOT(slotRemoveFromProject()) );
         popup->setWhatsThis(id, i18n("<b>Remove from project</b><p>Removes current file from the list of files in project. "
@@ -190,5 +190,5 @@ void CustomProjectPart::contextMenu(QPop
     else
     {
-        int id = popup->insertItem( i18n("Add to Project: %1").arg(popupstr),
+        int id = popup->insertItem( i18n("Add %1 to project").arg(popupstr),
                            this, SLOT(slotAddToProject()) );
         popup->setWhatsThis(id, i18n("<b>Add to project</b><p>Adds current file to the list of files in project. "

You guys are the greatest!

*** Bug 67468 has been marked as a duplicate of this bug. ***

There are still problems with kdevelop 3.0.1:

The option "add file to project" is missing from the file context menu in the file tree (at least for the qmake manager, did not check others)

The manual does not say that one has to use some "manager" to add an existing file to the project. Deeply in the "automake manager" chapter, there is a screenshot from where you can guess a way to add existing files, but this is not where one expects it. I would rather expect it in chapter 8 (I guess this should be names "project mangement", given the fact that chapter 14 is also called "advanced project management")

Please consider readding the menu entry Project->add existing file(s). From a kdevelop users POV this seems natural. From a kdevelop developers POV the "manager" things may be convenient, but as a user I only want to think about build sytems when I create a project. Afterwards, I just want to use them, and they should not hide important functionality in a difficult to find place.

Last, but not least: Yes, I do read documentation, and yes, I do mean this seriously, and yes, I have spent a long time figuring out how to add files via the GUI. In the end, I added the files to the qmake .pro file by hand.

PS: How can I reopen this bug?

Reopened, as demanded by last comment. See also http://lists.kde.org/?l=kde-devel&m=110361374410554&w=2 for some other guys requesting this. I myself was bitten by this too.

*** This bug has been confirmed by popular vote. ***

It seems its hard to find in the context menu of the file tree view.

Well, it is missing sometimes (see my comment 15). This is still true for kdevelop 3.2.0 (KDE 3.4.2).

Well the bug has been fixed in KDevelop 3.3.0 and the documentation has been much improved.

Nowadays we do not get e-mails or posts on the forum asking how to do it.

There should be such function in file or project menu indeed -- plus more:
* add current file to project
* remove current file from project
* add all opened files to project
* remove all opened files from project (makes sense if your project is pretty big)

v 3.3.5 

Still dont see this in any menu. File list, File selector ... none of the context menus have an "add to project" item.

Bottom line: why is this not on the Project menu? This must surely be the first place everyone would expect to find it.

Also could we please have some hints on the automake mangager icons. 

I should not have to click on everything to see what it does. This may even be distructive since I have no idea if it's dlg I can cancel or a button that has a direct action.

Maybe there is a need to increase visibility / accessability of the automake manager. I had never even noticed these tabs descretely tucked away of the right of the screen until I read this bug !

Adding an entry on the tools menu that opened up the auto-manage tab would be a good way of making this discoverable from the UI.

Saying RTFM is simply to admit a poorly designed interface.

I specifically went searching this for everwhere in the interface yesterday and concluded it was an omition in kdevelop.

Since this is such a fundemental function it should be a lot easier to find.
Thx.

> Also could we please have...

Is adding another report is so hard? Putting "and also this and this (losely related)" in one report is just making improvements to KDevelop more difficult for the developers (think: tracking requests).

Customer project does have context menu to add/remove files.
Automake, qmake, etc projects do not. They use the automake manager - hidden (till now) on the right.

As of revision 601417, there are:
- tool tips on the icons in the automake manager
- icons are disabled if they cannot be selected.
- project opens with automanager extended from right side - to make it clear that it is there.

This should help for now. This area is getting more work done on it.

> Customer project does have context menu to add/remove files.

Ok, but does this work? You are talking about released version or SVN?

I see such option in context menu but it failed silently (for external files for example) and it still fails now (it is a bug really, because it should work or provide some nice warning what is going on). So I see no change here.

Comment #24 is about obviously about KDevelop 3.4 from SVN.
http://www.kdevelop.org/index.html?filename=3.3/ChangeLog.html
http://www.kdevelop.org/index.html?filename=3.4/ChangeLog.html

We do have add/remove files on custom, qmake and automake projects, closing as fixed.

I could state that it is still missing for PHP projects (and maybe other projects, too). Or am I just too blind to see it.

No you're not blind. Script projects are not very well supported in KDevelop and thus the manager for script project doesn't offer this functionality. In fact I suggest to use more apropriate apps for PHP/HTML development, like Quanta.

If anybody demands it I will re-open the wishlist report, but its pretty sure that this will never happen for script projects in KDevelop3.

Shall I note that you don't need "add/remove to project" actions for scripting projects. The current implementation will load all files that comply with the pattern. And that's good. The problem is that the script manager doesn't get notified of new files. But that's a separate bug actually.