[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AppIcon patch revisited
From: |
Stefan Boehringer |
Subject: |
Re: AppIcon patch revisited |
Date: |
Sat, 10 Feb 2001 13:33:19 +0100 |
Hello Richard,
I think that there is some good chance to realize Dan's proposal without breaking the layering of the GNUstep API.
However this is at the cost of extending the existing backend API. There should be precisely the chance to forward events back to the backend. Then a miniwindow could forward back unneeded mouse down events.
In my point of view there is no way around doing some extra work to get mini windows straight. Having a window fully functional but at the same time dockable and correctly tiled needs special treatment somewhere in the libraries. I'm not convinced that it is WMakers part to handle all those complications, since it seems to be quite GNUstep specific etc., and we (the GNUstep libraries) have good chances to handle the case gracefully.
Unfortunatly I'm not familier with the backend stuff, so I just want to point out this possibility.
Best wishes,
Stefan
Richard Frith-Macdonald wrote:
> On Saturday, February 10, 2001, at 07:45 AM, Dan Pascu wrote:
>
> > On 9 Feb, Richard Frith-Macdonald wrote:
> > >> btw, why is appicon movement needed under program control (not user
> > >> control)?
> > >
> > > Under OpenStep, they are the same thing ... the user clicks on the
> appicon > > and drags ... the program decides how the appicon should react to
> that ... > > and usually moves the appicon to follow the mouse ... but has
> the right to > > do something different if it wants to.
> >
> > This should be easy. If the app doesn't want it to move, it shouldn't
> > relay the left click back to wmaker.
>
> But the app doesn't do the relaying ... that's handled by the backend
> library. The app (ie the code written by the app developer, not the library
> code) knows nothing about window managers and X.
>
> It's important to realise that a GNUstep app is *NOT* an X application - the
> application code has absolutely nothing to do with X, and any X interaction
> is performed only by a backend library.
>
> Check out the OpenStep or MacOS-X AppKit API ... this is the API that a
> GNUstep gui application is written to, not the X API.
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> `http://mail.gnu.org/mailman/listinfo/discuss-gnustep
>
- Re: AppIcon patch revisited, (continued)
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/09
- Re: AppIcon patch revisited, Frederic Stark, 2001/02/09
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/09
- Re: AppIcon patch revisited, Frederic Stark, 2001/02/09
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/09
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/10
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/10
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/10
- Re: AppIcon patch revisited, Richard Frith-Macdonald, 2001/02/10