![]() |
nkuvu,
I'd say not to worry too much about the April dev tools - I've been using them since they were first released and have had no problems with fink since doing so. |
Window managers and Dev Tools
Learning quite a lot, this forum is definitely helpful - this website for that matter!
--- I'm using OroborOSX thus far, but haven't tried anything else. Instead of opening OroborOSX one time I just opened XDarwin alone (via the icon) - it opened with windows! It wasn't OroborOSX, so what was it using? Blackbox (sao's recommendation) and the other window managers - are they able to be opened as OroborOSX - by just opening the icon in the normal Mac OS X way? ..or do you have to start up within the terminal to get the others going? (Will FINK install icons for Mac OS X usage if I dive into other window managers?) I see talk of the Dec Dev Tools, where can I download it? I have the Sept Dev Tools - are they satisfactory if I end up having to install them? What's the advantage of having FINK compile source rather than just download pre-digested binaries? --- sao - you wrote, "When you get those errors after starting The Gimp, are you in rootless-mode or fullscreen ? And are you starting from terminal.app or an xterm?" Rootless, either with XDarwin or OroborOSX - both in the xterm way (by typing 'gimp'). Any ideas? Are those MPEG libraries actually needed? Jacques |
Jacques,
you wrote: Quote:
Quote:
'exec blackbox' or 'exec icewm' or 'exec enlightenment' or 'exec wmaker' After setting your ~/.xinitrc file, then you can double click in the XDarwin.app and Xfree86 will open with the window manager you specified in either full-screen or rootless mode. OroborOSX is just another window manager. Quote:
http://www.apple.com/developer/ and download them from there. Quote:
If you type in terminal: 'sudo fink list' fink will show you a list of all the packages you can install. Quote:
Cheers... |
Thanks to all for such a helpful thread.:D
I went throught the steps recommended here for installing Fink, Xfree86, and GIMP and I had the same error message about the MPEG library. fix-fink gave this result: ----------------------------------------------------------- Welcome to fix-fink version 1.0. This program will check your fink installation for certain problems which are difficult to detect directly with fink. If problems are found, you will be asked if you wish to update certain parts of fink, and if so, fink will be called to do the updating. At the moment, this program only checks for one thing: whether your dynamic libraries have been linked to an outdated version of libSystem. Do you wish to perform this check? [Y/n] y Examining your dynamic libraries with otool......................................................................................................./usr/bin/otool: can't open file: libmpeg.dylib (No such file or directory) .......................... Your dynamic libraries are OK. ----------------------------------------------------------- I used "sudo dselect" to get the MPEG library and it was only 65K, not 65Mb. "Get:1 http://fink.sourceforge.net release/main libmpeg 1.3.1-4 [65.5kB] Fetched 65.5kB in 1s (47.6kB/s) " After dselect installed it the error message went away. V-tach |
V-tach,
Glad it worked. Fix-fink clearly showed what was missing. And yes, libmpeg is only 65k. Thanks for the tip. Cheers... PS: So Jacques, now you know. You can install libmpeg through dselect, or if you have already installed the Dec Dev Tools, through 'fink install libmpeg' or you can try 'sudo apt-get install libmpeg'. |
Thanks for the info, this has been a great thread.
Since I was missing it and the error kept coming up, I simply downloaded it through DSELECT since I saw it listed. All is well with FINK, haven't really dug into it yet but plan to. I've been trying to download the Dec Dev Tools, no way I can handle it with a dial-up. A friend is going to burn it to CD for me today, I'll have it soon enough! --- I look forward to a stable KDE, the KDE Office application looks incredible - and useful! For now I'm sticking with Okito Composer for my word processing, a beautiful Cocoa application. Have a good weekend all, Jacques |
OK, I have another silly question.
I installed Fink, I installed XDarwin, I got OroborOSX running, then installed the Gimp. (Actually I installed XDarwin before Fink, then told Fink where to find it) I followed the directions from Griffman's PDF file (located at http://homepage.mac.com/rgriff/ -- thanks, Griffman!) The first time I ran OroborOSX after installing the Gimp, XDarwin failed to start (and therefore OroborOSX failed to start). I tried it again (because I clicked too fast to fully read the error message) and it worked. Typed gimp & and Gimp started up, let me congifure stuff, then worked fine. I don't have the exact error message from XDarwin failing ( :rolleyes: Sorry) but it seems that OroborOSX fails every other time that I try to start it. By "every other" I mean, it works, then the next time it fails, then the next time it works, etc... Any ideas? It works, but not as well as I'd like. And I also have to echo the others in saying that this is a very informative thread. Thanks for the help. |
One of the funky things about OroborOSX is that it has it's own self-contained copy of XDarwin (v. 1.1). (Do a 'Show Package Contents' on it). So the normal version of XDarwin which you would use with any other window manager does not launch with OroborOSX.
If you try to launch them both at once without changing the default display number (typically 0) on one of them they will clobber each other. |
I've been launching just OroborOSX -- and it says it's starting XDarwin, so I assumed (I know, bad idea) that it was the same.
So why would it fail intermittently? |
Probably a silly question..
I load the GIMP by typing gimp which seems to work fine but I notice people say they load it by typing gimp & - what's the difference? Jacques |
background
Jacques
If you type an & after the command it runs in the background and returns your prompt to the terminal. This is very handy with X11 apps that open their own windows and long running commands (those that take several minutes or hours to complete) vs. you can just open another terminal or wait it out. So %gimp would tie up your terminal while %gimp & would let you continue using the terminal AND use gimp. Willy |
One other thing to note. If you run gimp without the &, then kill the terminal window, you kill gimp also. If it's not in the background it's dependent on the terminal window staying open.
|
Another way to start 'The Gimp' is directly from the menu of your window manager. For example if you use icewm, you can modify to your taste the file 'menu' in ~/.icewm/menu with your favorite applications. My menu file looks like this:
Code:
# This is an example for IceWM's menu definition file.Code:
[begin] (Blackbox)Same you can do in gnome, you can configure your panel and menus to show the applications you want. Cheers... |
| All times are GMT -5. The time now is 06:19 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.