Re: Re: Delete Project behavior
Stanislav Aubrecht <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.user-interface |
|---|---|
| Message-ID | <[email protected]> |
Jan Rojcek wrote: > On 20 Jun 2007, at 18:47, Jesse Glick wrote: > >> I agree that if you ask to delete a project, you probably intend to >> delete the whole project directory. I am always being surprised by >> Delete Project leaving all kinds of things around for no apparent >> reason. And the "also delete sources" checkbox has always mystified >> me. I asked to delete the project. A project is an IDE's way of >> managing program sources. What am I being asked, exactly? > > Other issues with delete: > > - I forgot why the delete action builds the project (actually cleans > it) before it deletes it. Seems very strange to me. > - I cannot select and delete multiple projects which can be quite > common when evaluating IDE and playing with different kinds of projects. > > I agree that clarifying what exactly gets deleted would be fine. OTOH, > I'm not sure the user wants the flexibility you're proposing. I'm also > thinking about how it would work for deleting multiple projects. How > about just showing the top level folders? In your examples it would be: > > [X] /home/jglick/NetBeansProjects/quick-experiment > > [X] /home/jglick/NetBeansProjects/jedit > [ ] /sources/jedit/src > > [X] /sources/nb_all/contrib/failed-experiment > > The last example would never delete the nested project folder. If the > user wants to delete it, she can do it by opening and deleting the > project. isn't this an overkill? i usually use just file manager to delete my projects... stan > > -Jano