From christian.hofer at gmx.de Thu May 20 18:06:27 2004 From: christian.hofer at gmx.de (Christian Hofer) Date: Thu, 20 May 2004 20:06:27 +0200 Subject: [eclipse-devel] Gnome not found during configuration Message-ID: <40ACF3A3.8020600@gmx.de> Hi, when I try to configure Eclipse, it will not create a gnome entry, even if I do ./configure --with-gnome-entry-dir /usr/X11R6/share/gnome/wm-properties/ Do I make s.th. wrong or is it maybe not yet working with the new gnome version, or is this not the supposed directory? I am working on FreeBSD 5.2.1 with Gnome 2.6.1. Thanks, Chris From hatchond at labri.fr Fri May 21 12:25:01 2004 From: hatchond at labri.fr (hatchond at labri.fr) Date: Fri, 21 May 2004 14:25:01 +0200 Subject: [eclipse-devel] Gnome not found during configuration In-Reply-To: <40ACF3A3.8020600@gmx.de> References: <40ACF3A3.8020600@gmx.de> Message-ID: <1085142301.40adf51da0ee7@iona.labri.fr> Selon Christian Hofer : > Hi, > > when I try to configure Eclipse, it will not create a gnome entry, even > if I do > > ./configure --with-gnome-entry-dir /usr/X11R6/share/gnome/wm-properties/ > > Do I make s.th. wrong or is it maybe not yet working with the new gnome > version, or is this not the supposed directory? As you noticed since gnome-2.0 things work differently on that side. The wm-properties, AFAIK, does not exist or is not used anymore. In that case you should do ./configure --without-gnome-entry-dir. After everything has been compiled and installed, start your X gnome-session from the console. Before starting your X session do an "export WINDOW_MANAGER=/path/to/eclipse", then the window manager that will be started should be eclipse. Now exit and save your session, and the next time you start it, eclipse should be your window manager. It might be a delay during the first start because the gnome session may not understand Eclipse as it should. The symptoms are the gnome splash screen that stay for a long time on the window manager starting phase. But it should start anyway. For those who want to do that with KDE the env variable that has to be set is KDEWM. Please let me know if this does help or not or you still encounter any problems. Regards, Iban. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From christian.hofer at gmx.de Fri May 21 21:43:42 2004 From: christian.hofer at gmx.de (Christian Hofer) Date: Fri, 21 May 2004 23:43:42 +0200 Subject: [eclipse-devel] Gnome not found during configuration In-Reply-To: <1085142301.40adf51da0ee7@iona.labri.fr> References: <40ACF3A3.8020600@gmx.de> <1085142301.40adf51da0ee7@iona.labri.fr> Message-ID: <40AE780E.6080305@gmx.de> hatchond at labri.fr wrote: >As you noticed since gnome-2.0 things work differently on that side. >The wm-properties, AFAIK, does not exist or is not used anymore. In that case >you should do ./configure --without-gnome-entry-dir. After everything has been >compiled and installed, start your X gnome-session from the console. Before >starting your X session do an "export WINDOW_MANAGER=/path/to/eclipse", then >the window manager that will be started should be eclipse. Now exit and save >your session, and the next time you start it, eclipse should be your window >manager. It might be a delay during the first start because the gnome session >may not understand Eclipse as it should. The symptoms are the gnome splash >screen that stay for a long time on the window manager starting phase. But it >should start anyway. > > Merci beaucoup! At first I felt a bit helpless, because I do not start the X session by hand, but use kdm and could not figure out, how to set the environment variable so that it takes effect. But now I knew for which keywords to search Google, and decided to use the brutal way: killall -9 metacity; sleep 5; exec eclipse & then logoff, saving the session. Maybe this is not the supposed way, but it worked (although it showed an error that there is no .eclipse-file). What is really cool, is the possibility to maximize the windows horizontally and vertically separately. The impossibiltiy to do this was one of the big annoyances so far for me (but maybe I just didn't know it existed in other window managers)! What I find strange, is that on the Gnome panel at the bottom of the screen, I cannot get a window to front by just clicking on the button, although I can minimize and get back windows by this method. Maybe this is a bug? (But I have little Gnome experience.) I will have to try it with KDE as well. Thanks again, Chris From edi at agharta.de Mon May 24 20:16:42 2004 From: edi at agharta.de (Edi Weitz) Date: Mon, 24 May 2004 22:16:42 +0200 Subject: [eclipse-devel] Some questions Message-ID: <877jv1polx.fsf@agharta.de> Hi! I've recently started to actually /use/ Eclipse after I had just tried it a couple of times. Great work, I'm very impressed! I have a couple of questions and issues which I list below. Pardon me if some of them are just plain stupid, I've mostly used KDE in the last years which probably completely ruined my understanding of X and window managers. I'm trying to run Eclipse "stand-alone", i.e. without Gnome or somesuch, because I figured out that I only need a rather minimal setup. I rarely use more apps than Emacs, some xterms, and a web browser. I'm using Eclipse from CVS. 1. I'm running gkrellm all of the time to monitor the CPU and some other things. I'd like to have this window always on top, i.e. not obscured by other windows. How do I do that with Eclipse? 2. It'd be even better if gkrellm had it's own part of the screen that couldn't be touched by other programs. In other words: If I maximize another window it should only grow as far as to the edge of gkrellm (as if it were a panel in KDE). Is that possible? 3. If I've maximized a window I can't resize it with the mouse afterwards - I have to unmaximize it first. Is that expected behaviour? 4. Sometimes when I maximize an xterm it looses focus. Does anybody else see this? I fail to create a reproducable test case but it happens regularly. 5. What does "Pin" mean? 6. Every xterm I start opens at the same place (0,0) and covers the other xterms that are already there although I haven't set this in my .Xdefaults. Is it possible to automatically place a new window in such a way that it doesn't obscure other windows of the same type (meaning from the same app)? 7. If I click button3 on the root window I get a menu with four entries "Move", "Resize", "Close", and "Kill". I understand what "Close" and "Kill" do but I cannot see how I'm supposed to use the other two. Thanks in advance for any help and, again, my apologies if these are dumb questions. Cheers, Edi. From edi at agharta.de Mon May 24 20:42:58 2004 From: edi at agharta.de (Edi Weitz) Date: Mon, 24 May 2004 22:42:58 +0200 Subject: [eclipse-devel] put-on-bottom Message-ID: <87y8nho8tp.fsf@agharta.de> In widgets.lisp: (defmethod put-on-bottom ((widget base-widget)) (setf (xlib:window-priority (widget-window widget)) :above)) Shouldn't that be :below? Currently it's the same code as put-on-top. From edi at agharta.de Mon May 24 23:03:09 2004 From: edi at agharta.de (Edi Weitz) Date: Tue, 25 May 2004 01:03:09 +0200 Subject: [eclipse-devel] Some questions In-Reply-To: <877jv1polx.fsf@agharta.de> (Edi Weitz's message of "Mon, 24 May 2004 22:16:42 +0200") References: <877jv1polx.fsf@agharta.de> Message-ID: <87d64to2c2.fsf@agharta.de> On Mon, 24 May 2004 22:16:42 +0200, Edi Weitz wrote: > 1. I'm running gkrellm all of the time to monitor the CPU and some > other things. I'd like to have this window always on top, i.e. not > obscured by other windows. How do I do that with Eclipse? I forgot: I'd be also nice if I could arrange for this app not to appear in the list of windows to cycle through with ALT-TAB. Edi.