Current folder icons: https://sourceforge.net/dbimage.php?id=152332
Mac OSX Leopard folder icons: http://www.gnome-look.org/CONTENT/co...1/68411-1.jpeg
Before this theme, I 've installed many themes. So I know how to do with cursor theme, but this is the first time I meet this problem.
On apps window, it's black (Mac theme) but on desktop it's white (default theme)
"The true measure of a man is how he treats someone who can do him absolutely no good."
http://phoenix-ani.blogspot.com
What's the theme engine mac4lin 1.0 uses? Intrepid says it's not installed by default.
Last edited by LavianoTS386; September 17th, 2008 at 05:52 PM.
Intel C2 3.0Ghz E8400 / Gigabyte GA-73PVM-S2H / 4GB DDR2-PC6400 / 1TB & 320GB SATA Seagate.
Asus EeePC 901
Bad.. bad intrepid! Mac4Lin is still based on gtk-pixbuf (pixmap) engine.
"The true measure of a man is how he treats someone who can do him absolutely no good."
http://phoenix-ani.blogspot.com
I installed the theme and it looks fantastic - thank you very much! For some reason my terminal isn't showing its window manager - all the other windows are fine. Can anyone think of why this would happen?
Edit: I think the problem is just that the terminal window is opening in the extreme upper left so I have to move the Menu Bar to see the window border. How can I set the terminal so it opens somewhere else like in the middle of the page?
Last edited by MaindotC; September 19th, 2008 at 10:20 PM.
This version doesn't come with any of the applets from the previous version. Is there a reason why? When I try and install the extra applets I get the following message:
and using the autogen:Code:amd64@amd64-desktop:~/Desktop/awn-extras-applets-0.2.6$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes ./configure: line 4997: AC_PROG_LIBTOOL: command not found checking for gconftool-2... /usr/bin/gconftool-2 checking for intltool >= 0.34... 0.37.1 found checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for python... /usr/bin/python checking for a version of Python >= 2.1.0... yes checking for the distutils Python package... yes checking for Python include path... -I/usr/include/python2.5 checking for Python library path... -L/usr/lib/python2.5 -lpython2.5 checking for Python site-packages path... ${exec_prefix}/lib/python2.5/site-packages checking python extra libraries... -lpthread -ldl -lutil checking python extra linking flags... -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions checking consistency of all components of python development environment... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PYCAIRO... yes checking for PYGTK... yes checking for pygtk-codegen-2.0... /usr/bin/pygtk-codegen-2.0 checking for pygtk defs... /usr/share/pygtk/2.0/defs checking for round in -lm... yes checking for AWN... configure: error: Package requirements (awn) were not met: No package 'awn' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables AWN_CFLAGS and AWN_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. amd64@amd64-desktop:~/Desktop/awn-extras-applets-0.2.6$
How do I resolve this?Code:amd64@amd64-desktop:~/Desktop/awn-extras-applets-0.2.6$ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes ./configure: line 4997: AC_PROG_LIBTOOL: command not found checking for gconftool-2... /usr/bin/gconftool-2 checking for intltool >= 0.34... 0.37.1 found checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for python... /usr/bin/python checking for a version of Python >= 2.1.0... yes checking for the distutils Python package... yes checking for Python include path... -I/usr/include/python2.5 checking for Python library path... -L/usr/lib/python2.5 -lpython2.5 checking for Python site-packages path... ${exec_prefix}/lib/python2.5/site-packages checking python extra libraries... -lpthread -ldl -lutil checking python extra linking flags... -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions checking consistency of all components of python development environment... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PYCAIRO... yes checking for PYGTK... yes checking for pygtk-codegen-2.0... /usr/bin/pygtk-codegen-2.0 checking for pygtk defs... /usr/share/pygtk/2.0/defs checking for round in -lm... yes checking for AWN... configure: error: Package requirements (awn) were not met: No package 'awn' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables AWN_CFLAGS and AWN_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. amd64@amd64-desktop:~/Desktop/awn-extras-applets-0.2.6$
Regarding the terminal, I guess it has more to do with the compiz? I'm just guessing that the particular app is slated to be started at a particular position?
As far as the AWN applets are concerned, the AWN team has made many changes. To get the bleeding edge applets you can check out the bzr version. Lemme however warn you that it may not be stable.
"The true measure of a man is how he treats someone who can do him absolutely no good."
http://phoenix-ani.blogspot.com
I found that I can just add some guy's launchpad repo and download his .deb's for AWN extras. It's on the AWN wiki. Problem solved I have Dilbert & the Weather apps again
Bookmarks