closing documents, take 2

[Maciej Pilichowski]

On Tuesday 19 May 2009 19:16:59 Matthew Woehlke wrote:

> > Wait, do we allow that one application instance (process) would
> > have several windows?
>
> Ideally, no :-). In reality, this already happens. Maybe that's the
> problem, I am assuming "application instance" = process.
>
> Okay... if I replace "application instance" with... hmm,
> "application window" isn't a great term, but that idea anyway...

This what I was thinking about. There is an application (kind), you 
can launch it, and you get one instance of it -- to display 
information it uses window (one).

> Would this make more sense? Does it cover what options you are
> wanting to provide?

Errrm, not only me :-))

> When closing a document...

I just realized I made an error while writing, copying&pasting text. 
This should be without above intro text.

>    ( ) Never close the window (application changes to "empty"
> state) 

Yes.

> (X) Close the window if there are sibling windows of the 
> same application type*.

Yes (you for the feature, I opted for making it an option).

>      [X] Disallow closing the document if there are no such
> siblings.

Nope, putting this as negation does not make sense -- there are 
siblings and you cannot close the document? 

Ok, I corrected this (sorry for previous mess):
[ ] on close of document, close "its" application as well if there are 
sibling instances of that application within the container
[x] on close of last application instance in container, keep this 
instance (do not close it)
     [x] close the document only instead

> * ...with tooltip explaining that 'same application type' does not
> include any running on other machines, and probably a description
> of what "application type" means

Yes, and this means also within the same container (well, it was the 
idea originally AFAIR).

> > Maybe it is where confusion comes from. I would say no, because
> > otherwise the whole environment would become more complicated,
> > and from user POV it is hard to tell if the window A and B are
> > from the same or different processes.
>
> It is preferable to hide this from the user as much as possible,
> yes. Ideally by making the behavior consistent regardless of if two
> windows belong to the same process or not.

Well, in the case described above we have to check if there is such 
app within the container -- no matter of origin.

> This is why careful terminology is important ;-).

Yes, I just noticed :-D

Matthew, in KDE is it really possible to have two application windows 
for one instance? What app is able to pull this out?

Cheers,