[Bf-committers] exit in blender

[Campbell Barton]

After being kicked for supporting the rabble (users) and then some
discussion, here is what Id propose,

* Save in current blend files directory so as not to loose linked
libs. can decide on name convention later, but something like
*.blend_quit, not fussed with specific extension for now.
* Apply editmode changes, so as not to loose work.
* Users need to know this exists, users THINK they loose work because
they arnt aware of quit.blend, blender should make this obvious,
display text while in the header before existing, have a printf in the
terminal....... (will have to sleep on this one :/ but it cant to too
hard)

Another thing that could be done separately.
* remove the cross button from the window border (maybe controversial,
but means you wont close by accidentally), however more of the time I
press Ctrl+Q, enter (mixup w/q) so it only stops 1 way to accidentally
quit. Unix had no window boarder for ages, so removing the X button
cant be that bad bit a deal ;).

As for big blend files, blender should of course save fast, but a
200meg *.blend + *.blend1 + *.blend_quit start to get a but too much,
so saving blend_quit's should be optional.

- Cam

On Tue, Apr 22, 2008 at 11:06 AM, Ton Roosendaal <ton at blender.org> wrote:
> Hi,
>
>  Here's my stance on issues like this:
>
>  We *always* should choose quality over convention, independent of what
>  websites votes for or what "standards" big software companies forced us
>  upon. If requests are popular they reveil a problem, something to
>  seriously tackle, but requests never are by definition the best
>  solution.
>
>  So! If users accidentally lose work, let's tackle that. But don't play
>  the popularity card or the standards card. These are hollow and
>  manipulative arguments, only leading to mediocre solutions.
>
>  -Ton-
>
>
>
>
>  On 19 Apr, 2008, at 17:44, Yves Poissant wrote:
>
>  >> The point is that saving at quit is so fast in blender is that it is
>  >> a better solution that adding a popup. Why should we adopt
>  >> an inferior solution because it is standard ?
>  >
>  > Interesting opinion but not an argument. Standard means that people
>  > using
>  > systems develop habits and automatisms. When a software does not
>  > follow the
>  > standards, then those habits get in the way and produces mishaps. I
>  > lost
>  > works because I forgot to save before quiting. My old habits kikked in
>  > even
>  > though I was aware. That sort of software behavior have become
>  > standards for
>  > good reasons.
>  >
>  >> btw, there is many softwares with automatic saves, like your
>  >> email software.
>  >
>  > Sometimes, I just want to quit and not save.
>  >
>  > _______________________________________________
>  > Bf-committers mailing list
>  > Bf-committers at blender.org
>  > http://lists.blender.org/mailman/listinfo/bf-committers
>  >
>  >
>  ------------------------------------------------------------------------
>  --
>  Ton Roosendaal  Blender Foundation ton at blender.org
>  http://www.blender.org
>
>
>
>  _______________________________________________
>  Bf-committers mailing list
>  Bf-committers at blender.org
>  http://lists.blender.org/mailman/listinfo/bf-committers
>