[Design] sowers notes #3

[Reid Ellis]

The model of which this reminds the most is the mp3 player model,  
particularly iTunes.

You have a library (All Items), and you have playlists (Collections).  
When you drag a song from one playlist to another, you get another  
reference in that playlist, but the reference from the originating  
playlist doesn't go away.

If you remove a song from a playlist (Edit->Remove), it is still in  
your library and other playlists.

If you delete something from your library (deleting item/dragging  
item to trash), it is also removed from all your playlists.

Chandler is like iTunes for your life.

Oooh, catchy phrase. To bad it contains a registered trade mark. :-)

Reid

On Fri Feb 24 2006, at 11:15, Jeffrey Harris wrote:
> Hi Jim,
>
>> * Dragging an event to a new collection, should be by default rather
>> than a copy.
>
> In other applications, there are many situations where copy is the
> default drag and drop behavior.  I think copy is a reasonable default
> here.  But I do think shift-dragging should force a move, I just  
> created
> bug 5276 for this.
>
>> Also, since it is a copy, if I drag an event to a new collection, and
>> then delete it from the original collection, it gets deleted from
>> BOTH.  Seems that assumption should be that calendars are segregated.
>
> There are two, slightly different, removal actions.  Delete, or  
> dragging
> to the trash, moves the item itself to the trash, which means that  
> item
> will go away everywhere.
>
> Remove, which is currently only available through the edit menu, does
> what you're looking for when moving, it removes the item from the
> currently selected collection.
>
> Sincerely,
> Jeffrey