Re: Re: Delete Project behavior

Hi again,

Just to avoid accidental project deletion I'd suggest making 3.3 the 
default option, so that if a user presses "Enter" without thinking (*) 
then the new dialog (presenting the dirs to delete) may save him some 
headache.

Cheers,
Antonio

(*) I press Enter without thinking quite often. In fact I can't think at 
all: I'm just a borg.


Antonio wrote:
> Hi,
> 
> Too complex, I'd say. What about this?
> 
> 1.- The user selects the "Delete project" menu item.
> 2.- A confirmation dialog appears, presenting the following options:
> 
>     Delete Project will delete all
>     files under /home/whatever/myproject.
> 
>     Are you sure you want to do this?
> 
>     [Yes] [No] [Select files to delete]
> 
> 3.1.- If the user clicks "Yes" files are deleted
> 3.2.- If the user selects "no" no files are deleted, and
> 3.3.- If the user selects "Select files to delete" then a new dialog box 
> appears, asking the user for confirmation on what to delete (using the 
> component Jesse has explained).
> 
> Cheers,
> Antonio
> 
> 
> Jesse Glick wrote:
>> [BTW please do not cross-post to multiple lists. nbui is the right 
>> list, I think.]
>>
>> Edwin Goei wrote:
>>> So the proposal is to change the meaning of the checkbox to "rm -rf 
>>> $projectdir".
>>
>> 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?
>>
>> Let me propose a completely different UI that I think would be much 
>> clearer. The dialog would contain a forest (list of trees) which would 
>> look a bit like the Files tab if just that project were open. Each 
>> root corresponds to one top-level directory and is labelled with the 
>> full path to that dir. For projects made from scratch there would be 
>> just one root; for projects from existing sources you would often have 
>> one entry for the NB metadata and one for the existing sources.
>>
>> The trees would be checkbox trees, i.e. each node can have states 
>> checked (delete entirely), unchecked (leave alone), half-checked (look 
>> at children to see which parts will be deleted).
>>
>> By default, the project directory (parent dir of nbproject) would be 
>> checked, except that any nested project directories would be 
>> unchecked. External source roots would by default be unchecked.
>>
>> Ignorable dirs (build, nbproject/private, ...) would always be deleted 
>> and would not be displayed at all.
>>
>> Examples:
>>
>> [X] /home/jglick/NetBeansProjects/quick-experiment
>>     [X] nbproject
>>     [X] src
>>     [X] test
>>     [X] build.xml
>>
>> [X] /home/jglick/NetBeansProjects/jedit
>>     [X] nbproject
>>     [X] build.xml
>> [ ] /sources/jedit/src
>>     [ ] org
>>
>> [/] /sources/nb_all/contrib/failed-experiment
>>     [X] nbproject
>>     [X] src
>>     [X] release
>>     [X] build.xml
>>     [X] manifest.mf
>>     [ ] another-module
>>
>> -J.
>>