From: Hal Fulton <hal9000@...>
Date: 2005-05-03T11:56:24+09:00
Subject: Re: "Bounty" approach for small pieces of code?

Richard Lyman wrote:
> 
> How black of a box do you want?
> 
> The problem, as I see it, is that we probably have different
> expectations of what it is to 'manually move an entry around'.
> 
> I'm fine with it not giving any indication of where the item will be
> dropped until after the move has been performed - you might want a
> visual indication of the results of your actions before you commit
> them... say... a line that moves between the elements as you move your
> selected entry into place - or maybe you want 'live dragging' so that
> the item is always where it would be if you dropped it... but then how
> would you decided where in the depth of the tree it would be placed?
> 
> Also - what kind of 'parenting' would I assume for the default? To
> make the dropped entry a child above/below the entry it was dropped
> on, or to make it a child/parent of the entry it was dropped on?
> 
> There are a lot of questions - I'm not sure what the 'default'
> behavior would be, to say nothing of what the default keys for moving
> an entry should be...

Quite right, there would be issues to resolve. This is one that I
haven't thought through.

The only other example I can think of would be even harder to specify --
an icon editor "superwidget" that could be included inside other apps.

I am mainly testing the water to see if anyone is open to this sort
of idea in general.

But your point is valid. To spec things out fully is hard. Maybe not
quite as hard as writing the code, but not trivial.


Hal