[development] better autocompletion?

Darrel O'Pry dopry at thing.net
Wed Apr 19 15:07:57 UTC 2006


On Wed, 2006-04-19 at 17:36 +0200, Gerhard Killesreiter wrote:
> Darrel O'Pry wrote:
> > On Wed, 2006-04-19 at 17:20 +0200, Gerhard Killesreiter wrote:
> >   
> >> Bèr Kessels wrote:
> >>     
> >>> Op woensdag 19 april 2006 15:46, schreef Moshe Weitzman:
> >>>   
> >>>       
> >>>> If you don't like this language, you could use other. I like its
> >>>> organicness
> >>>>     
> >>>>         
> >>> This method is how MusicBrainz does its (rather new) relationship interface 
> >>> too. It is interesting, but quite a horror when you are trying to add a 
> >>> relationship with more  tabs open. Just be aware of this, when developing the 
> >>> sessions that contain the pruned comments/nodes.
> >>>
> >>> It is a very interesting concept, especially because you use the 
> >>> statelessness. 
> >>>
> >>>   
> >>>       
> >> I was thinking about multiple tabs and I think that they are actually a 
> >> requirement in this case or at least not harmful.
> >>
> >> Use case: 1 misplaced comment (with children)
> >>
> >> Task: Move it to another node.
> >>
> >> Procedure: Mark comment as "being in the process of grafting" by 
> >> clicking link. Clicking sets a session variable and a redirects to the 
> >> same page. This page will display the message. Now you can go to any 
> >> other node and attach the comment there. It does not matter if you do 
> >> this in the same or another tab. You only need to make sure, the tab has 
> >> been loaded after you clicked on "prune".
> >>
> >> Cheers,
> >>     Gerhard
> >>     
> >
> >
> > Or you could always implement a clipboard like a approach, where you
> > select a few items for pruning. They're tossed in a clipboard, then you
> > can have a select for the graft, which will give you a shorter listto
> > deal with.
> >
> >   
> 
> Also an interesting idea.  I am not sure how the usage pattern for 
> comment_mover will be. Your idea woudl be usefull if I were to move a 
> lot of comments in one session. I think that the usage pattern will 
> rather be to move one comment/thread at a time.
> 
> 
> Cheers,
>     Gerhard

Sounds more likely that you'd do one at a time... unless you come across
a thread that needs moving while looking for that stinking node you
wanted to move that last comment thread to...



More information about the development mailing list