From neuhauser at bellavista.cz  Wed Mar  5 03:10:43 2003
From: neuhauser at bellavista.cz (Roman Neuhauser)
Date: Wed, 5 Mar 2003 09:10:43 +0100
Subject: [openbox] Re: Openbox, FreeBSD & Xft2
In-Reply-To: <20030204223600.GI3244@orodu.net>
References: <20030204162025.GA33898@meia.meia.local> <20030204223600.GI3244@orodu.net>
Message-ID: <20030305081043.GK12954@freepuppy.bellavista.cz>

# ben at orodu.net / 2003-02-04 16:36:00 -0600:
> On Tue, Feb 04, 2003 at 07:20:25PM +0300, Andrew Dolgov wrote:
> > Hi,
> > 
> > I have a little suggestion for Openbox under FreeBSD: it would be
> > nice to detect and use X11/Xft2.h if it is available, because Xft2
> > installed from ports uses this header file by default instead of
> > X11/Xft.h.
> 
> It would be nice. Te ports maintainer for Xft has decided to do a very
> nonstandard thing. I've told a couple users to file a bug report but I
> doubt anyone has bothered. My best advide is to rename Xft.h to Xft1.h
> and Xft2.h to Xft.h.

    FYI, this seems to have happened already. See
    http://marc.theaimsgroup.com/?l=freebsd-ports&m=104561709809620&w=2

-- 
If you cc me or remove the list(s) completely I'll most likely ignore
your message.    see http://www.eyrie.org./~eagle/faqs/questions.html


From pmartin at patm.net  Fri Mar 14 01:45:29 2003
From: pmartin at patm.net (Pat Martin)
Date: Thu, 13 Mar 2003 22:45:29 -0800
Subject: Xft and RedHat 8
In-Reply-To: <20030206004439.GX1303@dan0032.urh.uiuc.edu>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu>
Message-ID: <20030314064529.GA5717@patm.net>


I have been playing with openbox in RedHat 8 and I really like it. I
have a question concerning AntiAliased Fonts. I don't think openbox is
using AA fonts when needed I have added some true type fonts in the
~/.font directory and they appear in mozilla and other apps just fine
but when different styles call for them the styles end up with really
small fonts and changing font sizes in the style doesn't seem to affect
it. I notice on the web site that it talks about a proper Xft file but
RedHat 8 doesn't use an Xft.conf file. Anyone have ideas how I can fix
this problem?

Thanks.


From ben at orodu.net  Fri Mar 14 13:54:43 2003
From: ben at orodu.net (Ben Jansens)
Date: Fri, 14 Mar 2003 12:54:43 -0600
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030314064529.GA5717@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net>
Message-ID: <20030314185443.GE7849@orodu.net>

On Thu, Mar 13, 2003 at 10:45:29PM -0800, Pat Martin wrote:
> 
> I have been playing with openbox in RedHat 8 and I really like it. I
> have a question concerning AntiAliased Fonts. I don't think openbox is
> using AA fonts when needed I have added some true type fonts in the
> ~/.font directory and they appear in mozilla and other apps just fine
> but when different styles call for them the styles end up with really
> small fonts and changing font sizes in the style doesn't seem to affect
> it. I notice on the web site that it talks about a proper Xft file but
> RedHat 8 doesn't use an Xft.conf file. Anyone have ideas how I can fix
> this problem?

If you're using Openxbox 2.x with Xft 2, I'd recomment upgrading to 2.3.0.
This is most likely your problem. 2.x had some issues with font loading that
have been fixed.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030314/99d420e1/attachment.pgp>

From v.merkatz at gmx.net  Sat Mar 15 15:11:03 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Sat, 15 Mar 2003 21:11:03 +0100
Subject: patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
Message-ID: <20030315201103.GA10266@Otherland>

Hi,
openbox 2.3.0 claims to support NET_WM_STATE_FULLSCREEN, but to really
support it, it should resize windows setting that hint to fullscreen and
remove decorations.
The wm spec on freedesktop.org doesn't state this clearly, but that's
how metactiy, sawfish and kwin implement it.

The attached patch adds this functionality to openbox 2.3



Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org
-------------- next part --------------
Index: src/Window.cc
===================================================================
RCS file: /cvs/cvsroot/openbox/src/Attic/Window.cc,v
retrieving revision 1.183.2.9
diff -p -u -r1.183.2.9 Window.cc
--- src/Window.cc	2003/02/03 01:31:46	1.183.2.9
+++ src/Window.cc	2003/03/15 19:48:19
@@ -337,6 +337,8 @@ BlackboxWindow::BlackboxWindow(Blackbox 
 
   if (flags.maximized && (functions & Func_Maximize))
     remaximize();
+  if (flags.fullscreen)
+    doFullscreen();
 
   // create this last so it only needs to be configured once
   windowmenu = new Windowmenu(this);
@@ -2077,6 +2079,38 @@ void BlackboxWindow::remaximize(void) {
   blackbox_attrib.premax_h = premax_h;
 }
 
+
+void BlackboxWindow::doFullscreen(void) {
+  if (flags.fullscreen) {
+    // save current size/position (can i use the premax variables???)
+    blackbox_attrib.prefull_x = frame.rect.x();
+    blackbox_attrib.prefull_y = frame.rect.y();
+    blackbox_attrib.prefull_w = frame.rect.width();
+    blackbox_attrib.prefull_h =
+      client.rect.height() + frame.margin.top + frame.margin.bottom;
+    // go fullscreen
+    client.rect = screen->getRect();
+    frame.rect = screen->getRect();
+    configure(frame.rect.x(), frame.rect.y(),
+              frame.rect.width(), frame.rect.height());
+    // disbale decorations
+    enableDecor(False);
+    screen->getWorkspace(blackbox_attrib.workspace)->raiseWindow(this);
+    // disable functions, save old functions
+    blackbox_attrib.prefull_functions = functions;
+    functions = 0;
+  } else {
+    // reenable functions
+    functions = blackbox_attrib.prefull_functions;
+    // reenable decorations
+    enableDecor(True);
+    // restore size
+    configure(blackbox_attrib.prefull_x, blackbox_attrib.prefull_y,
+              blackbox_attrib.prefull_w, blackbox_attrib.prefull_h);
+    blackbox_attrib.prefull_x = blackbox_attrib.prefull_y = 0;
+    blackbox_attrib.prefull_w = blackbox_attrib.prefull_h = 0;
+  }
+}
 
 void BlackboxWindow::setWorkspace(unsigned int n) {
   blackbox_attrib.flags |= AttribWorkspace;
Index: src/Window.hh
===================================================================
RCS file: /cvs/cvsroot/openbox/src/Attic/Window.hh,v
retrieving revision 1.27.2.1
diff -p -u -r1.27.2.1 Window.hh
--- src/Window.hh	2003/01/11 20:37:50	1.27.2.1
+++ src/Window.hh	2003/03/15 19:48:20
@@ -400,6 +400,7 @@ public:
   void withdraw(void);
   void maximize(unsigned int button);
   void remaximize(void);
+  void doFullscreen(void);
   void shade(void);
   void stick(void);
   void reconfigure(void);
Index: src/blackbox.cc
===================================================================
RCS file: /cvs/cvsroot/openbox/src/Attic/blackbox.cc,v
retrieving revision 1.42
diff -p -u -r1.42 blackbox.cc
--- src/blackbox.cc	2002/08/27 08:18:04	1.42
+++ src/blackbox.cc	2003/03/15 19:48:24
@@ -827,6 +827,7 @@ void Blackbox::process_event(XEvent *e) 
               } else if (state[i] ==
                          xatom->getAtom(XAtom::net_wm_state_fullscreen)) {
                 win->setFullscreen(True);
+                win->doFullscreen();
               }
             } else if (action == 0) {
               // REMOVE
@@ -861,6 +862,7 @@ void Blackbox::process_event(XEvent *e) 
               } else if (state[i] ==
                          xatom->getAtom(XAtom::net_wm_state_fullscreen)) {
                 win->setFullscreen(False);
+                win->doFullscreen();
               }
             } else if (action == 2) {
               // TOGGLE
@@ -904,6 +906,7 @@ void Blackbox::process_event(XEvent *e) 
               } else if (state[i] ==
                          xatom->getAtom(XAtom::net_wm_state_fullscreen)) {
                 win->setFullscreen(! win->isFullscreen());
+                win->doFullscreen();
               }
             }
           }
Index: src/blackbox.hh
===================================================================
RCS file: /cvs/cvsroot/openbox/src/Attic/blackbox.hh,v
retrieving revision 1.15
diff -p -u -r1.15 blackbox.hh
--- src/blackbox.hh	2002/08/10 18:21:10	1.15
+++ src/blackbox.hh	2003/03/15 19:48:24
@@ -78,6 +78,9 @@ struct BlackboxAttributes {
   unsigned long flags, attrib, workspace, stack, decoration;
   int premax_x, premax_y;
   unsigned int premax_w, premax_h;
+  unsigned char prefull_functions;
+  int prefull_x, prefull_y;
+  unsigned int prefull_w, prefull_h;
 };
 
 #define PropBlackboxHintsElements      (5)

From smoynes at nexus.carleton.ca  Sat Mar 15 15:26:22 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Sat, 15 Mar 2003 15:26:22 -0500
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030315201103.GA10266@Otherland>
References: <20030315201103.GA10266@Otherland>
Message-ID: <20030315202622.GG10629@marilyn>

* Arwed von Merkatz (v.merkatz at gmx.net) wrote:
> Hi,
> openbox 2.3.0 claims to support NET_WM_STATE_FULLSCREEN, but to really
> support it, it should resize windows setting that hint to fullscreen and
> remove decorations.
> The wm spec on freedesktop.org doesn't state this clearly, but that's
> how metactiy, sawfish and kwin implement it.

Thanks, I've put this on my TODO. The only problem is, without
decorations, it is difficult to do some operations on the window, but
I don't think that's such a big deal.

-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra


From v.merkatz at gmx.net  Sat Mar 15 16:12:47 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Sat, 15 Mar 2003 22:12:47 +0100
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030315202622.GG10629@marilyn>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn>
Message-ID: <20030315211247.GA22474@Otherland>

On Sat, Mar 15, 2003 at 03:26:22PM -0500, smoynes at nexus.carleton.ca wrote:
> * Arwed von Merkatz (v.merkatz at gmx.net) wrote:
> > Hi,
> > openbox 2.3.0 claims to support NET_WM_STATE_FULLSCREEN, but to really
> > support it, it should resize windows setting that hint to fullscreen and
> > remove decorations.
> > The wm spec on freedesktop.org doesn't state this clearly, but that's
> > how metactiy, sawfish and kwin implement it.
> 
> Thanks, I've put this on my TODO. The only problem is, without
> decorations, it is difficult to do some operations on the window, but
> I don't think that's such a big deal.

That's expected behaviour imho for fullscreen windows, i think they
shouldn't even be lowerable, but that's open for discussion :)


Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org


From smoynes at nexus.carleton.ca  Sat Mar 15 17:15:00 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Sat, 15 Mar 2003 17:15:00 -0500
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030315211247.GA22474@Otherland>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland>
Message-ID: <20030315221500.GH10629@marilyn>

* Arwed von Merkatz (v.merkatz at gmx.net) wrote:
> That's expected behaviour imho for fullscreen windows, i think they
> shouldn't even be lowerable, but that's open for discussion :)

Well, openbox 2 doesn't support that. I'll take a look at the EWMH
spec and see what they say.

-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra


From ben at orodu.net  Sat Mar 15 20:15:04 2003
From: ben at orodu.net (Ben Jansens)
Date: Sat, 15 Mar 2003 19:15:04 -0600
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030315221500.GH10629@marilyn>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn>
Message-ID: <20030316011504.GB27899@orodu.net>

On Sat, Mar 15, 2003 at 05:15:00PM -0500, smoynes at nexus.carleton.ca wrote:
> * Arwed von Merkatz (v.merkatz at gmx.net) wrote:
> > That's expected behaviour imho for fullscreen windows, i think they
> > shouldn't even be lowerable, but that's open for discussion :)
> 
> Well, openbox 2 doesn't support that. I'll take a look at the EWMH
> spec and see what they say.

He's right. I don't know if that was added at some point or I missed it,
however, Openbox should resize the window and raise it, similar to
maximizing, allowing it to be restored again when the state is removed.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030315/e38c4ec5/attachment.pgp>

From msw at cox.net  Mon Mar 17 01:53:58 2003
From: msw at cox.net (Marc Wilson)
Date: Sun, 16 Mar 2003 22:53:58 -0800
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030316011504.GB27899@orodu.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net>
Message-ID: <20030317065358.GB1492@moonkingdom.net>

On Sat, Mar 15, 2003 at 07:15:04PM -0600, Ben Jansens wrote:
> He's right. I don't know if that was added at some point or I missed it,
> however, Openbox should resize the window and raise it, similar to
> maximizing, allowing it to be restored again when the state is removed.

You may recall that we talked about this in-channel a few weeks ago because
of Debian's xawtv expecting this to work whenever it found a window manager
claiming to understand NETWM.

-- 
 Marc Wilson |     BOFH excuse #81: Please excuse me, I have to circuit
 msw at cox.net |     an AC line through my head to get this database
             |     working.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030316/6a17f160/attachment.pgp>

From msw at cox.net  Mon Mar 17 02:12:20 2003
From: msw at cox.net (Marc Wilson)
Date: Sun, 16 Mar 2003 23:12:20 -0800
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317065358.GB1492@moonkingdom.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net>
Message-ID: <20030317071220.GC1492@moonkingdom.net>

On Sun, Mar 16, 2003 at 10:53:58PM -0800, Marc Wilson wrote:
> On Sat, Mar 15, 2003 at 07:15:04PM -0600, Ben Jansens wrote:
> > He's right. I don't know if that was added at some point or I missed it,
> > however, Openbox should resize the window and raise it, similar to
> > maximizing, allowing it to be restored again when the state is removed.
> 
> You may recall that we talked about this in-channel a few weeks ago because
> of Debian's xawtv expecting this to work whenever it found a window manager
> claiming to understand NETWM.

And having tried the patch, xawtv is still not able to shift screen modes.
The window DOES maximize now, and the decorations go away, but that's all.
I think that might be an xawtv-ism, though... it might not shift if it
finds NETWM.  I tried to read it again and got a headache again.

Also, it looks like the patch tries to take into account the size of the
window frame, but after it turns off decorations, you can still see the
root window at the top and the left. :)

-- 
 Marc Wilson |     I do not find in orthodox Christianity one redeeming
 msw at cox.net |     feature.  - Thomas Jefferson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030316/f4bc395e/attachment.pgp>

From ben at orodu.net  Mon Mar 17 02:33:36 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 01:33:36 -0600
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317071220.GC1492@moonkingdom.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net>
Message-ID: <20030317073336.GC27899@orodu.net>

On Sun, Mar 16, 2003 at 11:12:20PM -0800, Marc Wilson wrote:
> On Sun, Mar 16, 2003 at 10:53:58PM -0800, Marc Wilson wrote:
> > On Sat, Mar 15, 2003 at 07:15:04PM -0600, Ben Jansens wrote:
> > > He's right. I don't know if that was added at some point or I missed it,
> > > however, Openbox should resize the window and raise it, similar to
> > > maximizing, allowing it to be restored again when the state is removed.
> > 
> > You may recall that we talked about this in-channel a few weeks ago because
> > of Debian's xawtv expecting this to work whenever it found a window manager
> > claiming to understand NETWM.
> 
> And having tried the patch, xawtv is still not able to shift screen modes.
> The window DOES maximize now, and the decorations go away, but that's all.
> I think that might be an xawtv-ism, though... it might not shift if it
> finds NETWM.  I tried to read it again and got a headache again.
> 
> Also, it looks like the patch tries to take into account the size of the
> window frame, but after it turns off decorations, you can still see the
> root window at the top and the left. :)

Theres been some discussion on the wm-spec list regarding vid modes and
fullscreen. And the conclusion seems to be that xawtv+metacity will work so
everything is just dandy. I may just remove FULLSCREEN from the advertised
supported atoms. Because the situation is rather rediculous IMO.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/3774acb3/attachment.pgp>

From msw at cox.net  Mon Mar 17 03:26:38 2003
From: msw at cox.net (Marc Wilson)
Date: Mon, 17 Mar 2003 00:26:38 -0800
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317073336.GC27899@orodu.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net> <20030317073336.GC27899@orodu.net>
Message-ID: <20030317082638.GD1492@moonkingdom.net>

On Mon, Mar 17, 2003 at 01:33:36AM -0600, Ben Jansens wrote:
> Theres been some discussion on the wm-spec list regarding vid modes and
> fullscreen. And the conclusion seems to be that xawtv+metacity will work so
> everything is just dandy. I may just remove FULLSCREEN from the advertised
> supported atoms. Because the situation is rather rediculous IMO.

If I remember correctly, doesn't xawtv just decide that if it sees NETWM,
then whatever feature it thinks it wants is available?  Didn't you
determine that FULLSCREEN wasn't being advertised now, but it was assuming
it was there anyway?  Have to find old irc log...

-- 
 Marc Wilson |     The world's great men have not commonly been great
 msw at cox.net |     scholars, nor its great scholars great men.  --
             |     Oliver Wendell Holmes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/e9e35c67/attachment.pgp>

From ben at orodu.net  Mon Mar 17 03:28:39 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 02:28:39 -0600
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317082638.GD1492@moonkingdom.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net> <20030317073336.GC27899@orodu.net> <20030317082638.GD1492@moonkingdom.net>
Message-ID: <20030317082839.GD27899@orodu.net>

On Mon, Mar 17, 2003 at 12:26:38AM -0800, Marc Wilson wrote:
> On Mon, Mar 17, 2003 at 01:33:36AM -0600, Ben Jansens wrote:
> > Theres been some discussion on the wm-spec list regarding vid modes and
> > fullscreen. And the conclusion seems to be that xawtv+metacity will work so
> > everything is just dandy. I may just remove FULLSCREEN from the advertised
> > supported atoms. Because the situation is rather rediculous IMO.
> 
> If I remember correctly, doesn't xawtv just decide that if it sees NETWM,
> then whatever feature it thinks it wants is available?  Didn't you
> determine that FULLSCREEN wasn't being advertised now, but it was assuming
> it was there anyway?  Have to find old irc log...

That was an xawtv bug yes. This patch would change that though, and suddenly
we have an Openbox bug (so says the wm-spec list so far) because it doesnt
check with the VidMode extension for the screen size.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/3a0f4f14/attachment.pgp>

From msw at cox.net  Mon Mar 17 03:39:12 2003
From: msw at cox.net (Marc Wilson)
Date: Mon, 17 Mar 2003 00:39:12 -0800
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317082839.GD27899@orodu.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net> <20030317073336.GC27899@orodu.net> <20030317082638.GD1492@moonkingdom.net> <20030317082839.GD27899@orodu.net>
Message-ID: <20030317083912.GE1492@moonkingdom.net>

On Mon, Mar 17, 2003 at 02:28:39AM -0600, Ben Jansens wrote:
> On Mon, Mar 17, 2003 at 12:26:38AM -0800, Marc Wilson wrote:
> > If I remember correctly, doesn't xawtv just decide that if it sees NETWM,
> > then whatever feature it thinks it wants is available?  Didn't you
> > determine that FULLSCREEN wasn't being advertised now, but it was assuming
> > it was there anyway?  Have to find old irc log...
> 
> That was an xawtv bug yes. This patch would change that though, and suddenly
> we have an Openbox bug (so says the wm-spec list so far) because it doesnt
> check with the VidMode extension for the screen size.

What's stopping xawtv from ordering X to change screen modes, then?  With
patch or without, the shift never occurs.  The only difference is that with
the patch, you get this black screen with an itty-bitty (relatively) TV
picture in the middle of it. ^_^

Or am I missing something and xawtv is expecting openbox to shift modes for
it?  When the last discussion took place, I understood that xawtv was
assuming openbox supported something it didn't, but I didn't understand how
far that assumption went (I guess).

-- 
 Marc Wilson |     QOTD: "I've always wanted to work in the Federal
 msw at cox.net |     Mint.  And then go on strike.  To make less money."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/828cce5c/attachment.pgp>

From ben at orodu.net  Mon Mar 17 03:42:19 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 02:42:19 -0600
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317083912.GE1492@moonkingdom.net>
References: <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net> <20030317073336.GC27899@orodu.net> <20030317082638.GD1492@moonkingdom.net> <20030317082839.GD27899@orodu.net> <20030317083912.GE1492@moonkingdom.net>
Message-ID: <20030317084219.GE27899@orodu.net>

On Mon, Mar 17, 2003 at 12:39:12AM -0800, Marc Wilson wrote:
> On Mon, Mar 17, 2003 at 02:28:39AM -0600, Ben Jansens wrote:
> > On Mon, Mar 17, 2003 at 12:26:38AM -0800, Marc Wilson wrote:
> > > If I remember correctly, doesn't xawtv just decide that if it sees NETWM,
> > > then whatever feature it thinks it wants is available?  Didn't you
> > > determine that FULLSCREEN wasn't being advertised now, but it was assuming
> > > it was there anyway?  Have to find old irc log...
> > 
> > That was an xawtv bug yes. This patch would change that though, and suddenly
> > we have an Openbox bug (so says the wm-spec list so far) because it doesnt
> > check with the VidMode extension for the screen size.
> 
> What's stopping xawtv from ordering X to change screen modes, then?  With
> patch or without, the shift never occurs.  The only difference is that with
> the patch, you get this black screen with an itty-bitty (relatively) TV
> picture in the middle of it. ^_^
> 
> Or am I missing something and xawtv is expecting openbox to shift modes for
> it?  When the last discussion took place, I understood that xawtv was
> assuming openbox supported something it didn't, but I didn't understand how
> far that assumption went (I guess).

xawtv + netwm fullscreen is in flux and whatever version you have is probly
not the same as CVS. Xawtv will change reses itself, and set the FULLSCREEN
state, and then openbox is sopposed to resize the window to fill only the
part of the screen visible with the mode change. Or so I beleive. But now
there's the RandR extension too. We'll see. Basically, the proper behavior
for changing modes with the fullscreen hint is not defined yet.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/2594b32e/attachment.pgp>

From v.merkatz at gmx.net  Mon Mar 17 05:15:47 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Mon, 17 Mar 2003 11:15:47 +0100
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317071220.GC1492@moonkingdom.net>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net>
Message-ID: <20030317101547.GA4016@Otherland>

On Sun, Mar 16, 2003 at 11:12:20PM -0800, Marc Wilson wrote:
> And having tried the patch, xawtv is still not able to shift screen modes.
> The window DOES maximize now, and the decorations go away, but that's all.
> I think that might be an xawtv-ism, though... it might not shift if it
> finds NETWM.  I tried to read it again and got a headache again.
> 
> Also, it looks like the patch tries to take into account the size of the
> window frame, but after it turns off decorations, you can still see the
> root window at the top and the left. :)

That may be sillyness on my part, and the fact that i still don't
understand completely how the code works.
Here are some apps that work with the patch but not without it:
- gthumb (checks for NET_WM_STATE_FULLSCREEN support, if not present uses
  its own fullscreen code, if present just sets the atom)
- galeon/epiphany

-- 
Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org


From ben at orodu.net  Mon Mar 17 16:41:28 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 15:41:28 -0600
Subject: [openbox] patch for NET_WM_STATE_FULLSCREEN support in openbox 2.3
In-Reply-To: <20030317101547.GA4016@Otherland>
References: <20030315201103.GA10266@Otherland> <20030315202622.GG10629@marilyn> <20030315211247.GA22474@Otherland> <20030315221500.GH10629@marilyn> <20030316011504.GB27899@orodu.net> <20030317065358.GB1492@moonkingdom.net> <20030317071220.GC1492@moonkingdom.net> <20030317101547.GA4016@Otherland>
Message-ID: <20030317214128.GF27899@orodu.net>

On Mon, Mar 17, 2003 at 11:15:47AM +0100, Arwed von Merkatz wrote:
> On Sun, Mar 16, 2003 at 11:12:20PM -0800, Marc Wilson wrote:
> > And having tried the patch, xawtv is still not able to shift screen modes.
> > The window DOES maximize now, and the decorations go away, but that's all.
> > I think that might be an xawtv-ism, though... it might not shift if it
> > finds NETWM.  I tried to read it again and got a headache again.
> > 
> > Also, it looks like the patch tries to take into account the size of the
> > window frame, but after it turns off decorations, you can still see the
> > root window at the top and the left. :)
> 
> That may be sillyness on my part, and the fact that i still don't
> understand completely how the code works.

I think what you want to do is use:
frame.rect.left() - frame.margin.left
frame.rect.top() - frame.margin.top
frame.rect.width() + frame.margin.left + frame.margin.right
frame.rect.height() + frame.margin.top + frame.margin.bottom

for the call to configure when going to fullscreen :)

> Here are some apps that work with the patch but not without it:
> - gthumb (checks for NET_WM_STATE_FULLSCREEN support, if not present uses
>   its own fullscreen code, if present just sets the atom)
> - galeon/epiphany

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/7766a4e9/attachment.pgp>

From pmartin at patm.net  Mon Mar 17 17:15:11 2003
From: pmartin at patm.net (Pat Martin)
Date: Mon, 17 Mar 2003 14:15:11 -0800
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030314185443.GE7849@orodu.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030314185443.GE7849@orodu.net>
Message-ID: <20030317221511.GA7386@patm.net>

I have compiled 2.3.0 with no problems but I still don't think I am
getting AntiAliased fonts. Any ideas? There is no option in the openbox
menu for xft does that mean that it is not compiling it with xft support
in? When I go into the rc file it has antialiasFonts as true (it was
that by default). I have a screenshot of fieron2 

http://www.pe.net/~pmartin/Screenshot.png

When I compare that to:

http://icculus.org/openbox/shots/full/xor_fieron2.png

There is a fair difference.

Fieron2 uses Veranda and that font is available in phoenix, mozilla and
gnome so I am not sure what the problem is.

Any suggestions would be welcome. 

I am running RedHat 8



On Fri, Mar 14, 2003 at 12:54:43PM -0600, Ben Jansens wrote:
> On Thu, Mar 13, 2003 at 10:45:29PM -0800, Pat Martin wrote:
> > 
> > I have been playing with openbox in RedHat 8 and I really like it. I
> > have a question concerning AntiAliased Fonts. I don't think openbox is
> > using AA fonts when needed I have added some true type fonts in the
> > ~/.font directory and they appear in mozilla and other apps just fine
> > but when different styles call for them the styles end up with really
> > small fonts and changing font sizes in the style doesn't seem to affect
> > it. I notice on the web site that it talks about a proper Xft file but
> > RedHat 8 doesn't use an Xft.conf file. Anyone have ideas how I can fix
> > this problem?
> 
> If you're using Openxbox 2.x with Xft 2, I'd recomment upgrading to 2.3.0.
> This is most likely your problem. 2.x had some issues with font loading that
> have been fixed.
> 
> Ben
> -- 
> I am damn unsatisfied to be killed in this way.
> 
> http://www.icculus.org/openbox/




From ben at orodu.net  Mon Mar 17 19:09:12 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 18:09:12 -0600
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030317221511.GA7386@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030314185443.GE7849@orodu.net> <20030317221511.GA7386@patm.net>
Message-ID: <20030318000912.GG27899@orodu.net>

On Mon, Mar 17, 2003 at 02:15:11PM -0800, Pat Martin wrote:
> I have compiled 2.3.0 with no problems but I still don't think I am
> getting AntiAliased fonts. Any ideas? There is no option in the openbox
> menu for xft does that mean that it is not compiling it with xft support
> in? When I go into the rc file it has antialiasFonts as true (it was
> that by default). I have a screenshot of fieron2 

# openbox -help
...
  Debugging                     No
  Shape:                        Yes
  Xft:                          Yes  <----
  Xinerama:                     Yes
  8bpp Ordered Dithering:       No
	  
Look at the config.log for more details about why Xft isn't being compiled
in, if it's not.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/8c0d7db2/attachment.pgp>

From pmartin at patm.net  Tue Mar 18 00:03:05 2003
From: pmartin at patm.net (Pat Martin)
Date: Mon, 17 Mar 2003 21:03:05 -0800
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030318000912.GG27899@orodu.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030314185443.GE7849@orodu.net> <20030317221511.GA7386@patm.net> <20030318000912.GG27899@orodu.net>
Message-ID: <20030318050305.GA7494@patm.net>


Ok so it is not compiled in. I looked in the config.log like you
suggested and found 


----clip

configure:5523: checking whether to build support for the Xft extension
configure:5535: result: version 2
configure:5543: checking for XftFontOpenXlfd in -lXft
configure:5576: g++ -o conftest  -I/usr/include/Xft2
-I/usr/include/freetype2 -I
/usr/X11R6/include   -g -O2  -I/usr/X11R6/include -Wall -W
-L/usr/X11R6/lib 
 -lSM -lICE conftest.cc -lXft    -L/usr/X11R6/lib -lX11  -lXext
 -L/usr/X11R6/li
 b -lXft2 -lfreetype -lXrender -lfontconfig   >&5
 /usr/bin/ld: cannot find -lXft

----clip

 Yet like I said I have other programs that use it succesfully. And when
 I do a locate I get:

-----clip

./etc/X11/XftConfig.README-OBSOLETE
 ./usr/lib/libXft.so.2
 ./usr/lib/libXft.so.2.0
 ./usr/lib/libXft2.so
 ./usr/share/man/man3/Xft.3x.gz
 ./usr/share/gtk-doc/html/pango/pango-Xft-Fonts-and-Rendering.html
 ./usr/X11R6/lib/libXft.so.1
 ./usr/X11R6/lib/libXft.so.1.2
 ./usr/X11R6/include/X11/Xft
 ./usr/X11R6/man/man3/Xft.3x.gz
 ./usr/include/Xft2
 ./usr/include/Xft2/X11/Xft
 ./usr/include/Xft2/X11/Xft/XftCompat.h
 ./usr/include/Xft2/X11/Xft/Xft.h

------clip

I tried search for similar things on the net but not luck.
 
As always any help is definately appreciated and thanks for the help so
far.


Thanks

Pat


On Mon, Mar 17, 2003 at 06:09:12PM -0600, Ben Jansens wrote:
> On Mon, Mar 17, 2003 at 02:15:11PM -0800, Pat Martin wrote:
> > I have compiled 2.3.0 with no problems but I still don't think I am
> > getting AntiAliased fonts. Any ideas? There is no option in the openbox
> > menu for xft does that mean that it is not compiling it with xft support
> > in? When I go into the rc file it has antialiasFonts as true (it was
> > that by default). I have a screenshot of fieron2 
> 
> # openbox -help
> ...
>   Debugging                     No
>   Shape:                        Yes
>   Xft:                          Yes  <----
>   Xinerama:                     Yes
>   8bpp Ordered Dithering:       No
> 	  
> Look at the config.log for more details about why Xft isn't being compiled
> in, if it's not.
> 
> Ben
> -- 
> I am damn unsatisfied to be killed in this way.
> 
> http://www.icculus.org/openbox/




From ben at orodu.net  Tue Mar 18 00:16:15 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 17 Mar 2003 23:16:15 -0600
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030318050305.GA7494@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030314185443.GE7849@orodu.net> <20030317221511.GA7386@patm.net> <20030318000912.GG27899@orodu.net> <20030318050305.GA7494@patm.net>
Message-ID: <20030318051615.GH27899@orodu.net>

On Mon, Mar 17, 2003 at 09:03:05PM -0800, Pat Martin wrote:
> 
> Ok so it is not compiled in. I looked in the config.log like you
> suggested and found 
> 
> 
> ----clip
> 
> configure:5523: checking whether to build support for the Xft extension
> configure:5535: result: version 2
> configure:5543: checking for XftFontOpenXlfd in -lXft
> configure:5576: g++ -o conftest  -I/usr/include/Xft2
> -I/usr/include/freetype2 -I
> /usr/X11R6/include   -g -O2  -I/usr/X11R6/include -Wall -W
> -L/usr/X11R6/lib 
>  -lSM -lICE conftest.cc -lXft    -L/usr/X11R6/lib -lX11  -lXext
>  -L/usr/X11R6/li
>  b -lXft2 -lfreetype -lXrender -lfontconfig   >&5
>  /usr/bin/ld: cannot find -lXft
> 
> ----clip
> 
>  Yet like I said I have other programs that use it succesfully. And when
>  I do a locate I get:
> 
> -----clip
> 
> ./etc/X11/XftConfig.README-OBSOLETE
>  ./usr/lib/libXft.so.2
>  ./usr/lib/libXft.so.2.0
>  ./usr/lib/libXft2.so
>  ./usr/share/man/man3/Xft.3x.gz
>  ./usr/share/gtk-doc/html/pango/pango-Xft-Fonts-and-Rendering.html
>  ./usr/X11R6/lib/libXft.so.1
>  ./usr/X11R6/lib/libXft.so.1.2
>  ./usr/X11R6/include/X11/Xft
>  ./usr/X11R6/man/man3/Xft.3x.gz
>  ./usr/include/Xft2
>  ./usr/include/Xft2/X11/Xft
>  ./usr/include/Xft2/X11/Xft/XftCompat.h
>  ./usr/include/Xft2/X11/Xft/Xft.h

Its looking for a libXft.so, but yours is called libXft2.so. FreeBSD was teh
only other platform to do this until recently, they fixed theirs. I guess
RedHat sits alone, didn't realise they did too.

mv'ing or ln'ing that to libXft.so should fix that problem. I think the
headers should work from what I see.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030317/442fa58c/attachment.pgp>

From pmartin at patm.net  Tue Mar 18 01:47:47 2003
From: pmartin at patm.net (Pat Martin)
Date: Mon, 17 Mar 2003 22:47:47 -0800
Subject: [openbox] Xft and RedHat 8
In-Reply-To: <20030318051615.GH27899@orodu.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030314185443.GE7849@orodu.net> <20030317221511.GA7386@patm.net> <20030318000912.GG27899@orodu.net> <20030318050305.GA7494@patm.net> <20030318051615.GH27899@orodu.net>
Message-ID: <20030318064747.GA7565@patm.net>


That did it! Xft support is now enabled and I like the look!

Thank you very much!

On Mon, Mar 17, 2003 at 11:16:15PM -0600, Ben Jansens wrote:
> On Mon, Mar 17, 2003 at 09:03:05PM -0800, Pat Martin wrote:
> > 
> > Ok so it is not compiled in. I looked in the config.log like you
> > suggested and found 
> > 
> > 
> > ----clip
> > 
> > configure:5523: checking whether to build support for the Xft extension
> > configure:5535: result: version 2
> > configure:5543: checking for XftFontOpenXlfd in -lXft
> > configure:5576: g++ -o conftest  -I/usr/include/Xft2
> > -I/usr/include/freetype2 -I
> > /usr/X11R6/include   -g -O2  -I/usr/X11R6/include -Wall -W
> > -L/usr/X11R6/lib 
> >  -lSM -lICE conftest.cc -lXft    -L/usr/X11R6/lib -lX11  -lXext
> >  -L/usr/X11R6/li
> >  b -lXft2 -lfreetype -lXrender -lfontconfig   >&5
> >  /usr/bin/ld: cannot find -lXft
> > 
> > ----clip
> > 
> >  Yet like I said I have other programs that use it succesfully. And when
> >  I do a locate I get:
> > 
> > -----clip
> > 
> > ./etc/X11/XftConfig.README-OBSOLETE
> >  ./usr/lib/libXft.so.2
> >  ./usr/lib/libXft.so.2.0
> >  ./usr/lib/libXft2.so
> >  ./usr/share/man/man3/Xft.3x.gz
> >  ./usr/share/gtk-doc/html/pango/pango-Xft-Fonts-and-Rendering.html
> >  ./usr/X11R6/lib/libXft.so.1
> >  ./usr/X11R6/lib/libXft.so.1.2
> >  ./usr/X11R6/include/X11/Xft
> >  ./usr/X11R6/man/man3/Xft.3x.gz
> >  ./usr/include/Xft2
> >  ./usr/include/Xft2/X11/Xft
> >  ./usr/include/Xft2/X11/Xft/XftCompat.h
> >  ./usr/include/Xft2/X11/Xft/Xft.h
> 
> Its looking for a libXft.so, but yours is called libXft2.so. FreeBSD was teh
> only other platform to do this until recently, they fixed theirs. I guess
> RedHat sits alone, didn't realise they did too.
> 
> mv'ing or ln'ing that to libXft.so should fix that problem. I think the
> headers should work from what I see.
> 
> Ben
> -- 
> I am damn unsatisfied to be killed in this way.
> 
> http://www.icculus.org/openbox/




From smoynes at nexus.carleton.ca  Thu Mar 20 23:34:16 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Thu, 20 Mar 2003 23:34:16 -0500
Subject: [openbox] unexpandTilde()
In-Reply-To: <Pine.LNX.4.44.0302251436520.5873-200000@aratinga.cosy.sbg.ac.at>
References: <Pine.LNX.4.44.0302251436520.5873-200000@aratinga.cosy.sbg.ac.at>
Message-ID: <20030321043416.GN10629@marilyn>

* Bernhard Kepplinger (bkeppl at cosy.sbg.ac.at) wrote:
> Hi!
> 
> Just wrote a patch that makes openbox store the stylefilepath
> relative to ~ (if possible).  thus one can use the same rc file in
> different home directories (/home/gcc4fun at home and
> /home/stud1/bkeppl at universitiy) without loosing the current
> theme.
> 
> bernhard

I just wanted to let you know I've applied and committed this to
CVS. Sorry it took so long. 

Thanks!
-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra


From smoynes at nexus.carleton.ca  Sat Mar 22 13:23:00 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Sat, 22 Mar 2003 13:23:00 -0500
Subject: [ob3] config stuff
Message-ID: <20030322182300.GC30077@marilyn>

Here's a patch for the config system.

It allows the plugins to specify the config parameters they take and
basic information about the type of data. They can register parameter
names and specify if they are strings or integers. If they are
strings, they can either be free form, or given a list of valid
strings using config_def_add_value().
There's currently plenty of issues with memory handling, but I guess
we can fix that up when we decide how to handle reloading the config
file and plugins.
-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra
-------------- next part --------------
? config-def.diff
? openbox-2_3
? swigpatch.diff
? woodblocks-first-patch.diff
? c/.deps
? c/Makefile
? c/Makefile.in
? data/styles/Makefile
? data/styles/Makefile.in
? engines/ob/Makefile
? engines/ob/Makefile.in
? engines/openbox/semantic.cache
? engines/pwm/.deps
? engines/pwm/.libs
? engines/pwm/Makefile
? engines/pwm/Makefile.in
? engines/pwm/pwm.la
? engines/pwm/pwm.lo
? intl/Makefile
? kernel/menu.c
? kernel/menu.h
? kernel/menunotes
? kernel/ob3
? kernel/semantic.cache
? m4/Makefile
? m4/Makefile.in
? otk/Makefile.in
? otk/otk.py
? otk/otk_wrap.cc
? plugins/resistance.lo
? python/Makefile
? python/Makefile.in
? python/hooks/Makefile
? python/hooks/Makefile.in
? python/ob/Makefile
? python/ob/Makefile.in
? render/semantic.cache
? scripts/Makefile.in
? src/Makefile.in
? src/ob.py
? src/openbox_wrap.cc
? util/.deps
? util/Makefile
? util/Makefile.in
? util/epist/.deps
? util/epist/Makefile
? util/epist/Makefile.in
Index: bootstrap
===================================================================
RCS file: /cvs/cvsroot/openbox/bootstrap,v
retrieving revision 1.13
diff -p -u -r1.13 bootstrap
--- bootstrap	2003/03/16 21:11:38	1.13
+++ bootstrap	2003/03/22 18:14:19
@@ -6,9 +6,9 @@ sh() {
 
 sh autopoint --force # for GNU gettext
 sh libtoolize --copy --force --automake
-sh aclocal -I m4
+sh aclocal -I m4 -I /usr/local/share/aclocal
 #sh autoheader
-sh autoconf
+sh autoconf 
 sh automake --foreign --include-deps --add-missing --copy
 
 echo
Index: kernel/config.c
===================================================================
RCS file: /cvs/cvsroot/openbox/kernel/config.c,v
retrieving revision 1.1
diff -p -u -r1.1 config.c
--- kernel/config.c	2003/03/22 14:41:19	1.1
+++ kernel/config.c	2003/03/22 18:14:19
@@ -4,7 +4,15 @@
 #  include <stdio.h>
 #endif
 
-static GSList *config = NULL;
+void config_free_entry(gpointer entry);
+void config_set_entry(char *name, ConfigValueType type, ConfigValue value);
+void print_config(GQuark q, gpointer data, gpointer fonk){
+    ConfigDefEntry *e = (ConfigDefEntry *)data;
+    g_message("config: %s %d\n", e->name, e->hasList);
+}
+
+static GData *config = NULL;
+static GData *config_def = NULL;
 
 /* provided by cparse.l */
 void cparse_go(FILE *);
@@ -12,6 +20,18 @@ void cparse_go(FILE *);
 
 void config_startup()
 {
+    /* test definition */
+    ConfigDefEntry *def;
+
+    config_def_new(&def, "test", Config_String);
+    config_def_set(def);
+
+    config_def_new(&def, "testlist", Config_String);
+    config_def_add_value(def, "one");
+    config_def_add_value(def, "two");
+    config_def_set(def);
+
+    g_datalist_foreach(&config_def, print_config, NULL);
 }
 
 void config_shutdown()
@@ -32,6 +52,97 @@ void config_parse()
 
 gboolean config_set(char *name, ConfigValueType type, ConfigValue value)
 {
+    ConfigDefEntry *def;
+     
     g_message("Setting %s\n", name);
+
+    g_datalist_foreach(&config_def, print_config, NULL);
+    def = (ConfigDefEntry *) g_datalist_get_data(&config_def, g_strdown(name));
+
+    if (def == NULL)
+    {
+        g_message("Invalid config option '%s'\n", name);
+    }
+    else
+    {
+        if (def->hasList)
+        {
+            gboolean found = FALSE;
+            GSList *i = def->values;
+
+            do
+            {
+                if (g_strcasecmp((char *)i->data, value.string) == 0)
+                {
+                    found = TRUE;
+                    break;
+                }
+            }while( (i = g_slist_next(i)) );
+            
+
+            if (found)
+                config_set_entry(name, type, value);
+            else
+                g_message("Invalid value '%s' for config option '%s'",
+                          value.string, name);
+        }
+
+        config_set_entry(name, type, value);
+    }
+    return TRUE;
+}
+
+void config_set_entry(char *name, ConfigValueType type, ConfigValue value)
+{
+    ConfigEntry *entry = NULL;
+
+    
+    entry = g_malloc(sizeof(ConfigEntry));
+    entry->name = g_strdup(name);
+    entry->type = type;
+    if (type == Config_String)
+        entry->value.string = g_strdup(value.string);
+    else
+        entry->value = value;
+
+    g_datalist_set_data_full(&config, name, entry, config_free_entry);
+}
+
+void config_free_entry(gpointer p)
+{
+    ConfigEntry *entry = (ConfigEntry *)p;
+    g_free(entry->name);
+    entry->name = NULL;
+    if(entry->type == Config_String)
+        g_free(entry->value.string);
+    entry->value.string = NULL;
+    g_free(entry);
+    entry = NULL;
+}
+
+void config_def_new(ConfigDefEntry **entry, char *name, ConfigValueType type)
+{
+    *entry = g_malloc(sizeof(ConfigDefEntry));
+    (*entry)->name = name;
+    (*entry)->hasList = FALSE;
+    (*entry)->type = type;
+    (*entry)->values = NULL;
+}
+
+gboolean config_def_add_value(ConfigDefEntry *entry, char *value)
+{
+    if (entry->type != Config_String) {
+        g_message("Error: Tried adding value to non-string config definition\n");
+        return FALSE;
+    }
+
+    entry->hasList = TRUE;
+    entry->values = g_slist_append(entry->values, value);
+    return TRUE;
+}
+
+gboolean config_def_set(ConfigDefEntry *entry)
+{
+    g_datalist_set_data(&config_def, g_strdown(entry->name), entry);
     return TRUE;
 }
Index: kernel/config.h
===================================================================
RCS file: /cvs/cvsroot/openbox/kernel/config.h,v
retrieving revision 1.1
diff -p -u -r1.1 config.h
--- kernel/config.h	2003/03/22 14:41:19	1.1
+++ kernel/config.h	2003/03/22 18:14:19
@@ -19,10 +19,23 @@ typedef struct {
     ConfigValue value;
 } ConfigEntry;
 
+typedef struct {
+    char *name;
+    ConfigValueType type;
+    /* if it is a string type optionally provide a list of valid strings */
+    gboolean hasList;
+    GSList *values;
+} ConfigDefEntry;
+
 void config_startup();
 void config_shutdown();
 
 gboolean config_set(char *name, ConfigValueType type, ConfigValue value);
+
+/* XXX: aiee. what to do about memory? */
+void config_def_new(ConfigDefEntry **entry, char *name, ConfigValueType type);
+gboolean config_def_add_value(ConfigDefEntry *entry, char *value);
+gboolean config_def_set(ConfigDefEntry *entry);
 
 void config_parse();
 

From ulerich at psu.edu  Sat Mar 22 18:33:35 2003
From: ulerich at psu.edu (Rhys Ulerich)
Date: Sat, 22 Mar 2003 18:33:35 -0500
Subject: Using Nautilus w/ OpenBox
Message-ID: <20030322233335.GC22796@jazz.me.psu.edu>

The main OpenBox page indicates that Nautilus can be used with OpenBox.
Running a straight 'nautilus' or 'nautilus ?-no-desktop' winds up with my
root window managed by nautilus to the point where I can't right click
to bring up my openbox menu.  I've been looking around but can't find
out how to circumvent this problem.  Suggestions?

Thank you,
Rhys


From v.merkatz at gmx.net  Sat Mar 22 18:45:46 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Sun, 23 Mar 2003 00:45:46 +0100
Subject: [openbox] Using Nautilus w/ OpenBox
In-Reply-To: <20030322233335.GC22796@jazz.me.psu.edu>
References: <20030322233335.GC22796@jazz.me.psu.edu>
Message-ID: <20030322234546.GA16004@Otherland>

I had a similar problem with rox-filer, i worked around it by changing
the menus to only have one menu on middle click with the following
setting in ~/.openbox/rc

session.screen0.rootMenuButton: Middle

then i included the workspace menu in the root menu.


On Sat, Mar 22, 2003 at 06:33:35PM -0500, Rhys Ulerich wrote:
> The main OpenBox page indicates that Nautilus can be used with OpenBox.
> Running a straight 'nautilus' or 'nautilus ?-no-desktop' winds up with my
> root window managed by nautilus to the point where I can't right click
> to bring up my openbox menu.  I've been looking around but can't find
> out how to circumvent this problem.  Suggestions?
> 
> Thank you,
> Rhys
> 
> 

-- 
Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org


From ajar at katanalynx.dyndns.org  Sat Mar 22 22:04:18 2003
From: ajar at katanalynx.dyndns.org (Ava Arachne Jarvis)
Date: Sat, 22 Mar 2003 21:04:18 -0600
Subject: [openbox] Using Nautilus w/ OpenBox
In-Reply-To: <20030322234546.GA16004@Otherland>
References: <20030322233335.GC22796@jazz.me.psu.edu> <20030322234546.GA16004@Otherland>
Message-ID: <20030323030418.GL8222@dan0032.urh.uiuc.edu>

[Arwed von Merkatz - Sat, 22 Mar 2003 05:45:51 PM CST]
> I had a similar problem with rox-filer, i worked around it by changing
> the menus to only have one menu on middle click with the following
> setting in ~/.openbox/rc
> 
> session.screen0.rootMenuButton: Middle
> 
> then i included the workspace menu in the root menu.

There's also a patch floating around for Rox-Filer so that third-button
clicks will be passed to the window manager correctly.  I forget what
version it was for, though.


-- 
| Trust in Allah, but tie your camel.
| 		-- Arabian proverb


From dpb at clara.co.uk  Sun Mar 23 13:13:09 2003
From: dpb at clara.co.uk (David Barr)
Date: Sun, 23 Mar 2003 18:13:09 +0000
Subject: [openbox] Using Nautilus w/ OpenBox
In-Reply-To: <20030323030418.GL8222@dan0032.urh.uiuc.edu>
References: <20030322233335.GC22796@jazz.me.psu.edu> <20030322234546.GA16004@Otherland> <20030323030418.GL8222@dan0032.urh.uiuc.edu>
Message-ID: <3E7DF935.2020709@clara.co.uk>

Ava Arachne Jarvis wrote:

>[Arwed von Merkatz - Sat, 22 Mar 2003 05:45:51 PM CST]
>  
>
>>I had a similar problem with rox-filer, i worked around it by changing
>>the menus to only have one menu on middle click with the following
>>setting in ~/.openbox/rc
>>
>>session.screen0.rootMenuButton: Middle
>>
>>then i included the workspace menu in the root menu.
>>    
>>
>
>There's also a patch floating around for Rox-Filer so that third-button
>clicks will be passed to the window manager correctly.  I forget what
>version it was for, though.
>
>
>  
>
i don't know where this came from but here's said patch for anyone 
interested, it seems to work ok on cvs and most 1.4 versions
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rox-1.3.x-blackbox.patch
URL: <http://icculus.org/pipermail/openbox/attachments/20030323/c1d75c0f/attachment.diff>

From lists at siology.net  Sun Mar 23 22:23:28 2003
From: lists at siology.net (lists)
Date: Mon, 24 Mar 2003 03:23:28 +0000
Subject: irc, tabs, Hotkeys & Tile/Cascade
Message-ID: <20030324032328.36e91af0.lists@siology.net>

 - irc channel on freenode removed, so where is it now? (sorry, couldn't see in FAQ)
 - tabs not in .plan? (as in Fluxbox) (expecting you've heard this before :/ )
 - Tile and cascade windows set to a hotkey possible? by using an external program of some sort perhaps?
- Xinerama?

 Many thanks



From ben at orodu.net  Sun Mar 23 23:46:35 2003
From: ben at orodu.net (Ben Jansens)
Date: Sun, 23 Mar 2003 22:46:35 -0600
Subject: [openbox] irc, tabs, Hotkeys & Tile/Cascade
In-Reply-To: <20030324032328.36e91af0.lists@siology.net>
References: <20030324032328.36e91af0.lists@siology.net>
Message-ID: <20030324044635.GK27899@orodu.net>

On Mon, Mar 24, 2003 at 03:23:28AM +0000, lists wrote:
>  - irc channel on freenode removed, so where is it now? (sorry, couldn't see in FAQ)

This is right on the front page http://icculus.org/openbox. :)

>  - tabs not in .plan? (as in Fluxbox) (expecting you've heard this before :/ )

No, that's Fluxbox. We are not.

>  - Tile and cascade windows set to a hotkey possible? by using an external program of some sort perhaps?

This kind of thing is being worked into the plan with openbox3. You can't do
it without an external program (which could do it!) in openbox2.

> - Xinerama?

There is support in openbox2. Build with --enable-xinerama.

Ciao,
Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030323/3337c3f2/attachment.pgp>

From msw at cox.net  Mon Mar 24 01:23:58 2003
From: msw at cox.net (Marc Wilson)
Date: Sun, 23 Mar 2003 22:23:58 -0800
Subject: [openbox] irc, tabs, Hotkeys & Tile/Cascade
In-Reply-To: <20030324032328.36e91af0.lists@siology.net>
References: <20030324032328.36e91af0.lists@siology.net>
Message-ID: <20030324062358.GA7065@moonkingdom.net>

On Mon, Mar 24, 2003 at 03:23:28AM +0000, lists wrote:
>  - irc channel on freenode removed, so where is it now? (sorry, couldn't see in FAQ)

It's at irc.oftc.net.  Funny, it's right there on the openbox site.

>  - tabs not in .plan? (as in Fluxbox) (expecting you've heard this before :/ )

Gods, we can all only hope not.  Tabs might theoretically be a neat thing,
but whyinhell would you want anything resembling Fluxbox's broken
interpretation?  The way pwm does them might be nice, where they replace
the titlebar....

People who want Fluxbox brokenness should use Fluxbox.

>  - Tile and cascade windows set to a hotkey possible? by using an
>  external program of some sort perhaps?

I wish.

> - Xinerama?

Openbox2 already supports the most common Xinerama brokennesses... just
build it with --enable-xinerama.  Why people call that "support" when all
you're doing is breaking the logical and consistent X behavior is beyond
me.

-- 
 Marc Wilson |     What's so funny?
 msw at cox.net |


From pmartin at patm.net  Wed Mar 26 17:28:35 2003
From: pmartin at patm.net (Pat Martin)
Date: Wed, 26 Mar 2003 14:28:35 -0800
Subject: Keyboard control of root menu
In-Reply-To: <20030314064529.GA5717@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net>
Message-ID: <20030326222835.GA11130@patm.net>


Hello all,

I have been playing with the configuration of epist and have a question
about showRootMenu, it brings up the Root Menu but then I cannot
manipulate it with the keyboard which kind of defeats the purpose of the
command doesn't it. Unless of course it is just there for when you can't
right click on the desktop and get the root menu. Is there any plans on
putting that functionality into openbox? 

Great window manager.

Thanks.

Pat Martin



From msw at cox.net  Wed Mar 26 22:58:59 2003
From: msw at cox.net (Marc Wilson)
Date: Wed, 26 Mar 2003 19:58:59 -0800
Subject: [openbox] Keyboard control of root menu
In-Reply-To: <20030326222835.GA11130@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030326222835.GA11130@patm.net>
Message-ID: <20030327035859.GN7065@moonkingdom.net>

On Wed, Mar 26, 2003 at 02:28:35PM -0800, Pat Martin wrote:
> I have been playing with the configuration of epist and have a question
> about showRootMenu, it brings up the Root Menu but then I cannot
> manipulate it with the keyboard which kind of defeats the purpose of the
> command doesn't it.

It's there so that you can pop the menu without having to have access to
the root window.

-- 
 Marc Wilson |     Don't hit the keys so hard, it hurts.
 msw at cox.net |


From smoynes at nexus.carleton.ca  Wed Mar 26 23:14:43 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Wed, 26 Mar 2003 23:14:43 -0500
Subject: [openbox] Keyboard control of root menu
In-Reply-To: <20030326222835.GA11130@patm.net>
References: <Pine.SOL.4.33.0302051157310.469-100000@panther.cs.ucla.edu> <20030206004021.GA8496@patm.net> <20030206004439.GX1303@dan0032.urh.uiuc.edu> <20030314064529.GA5717@patm.net> <20030326222835.GA11130@patm.net>
Message-ID: <20030327041443.GG2796@marilyn>

* Pat Martin (pmartin at patm.net) wrote:
> I have been playing with the configuration of epist and have a
> question about showRootMenu, it brings up the Root Menu but then I
> cannot manipulate it with the keyboard which kind of defeats the
> purpose of the command doesn't it. Unless of course it is just there
> for when you can't right click on the desktop and get the root
> menu. Is there any plans on putting that functionality into openbox?

The keybinding is there to work around rude applications that don't
pass the clicks on to the window manager. There are no plans to add
menu navigation using the keyboard to openbox 2. I am open to patches
though.
-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra


From thomas.loescher at gmx.de  Thu Mar 27 15:00:15 2003
From: thomas.loescher at gmx.de (Thomas Loescher)
Date: Thu, 27 Mar 2003 21:00:15 +0100
Subject: some problems with rox and openbox
Message-ID: <20030327210015.3305010a.thomas.loescher@gmx.de>

dear openbox users/developers,

at first, thank you developing such a small and fast windowmanager.

It seems to be the one I could use in the future, small, fast and compatible with the most (all?) blackbox compatible programs. Currently I'm using icewm, but I have there some problem wich are seem to be harder to resolve, so I'm thinking about changing the wm.
O.K. back to openbox:
I red on your website, that openbox should be compatible with rox. That's really nice, because I linke rox very much.
 But there seems to be a problem with using rox. I don't know if it's an openbox problem, but I don't have the problem with rox and icewm, so I try to solve my problem at first here ;-)
When I start rox from a xterm inside a running openbox (for testing purposes only) and after that I change the openbox style, everytime rox crashes. I'm using the most recent version of rox and openbox 2.3
Is this a known problem?

Second (also rox related):
When I open the openbox root menu (rox is running) the menu will not be kept open. It disappears immediately after releasing the mousebutton. But when I move the mouse pointer away from the menu (mousebutton is keeping pressed) and I release the mouse button after moving the pointer away the menu will stay on desktop and I can use it.
Is this a settings problem? Where can I change this behavior?
(is it possible, thta the menu-problem is a *box-windowmamnager problem? Because I had the same behavior with fluxbox.)

Update: O.K. before sending this email I red on the rox-website something about the problems of the *box-wm with rox. So it seems that openbox has still the same problems. Is that right? will this problem be fixed in the future? 

Sorry for starting posting in this ml with openbox problem (perhaps not real openbox problems) but I would like to use openbox together with rox, and at the moment it doesn't work really good.



Thanks for reading this and best regards

from switzerland

Thomas


From v.merkatz at gmx.net  Thu Mar 27 15:13:18 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Thu, 27 Mar 2003 21:13:18 +0100
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327210015.3305010a.thomas.loescher@gmx.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
Message-ID: <20030327201318.GA28170@Otherland>

Just a question, are you using rox 1.2.x or rox 1.3.x?
rox 1.3.7 works fine with openbox here

-- 
Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org


From thomas.loescher at gmx.de  Thu Mar 27 15:20:20 2003
From: thomas.loescher at gmx.de (Thomas Loescher)
Date: Thu, 27 Mar 2003 21:20:20 +0100
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327201318.GA28170@Otherland>
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
	<20030327201318.GA28170@Otherland>
Message-ID: <20030327212020.530dbe62.thomas.loescher@gmx.de>

Hi,
woah!
what a fast reply!
Thanks for this fast reply.
sorry I forgot to tell the version.
I'm using rox 1.3.8 the most recent version from rox.sf.net
That's really strange.
Why it doesn't work on my computer?
Do you have some "special" settings for rox or openbox?

regards

Thomas

On Thu, 27 Mar 2003 21:13:18 +0100
Arwed von Merkatz <v.merkatz at gmx.net> wrote:

> Just a question, are you using rox 1.2.x or rox 1.3.x?
> rox 1.3.7 works fine with openbox here
> 
> -- 
> Arwed v. Merkatz
> Grimoire Guru for video
> Sourcemage GNU/Linux
> http://www.sourcemage.org
> 


From v.merkatz at gmx.net  Thu Mar 27 15:34:24 2003
From: v.merkatz at gmx.net (Arwed von Merkatz)
Date: Thu, 27 Mar 2003 21:34:24 +0100
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327212020.530dbe62.thomas.loescher@gmx.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de> <20030327201318.GA28170@Otherland> <20030327212020.530dbe62.thomas.loescher@gmx.de>
Message-ID: <20030327203424.GA374@Otherland>

On Thu, Mar 27, 2003 at 09:20:20PM +0100, Thomas Loescher wrote:
> Hi,
> woah!
> what a fast reply!
> Thanks for this fast reply.
> sorry I forgot to tell the version.
> I'm using rox 1.3.8 the most recent version from rox.sf.net
> That's really strange.
> Why it doesn't work on my computer?
> Do you have some "special" settings for rox or openbox?

I don't think i have anything special, i changed openbox to open the
root menu on middle click and disabled the right click menu, so i can
use the rox right-click menu.
Rox does have some "Window manager problems" options under
'Compatibility', not sure if those could cause your problems, i have all
of them turned off.

-- 
Arwed v. Merkatz
Grimoire Guru for video
Sourcemage GNU/Linux
http://www.sourcemage.org


From thomas.loescher at gmx.de  Thu Mar 27 15:55:17 2003
From: thomas.loescher at gmx.de (Thomas Loescher)
Date: Thu, 27 Mar 2003 21:55:17 +0100
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327203424.GA374@Otherland>
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
	<20030327201318.GA28170@Otherland>
	<20030327212020.530dbe62.thomas.loescher@gmx.de>
	<20030327203424.GA374@Otherland>
Message-ID: <20030327215517.648821f0.thomas.loescher@gmx.de>

> 
> I don't think i have anything special, i changed openbox to open the
> root menu on middle click and disabled the right click menu, so i can
> use the rox right-click menu.
> Rox does have some "Window manager problems" options under
> 'Compatibility', not sure if those could cause your problems, i have all
> of them turned off.
> 
hm...
O.k. it seems, that I should move the menu from the second mousebutton to the third (the third work in the right way,  I tested it now, only the second has the behavior I told in the first post)

But there was a second strnge thing.
I teste dchanging style in openbox while having rox running and it worked!
Then I played with the rox settings (I enabled  "ignore wm control over pinboard and panel" in compatibility settings -> don't know why) and after that rox crashed while changing settings. I immediately disabled this checkbox in rox but it continues crashing...
Strange.. (sometimes I think, that there must be a kind of intelligent life in my computer)

But anyway, thank you for your help the rest of configuration and learning openbox should be done by myself
 A lst question: does the bbox configuration tools (e.g. whitebox) work together with openbox? especially for menu-configuration and also for the wm settings?

best regards

Thomas


From ben at orodu.net  Thu Mar 27 16:34:08 2003
From: ben at orodu.net (Ben Jansens)
Date: Thu, 27 Mar 2003 15:34:08 -0600
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327215517.648821f0.thomas.loescher@gmx.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de> <20030327201318.GA28170@Otherland> <20030327212020.530dbe62.thomas.loescher@gmx.de> <20030327203424.GA374@Otherland> <20030327215517.648821f0.thomas.loescher@gmx.de>
Message-ID: <20030327213408.GQ27899@orodu.net>

On Thu, Mar 27, 2003 at 09:55:17PM +0100, Thomas Loescher wrote:
> > 
> > I don't think i have anything special, i changed openbox to open the
> > root menu on middle click and disabled the right click menu, so i can
> > use the rox right-click menu.
> > Rox does have some "Window manager problems" options under
> > 'Compatibility', not sure if those could cause your problems, i have all
> > of them turned off.
> > 
> hm...
> O.k. it seems, that I should move the menu from the second mousebutton to the third (the third work in the right way,  I tested it now, only the second has the behavior I told in the first post)
> 
> But there was a second strnge thing.
> I teste dchanging style in openbox while having rox running and it worked!
> Then I played with the rox settings (I enabled  "ignore wm control over pinboard and panel" in compatibility settings -> don't know why) and after that rox crashed while changing settings. I immediately disabled this checkbox in rox but it continues crashing...
> Strange.. (sometimes I think, that there must be a kind of intelligent life in my computer)
> 
> But anyway, thank you for your help the rest of configuration and learning openbox should be done by myself
>  A lst question: does the bbox configuration tools (e.g. whitebox) work together with openbox? especially for menu-configuration and also for the wm settings?

They dont represent all the options in the rc file. But they will work for
editing the menu, as the menu format has not changed. For style editing, I'd
recommend using Stylebox
http://icculus.org/openbox/phpwiki/index.php/OpenboxStyles

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030327/40a6f5ff/attachment.pgp>

From thomas.loescher at gmx.de  Thu Mar 27 17:32:16 2003
From: thomas.loescher at gmx.de (Thomas Loescher)
Date: Thu, 27 Mar 2003 23:32:16 +0100
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327213408.GQ27899@orodu.net>
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
	<20030327201318.GA28170@Otherland>
	<20030327212020.530dbe62.thomas.loescher@gmx.de>
	<20030327203424.GA374@Otherland>
	<20030327215517.648821f0.thomas.loescher@gmx.de>
	<20030327213408.GQ27899@orodu.net>
Message-ID: <20030327233216.56862f9c.thomas.loescher@gmx.de>

> 
> They dont represent all the options in the rc file. But they will work for
> editing the menu, as the menu format has not changed. For style editing, I'd
> recommend using Stylebox
> http://icculus.org/openbox/phpwiki/index.php/OpenboxStyles
> 
thanks for this tip.

So it seems that for editing the generally behavior of openbox I have to use vi or something else?

Thomas


From ben at orodu.net  Fri Mar 28 06:10:25 2003
From: ben at orodu.net (Ben Jansens)
Date: Fri, 28 Mar 2003 05:10:25 -0600
Subject: [openbox] some problems with rox and openbox
In-Reply-To: <20030327233216.56862f9c.thomas.loescher@gmx.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de> <20030327201318.GA28170@Otherland> <20030327212020.530dbe62.thomas.loescher@gmx.de> <20030327203424.GA374@Otherland> <20030327215517.648821f0.thomas.loescher@gmx.de> <20030327213408.GQ27899@orodu.net> <20030327233216.56862f9c.thomas.loescher@gmx.de>
Message-ID: <20030328111025.GS27899@orodu.net>

On Thu, Mar 27, 2003 at 11:32:16PM +0100, Thomas Loescher wrote:
> > 
> > They dont represent all the options in the rc file. But they will work for
> > editing the menu, as the menu format has not changed. For style editing, I'd
> > recommend using Stylebox
> > http://icculus.org/openbox/phpwiki/index.php/OpenboxStyles
> > 
> thanks for this tip.
> 
> So it seems that for editing the generally behavior of openbox I have to use vi or something else?

Most of the options are available in the configuration menu (which is found
in the default root menu).

http://icculus.org/openbox/rc.php is a guide to the options if you want to 
tackle any by hand.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030328/ab4c6307/attachment.pgp>

From mfabian at suse.de  Fri Mar 28 08:35:24 2003
From: mfabian at suse.de (Mike FABIAN)
Date: Fri, 28 Mar 2003 14:35:24 +0100
Subject: Patch: Typo in nls/ko_KR/Makefile.am
In-Reply-To: <20030327210015.3305010a.thomas.loescher@gmx.de> (Thomas
 Loescher's message of "Thu, 27 Mar 2003 21:00:15 +0100")
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
Message-ID: <s3t4r5n62cj.fsf@magellan.suse.de>


There is a typo on nls/ko_KR/Makefile.am which causes Korean
translations to be installed as /usr/share/openbox/ko_KO where they
cannot be found.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: openbox-2.2.3-ko_KR.diff
Type: text/x-patch
Size: 769 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030328/4c806dd6/attachment.bin>
-------------- next part --------------

-- 
Mike Fabian   <mfabian at suse.de>   http://www.suse.de/~mfabian
?????????????

From smoynes at nexus.carleton.ca  Fri Mar 28 09:27:07 2003
From: smoynes at nexus.carleton.ca (smoynes at nexus.carleton.ca)
Date: Fri, 28 Mar 2003 09:27:07 -0500
Subject: [openbox] Patch: Typo in nls/ko_KR/Makefile.am
In-Reply-To: <s3t4r5n62cj.fsf@magellan.suse.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de> <s3t4r5n62cj.fsf@magellan.suse.de>
Message-ID: <20030328142707.GL2796@marilyn>

* Mike FABIAN (mfabian at suse.de) wrote:
> 
> There is a typo on nls/ko_KR/Makefile.am which causes Korean
> translations to be installed as /usr/share/openbox/ko_KO where they
> cannot be found.
> 

Thank you. This has been applied to CVS.

-- 
Scott Moynes http://www.icculus.org/openbox/
"Computer science is as much about computers
as astronomy is about telescopes." -- Dijkstra


From mfabian at suse.de  Mon Mar 31 04:00:08 2003
From: mfabian at suse.de (Mike FABIAN)
Date: Mon, 31 Mar 2003 11:00:08 +0200
Subject: Patch: fix a problem on 64 bit machines
In-Reply-To: <20030328142707.GL2796@marilyn> (smoynes@nexus.carleton.ca's
 message of "Fri, 28 Mar 2003 09:27:07 -0500")
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
	<s3t4r5n62cj.fsf@magellan.suse.de> <20030328142707.GL2796@marilyn>
Message-ID: <s3tk7ef7vxj.fsf_-_@magellan.suse.de>

smoynes at nexus.carleton.ca ????????:

> Thank you. This has been applied to CVS.

Thank you.

I found another small problem which causes crashes on 64 bit machines
like AMD x86_64. Patch attached.

In Configuration.hh there is the code:

  inline bool getValue(const std::string &rname, int &value) const {
    return getValue(rname, (long&) value);
  }
  inline bool getValue(const std::string &rname, unsigned int &value) const {
    return getValue(rname, (unsigned long&) value);
  }

This looks suspicious to me, I think this casting of "int &" to "long
&" won't work on 64 bit platforms. My patch just avoids to call one of
the above two methods by using a "long" from the beginning, thus
avoiding the cast which makes it "work for me".

But something needs to be fixed in the above two methods if one
actually wants to use them on platforms where "int" and "long" are not
the same.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: openbox-2.2.3-64bit.diff
Type: text/x-patch
Size: 341 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030331/596d6138/attachment.bin>
-------------- next part --------------

-- 
Mike Fabian   <mfabian at suse.de>   http://www.suse.de/~mfabian
?????????????

From mfabian at suse.de  Mon Mar 31 06:27:30 2003
From: mfabian at suse.de (Mike FABIAN)
Date: Mon, 31 Mar 2003 13:27:30 +0200
Subject: Patch: fix for setlocale problem
In-Reply-To: <s3tk7ef7vxj.fsf_-_@magellan.suse.de> (Mike FABIAN's message of
 "Mon, 31 Mar 2003 11:00:08 +0200")
References: <20030327210015.3305010a.thomas.loescher@gmx.de>
	<s3t4r5n62cj.fsf@magellan.suse.de> <20030328142707.GL2796@marilyn>
	<s3tk7ef7vxj.fsf_-_@magellan.suse.de>
Message-ID: <s3tvfxz4vz1.fsf_-_@magellan.suse.de>

The attached patch fixes a problem with the usage of setlocale.

The original code has some problems:

1) it changes the string returned by setlocale() directly without
making a copy, which is not allowed according to the glibc info pages:

glibc info>     The string returned by `setlocale' can be overwritten by subsequent
glibc info>     calls, so you should make a copy of the string (*note Copying and
glibc info>     Concatenation::) if you want to save it past any further calls to
glibc info>     `setlocale'.  (The standard library is guaranteed never to call
glibc info>     `setlocale' itself.)
glibc info>
glibc info>     You should not modify the string returned by `setlocale'.  It might
glibc info>     be the same string that was passed as an argument in a previous
glibc info>     call to `setlocale'.  One requirement is that the CATEGORY must be
glibc info>     the same in the call the string was returned and the one when the
glibc info>     string is passed in as LOCALE parameter.

2> it parses the return value of setlocale(LC_ALL, "") which isn't
allowed either:

glibc info>     When you read the current locale for category `LC_ALL', the value
glibc info>     encodes the entire combination of selected locales for all
glibc info>     categories.  In this case, the value is not just a single locale
glibc info>     name.  In fact, we don't make any promises about what it looks like.
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
glibc info>     But if you specify the same "locale name" with `LC_ALL' in
glibc info>     a subsequent call to `setlocale', it restores the same combination
glibc info>     of locale selections.

Indeed, this causes a problem on some platforms with the current
openbox. Let's have a look at the return values of
setlocale(LC_ALL,"") on different systems (the test program
"setlocale.c" which is used in the following example is attached).

First on a AMD x86_64:

    mfabian at magellan:~/tmp$ uname -a
    Linux magellan 2.4.20 #1 Sun Mar 23 07:16:53 UTC 2003 x86_64 unknown unknown GNU/Linux
    mfabian at magellan:~/tmp$ gcc setlocale.c
    mfabian at magellan:~/tmp$ ./a.out
    return value of setlocale()=ja_JP.UTF-8

Now the same program on an i686 platform:

    mfabian at gregory:~$ uname -a
    Linux gregory 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux
    mfabian at gregory:~/tmp$ gcc setlocale.c
    gcc setlocale.c
    mfabian at gregory:~/tmp$ ./a.out
    ./a.out
    return value of setlocale()=LC_CTYPE=ja_JP.UTF-8;LC_NUMERIC=ja_JP.UTF-8;LC_TIME=ja_JP.UTF-8;LC_COLLATE=C;LC_MONETARY=ja_JP.UTF-8;LC_MESSAGES=ja_JP.UTF-8;LC_PAPER=ja_JP.UTF-8;LC_NAME=ja_JP.UTF-8;LC_ADDRESS=ja_JP.UTF-8;LC_TELEPHONE=ja_JP.UTF-8;LC_MEASUREMENT=ja_JP.UTF-8;LC_IDENTIFICATION=ja_JP.UTF-8
    mfabian at gregory:~/c$ 

The return value of setlocale(LC_ALL, "") is different ("no promises
about what it looks like"!).

Currently openbox uses the return value of setlocale(LC_ALL, "")
cut before the first '.' character to find out which translation
file to read. This happens to work on the AMD x86_64 but fails
on i686. On i686 openbox tries to open 

    /usr/share/openbox/nls/LC_CTYPE=ja_JP/openbox.cat

which doesn't exist of course, therefore the fallback to English is
used (verified with "strace -eopen openbox").

I believe my patch openbox-2.2.3-setlocale.diff solves the above
problems.

First it calls setlocale(LC_ALL, "") to make use of all locales
specified by the environment variables, but doesn't use the return
value.

Then it just queries the value of LC_MESSAGES by calling
setlocale(LC_MESSAGES, NULL) and makes a copy of the return value
which is then modified to find the translation file to use. The return
value of setlocale(LC_MESSAGES, "") doesn't have the problem
demonstrated above for the return value of setlocale(LC_ALL,""), it
looks like it can safely be parsed to find the language subdirectory
where to find the openbox.cat file with the translated messages.

According to POSIX, LC_MESSAGES should be used to determine
the language of the messages, see also

http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap08.html


-------------- next part --------------
A non-text attachment was scrubbed...
Name: openbox-2.2.3-setlocale.diff
Type: text/x-patch
Size: 856 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030331/7cf559d2/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: setlocale.c
URL: <http://icculus.org/pipermail/openbox/attachments/20030331/7cf559d2/attachment.diff>
-------------- next part --------------

-- 
Mike Fabian   <mfabian at suse.de>   http://www.suse.de/~mfabian
?????????????

From ben at orodu.net  Mon Mar 31 13:42:32 2003
From: ben at orodu.net (Ben Jansens)
Date: Mon, 31 Mar 2003 12:42:32 -0600
Subject: [openbox] Patch: fix for setlocale problem
In-Reply-To: <s3tvfxz4vz1.fsf_-_@magellan.suse.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de> <s3t4r5n62cj.fsf@magellan.suse.de> <20030328142707.GL2796@marilyn> <s3tk7ef7vxj.fsf_-_@magellan.suse.de> <s3tvfxz4vz1.fsf_-_@magellan.suse.de>
Message-ID: <20030331184232.GF10599@orodu.net>

On Mon, Mar 31, 2003 at 01:27:30PM +0200, Mike FABIAN wrote:

<snip>

> First it calls setlocale(LC_ALL, "") to make use of all locales
> specified by the environment variables, but doesn't use the return
> value.
> 
> Then it just queries the value of LC_MESSAGES by calling
> setlocale(LC_MESSAGES, NULL) and makes a copy of the return value
> which is then modified to find the translation file to use. The return
> value of setlocale(LC_MESSAGES, "") doesn't have the problem
> demonstrated above for the return value of setlocale(LC_ALL,""), it
> looks like it can safely be parsed to find the language subdirectory
> where to find the openbox.cat file with the translated messages.

Thanks for the patch. One quick note is I believe it would be preferable to
use a std::string to make a copy of the value instead of strdup. strdup is
not a portable function.

Ben
-- 
I am damn unsatisfied to be killed in this way.

http://www.icculus.org/openbox/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030331/c4d21d5b/attachment.pgp>

From dpb at clara.co.uk  Mon Mar 31 13:52:51 2003
From: dpb at clara.co.uk (David Barr)
Date: Mon, 31 Mar 2003 18:52:51 +0000
Subject: toggled bitmaps for ob3
In-Reply-To: <s3tvfxz4vz1.fsf_-_@magellan.suse.de>
References: <20030327210015.3305010a.thomas.loescher@gmx.de>	<s3t4r5n62cj.fsf@magellan.suse.de> <20030328142707.GL2796@marilyn>	<s3tk7ef7vxj.fsf_-_@magellan.suse.de> <s3tvfxz4vz1.fsf_-_@magellan.suse.de>
Message-ID: <3E888E83.5040502@clara.co.uk>

here are the bitmaps you (xor) asked for; they are not fancy and not 
clever, but they are what they are i suppose.


I'm not sure about the states for (max and) sticky, maybe they would 
make more sense if the dots were stuck and the cross was un-stuck? so 
they would look like windows on different desktop (a bit, if you use 
your imagination...)?  i dunno.

--
for anonymous info: the ob2 theme (that looks a tad like metacity) from 
ob3++ is here, which may be of little interest to you
http://home.clara.net/dpb/junk/ob/merry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ob3.tar.bz2
Type: application/x-bzip2
Size: 544 bytes
Desc: not available
URL: <http://icculus.org/pipermail/openbox/attachments/20030331/4aa598ff/attachment.bz2>

