On Mon, 19 Mar 2012, Allin Cottrell wrote:
I'd like to get a release out soon. That raises the question
of what to do with the new tabbed windows.
I think the best thing at this point would be to disable
tabbed windows altogether for the release, then resume testing
and development in CVS. With the tabbed model window I don't
feel I can guarantee that it works right in all respects; and
with the tabbed script editor the issue is that the design
isn't finalized -- in particular, in respect of what happens
when you "undock" a tab.
I've been playing with tabs intermittently and my house hasn't caught
fire, nor my dog has been eaten by aliens. OTOH, I never set to work with
the specific intent of stress-testing tabbed windows by trying crazy
things. For these things, you need the wisdom of crowds. How about leaving
the situation as is now (that is, no tabs by default, but you can enable
them if you want) but addin, somehow, a big flashing "WARNING!
EXPERIMENTAL! USE AT YOUR OWN RISK!" sign?
Anyway, the bottom line is that I don't want to put half-baked
stuff into a release.
I hear you, but my point is that it's almost impossible for a group of
50-100 people to debug a thing like tabs to the end; you need the mass of
users to find the weird guy who tries something totally unexpected and
triggers the corner case.
Riccardo (Jack) Lucchetti
Dipartimento di Economia
Università Politecnica delle Marche
(formerly known as Università di Ancona)