Re: [Monotone-devel] [PATCH] mtn automate set_option

[Thomas Keller]

Nathaniel J. Smith schrieb:
> On Thu, Dec 21, 2006 at 03:04:22PM -0500, Ben Walton wrote:
> > I cooked this up today as a corollary to get_option.  I hope it's useful.
>
> So, umm... before investing time in reviewing the patch, rewriting
> internal interfaces, answering future support questions, etc... _do_
> you have any ideas where it would be useful?  Because I'm not really
> sure myself (_MTN/options is really an implementation detail kind of
> thing, and now that I think about it get_option is really unlikely to
> survive into mtn 1.0), and it seems silly to spend that time unless
> it's plausible that there will be commensurate rewards?

Don't get me wrong, but how is he supposed to know that? Maybe we should 
start and explicitely name / comment certain things as "temporary, will 
be replaced", so no manpower goes into that?

In the end get_option as well as set_option is just some interface to 
something which has been introduced into monotone for some time 
(workspace options), probably long before I knew monotone, but didn't 
get proper UI support until now. IMHO there are use cases when 
get/set_option is useful, now the question is if these use cases should 
get support or if we should throw them over because they're just of 
temporary nature?

Thomas.

--
ICQ: 85945241 | SIP: 1-747-027-0392 | http://www.thomaskeller.biz
> Guitone, a frontend for monotone: http://guitone.berlios.de
> Music lyrics and more: http://musicmademe.com