[Pidgin] #8789: Allow all window managers to handle conv window placement

[Pidgin]

#8789: Allow all window managers to handle conv window placement
-----------------------------------------+----------------------------------
 Reporter:  karvanitis                   |        Owner:  deryni      
     Type:  patch                        |       Status:  new         
Milestone:  Patches Needing Improvement  |    Component:  pidgin (gtk)
  Version:  2.5.5                        |   Resolution:              
 Keywords:  conv window manager          |  
-----------------------------------------+----------------------------------

Comment(by deryni):

 Your patch doesn't "allow for th[at] in Pidgin" it removes pidgin's
 ability to place windows entirely, that's not quite the same thing (nor is
 it place-first-cascade-subsequent, which is what was being discussed).

 As I've said more than once that is *one* possible desire and by no means
 am I convinced it is the main one, nor is it what your patch does (as I
 indicated above).

 I would be perfectly happy to remove all size/location remembering code
 from pidgin entirely but that would negatively affect an enormous
 percentage of pidgin users.

 I'm not at all convinced that IE, firefox, or opera behave anywhere near
 that simply in terms of remembering window positions (at least not given
 my experience with multiple monitors at work). I don't know what other
 programs do or do not do.

 I actually wonder how the cascading works with an initially placed window,
 I actually think the application probably has to do that itself since I
 can't see how Windows would handle that correctly automatically, but I'd
 love for someone who actually knows to comment on that.

 If it was possible for pidgin to place the initial window and then let
 Windows do the rest I would accept a patch which tested for the existence
 of another conversation window before placing the new window. I'm not at
 all certain I'd accept a patch which implements manual cascading.

 You've also managed to avoid considering any of the non-placement points
 under discussion, that is the points about which windows position and size
 to save for the next placement. Which is, in reality, where this gets most
 complicated anyway.

 I fully admit that if placing the initial window is all that is necessary
 to trigger Windows to do the right thing with subsequent window placement
 that allowing that to happen is almost certainly better than what we have
 now, but I'm not convinced that is the case, nor am I convinced that
 everyone will want that (hence the plugin-able action discussion).

-- 
Ticket URL: <http://developer.pidgin.im/ticket/8789#comment:18>
Pidgin <http://pidgin.im>
Pidgin