On Tue, 20 Mar 2012, Riccardo (Jack) Lucchetti wrote:
On Mon, 19 Mar 2012, Allin Cottrell wrote:
> I think the best thing at this point would be to disable
> tabbed windows altogether for the release [...]
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.
Agreed, we'll get more bugs shaken out the more people are
trying out the new code. But I don't much like the idea of
making users of an official release into guinea pigs. I think
that given some more testing time, those who use CVS/snapshots
should be able to help us get the new code into more
presentable shape.
Anyway, for now I've done two things in CVS:
* Made it so that an "undocked" editor tab doesn't have the
New and Open controls.
* Added a right-click menu item to let you "re-dock" a script
or model that has been dragged out of a tabbed context.
Allin