AfterStep 1.8 FAQ Charlie Schmidt (ishamael@themes.org) 14 January 2000 This is the AfterStep version 1.8 FAQ. Copyright (C) 1996-2000, Frank Fejes, Jonathan B. Leffert, Kragen Sittler, Diego Zamboni, Guyhelm Aznar, Andrew Sullivan, Sasha Vasko, Andrew Ferguson, and Charlie Schmidt. Freely redistributable under the terms of the LDP license, Version 2, January 1998. ______________________________________________________________________ Table of Contents 1. General Information 1.1 About this Document. 1.2 What is AfterStep? 1.3 What is AfterStep's history? 1.4 Fine, what if I'm not running AfterStep 1.8? Is there a FAQ for me? 1.5 What is X? What are these "window managers" ? 1.6 What are AfterStep's main features? 1.7 Is AfterStep 1.8 GNOME and/or KDE compliant? 1.8 Can I run it in Microsoft Windows(tm)? 1.9 Who develops AfterStep? 1.10 AfterStep is awesome! How can I help? 1.11 Who writes this FAQ? 2. Resources 2.1 Where can I find AfterStep resources, or help? 2.2 What are the AfterStep mailing lists, and where are their archives? 3. Getting and Installing AfterStep 1.8 3.1 Where can I get AfterStep 1.8? 3.2 What do I need to compile and install AfterStep? 3.3 Can I install AfterStep without being root? 3.4 How do I upgrade AfterStep? 3.5 What's up with all these compile errors? 3.6 What's up with this error about sgmltools? 3.7 What if I don't want to compile AfterStep, can I get a binary package, like rpm? 3.8 How do I install AfterStep on SGI or SCO? 3.9 How do I install AfterStep on MacOS X? 3.10 How do I install AfterStep on a system with CDE? 4. Problems After Installing 4.1 I keep getting this "Cannot open display" error when I run AfterStep, what gives? 4.2 Why isn't my alt key working in emacs anymore? 4.3 I use RedHat Linux, and my startmenu changes keep disappearing, why? 4.4 How do I report a bug or suggest a new feature? 5. AfterStep Configuration 5.1 Where are the AfterStep configuration files? 5.2 Explain what all these configuration files do. 5.3 What is this .steprc everyone keeps talking about? 5.4 How do I add things to my startmenu? 5.5 How do I remove some of these titlebar buttons? 5.6 How do I change what happens when I click on a certain titlebar button? 5.7 How do I remove the titlebar from a window? 5.8 I don't want window focus to follow the mouse, how do I change it so it acts like Microsoft Windows(tm)? 5.9 What are these MyStyles I keep hearing about? 5.10 How do I get applications to iconify to a different place? 5.11 Suddenly, some windows stay on top of everything else, why? 5.12 Is there a graphical configuration program for AfterStep? 6. GNOME 6.1 What is GNOME, and why should I use it? 6.2 Why do window managers have to be GNOME compliant? 6.3 How do I get AfterStep to be GNOME compliant? 7. Graphics issues 7.1 Why do Swallowed apps and icons keep disappearing from the Wharf? 7.2 Why are the Netscape buttons deformed? Why does Netscape get its own colormap? 7.3 How do I create an icon with a transparent pixel? 7.4 Why are PNGs and JPEGs darker when they get loaded into AfterStep? 7.5 Why doesn't some program work in 16bpp? 7.6 How do I change the background in AfterStep? 7.7 How can I make the background centered, instead of tiled? 7.8 Why do some applications not have icons? 7.9 What is this transparent terminal I keep seeing? 7.10 How come some pixmaps look messed up when I set them as the aterm background? 8. AfterStep Modules 8.1 What are AfterStep modules? 8.2 How can I get multiple Wharfs or Pagers? 8.3 Why can't I find the man page for Wharf? 8.4 What is the difference between Wharf and Zharf? 8.5 How do I change the Pager's size? 8.6 Is it possible for an application to wait for the background to get loaded? 8.7 How can I get rid of the desk name in my Pager? 8.8 How do I start an application on a specific desk or page? 9. Themes 9.1 What is a "theme"? 9.2 Where can I find AfterStep themes? 9.3 How do I install an AfterStep theme? 9.4 How do I make an AfterStep theme? 9.5 Where can I get help on themes? 10. Miscellany 10.1 What is this "shade" thing? 10.2 How do I use Microsoft Windows(tm) TrueType fonts in AfterStep? ______________________________________________________________________ 11.. GGeenneerraall IInnffoorrmmaattiioonn 11..11.. AAbboouutt tthhiiss DDooccuummeenntt.. This document is an ever growing set of questions, statements, ideas and complaints about AfterStep version 1.8. You can get this FAQ at the following locations: +o +o +o +o (may be outdated) +o (thanks to Albert Dorofeev tigr@tigr.net) The rest of this document assumes you are running AfterStep 1.8, there is no more information pertaining to AfterStep 1.6. If you are running a version of AfterStep prior to version 1.8, this document will suggests only one thing: upgrade. 11..22.. WWhhaatt iiss AAfftteerrSStteepp?? AfterStep is a window manager for the X Window System (hereafter referred to as X). It was started to emulate the look and feel of NeXTSTEP(tm), but has evolved into something that while still being able to emulate NeXT, can do much much more. Without using much memory or cpu time, AfterStep provides all the features one could want in a window manager. 11..33.. WWhhaatt iiss AAfftteerrSStteepp''ss hhiissttoorryy?? The following is taken from the AfterStep man page ( ) AfterStep is a continuation of the BowMan window manager which was originally put together by Bo Yang. BowMan was based on the fvwm window manager, written by Robert Nation. Fvwm was based on code from twm. And so on.... It is designed not only to emulate some of the look and feel of the NEXTSTEP(tm) user interface, but also to add useful, requested, and neat features. The changes which comprise AfterStep's personality were originally part of BowMan development, but due to a desire to move past SIM- PLE EMULATION and into a niche as its OWN valuable window manager, the previous designers decided to change the pro- ject name and move on. 11..44.. FFiinnee,, wwhhaatt iiff II''mm nnoott rruunnnniinngg AAfftteerrSStteepp 11..88?? IIss tthheerree aa FFAAQQ ffoorr mmee?? Yes. There should be a version of the AfterStep 1.6 FAQ available anywhere this document is located. If you are using a version earlier than 1.6, it is strongly suggested you upgrade. 11..55.. WWhhaatt iiss XX?? WWhhaatt aarree tthheessee ""wwiinnddooww mmaannaaggeerrss"" ?? "X" is shorthand for The X Window System. It is a basis for building graphical user interfaces for UNIX (it is available for non-UNIX systems, but wasn't designed to be as such). "X" is not the interface itself, just a foundation for one. For more information, check . A window manager is a program that manages your windows during your X session. AfterStep is one of many available window managers . 11..66.. WWhhaatt aarree AAfftteerrSStteepp''ss mmaaiinn ffeeaattuurreess?? +o The Wharf. Similar to NeXTSTEP's(tm) Dock, it allows applications to be Swallowed, shortcuts with icons, and many other things. +o The Pager. Shows a miniature view of the Afterstep desktops, you can move between them, and move windows around in the Pager as though it were a miniature desktop. +o The WinList. A list of all the windows, clicking on the items can show that window, destroy it, shade it, or anything you might want. +o NeXTSTEP(tm) like look, feel, icons, and menus. +o Very configurable. Almost anything can be changed. 11..77.. IIss AAfftteerrSStteepp 11..88 GGNNOOMMEE aanndd//oorr KKDDEE ccoommpplliiaanntt?? As of version 1.7.59 AfterStep has been GNOME compliant through the Gnome module. It is not perfect yet, but near-100% compliance is on the way. AfterStep works fine with KDE. It may not be "compliant" per se, but the desktop icons KDE provides, and most of its other features work with AfterStep almost perfectly. 11..88.. CCaann II rruunn iitt iinn MMiiccrroossoofftt WWiinnddoowwss((ttmm))?? Not unless you get an X server. Take a look at for more information on how to set one up. Or, you could use an AfterStep like program named "LiteSTEP" to give your Windows 9x interface an appearance quite similar to AfterStep. You can get more information about LiteSTEP at . _N_o_t_e: please do note send LiteSTEP related questions to the AfterStep mailing list, the AfterStep developers, or the maintainers of this FAQ, they _c_a_n_n_o_t help you. 11..99.. WWhhoo ddeevveellooppss AAfftteerrSStteepp?? Many people. Take a look at for a list of current developers. Read the TEAM file distributed with AfterStep for a list of all contributors. 11..1100.. AAfftteerrSStteepp iiss aawweessoommee!! HHooww ccaann II hheellpp?? Send us money. Seriously though, if you can help write AfterStep, or feel you can help the effort elsewhere, do so. Hang out on irc (#afterstep, efnet), participate on the mailing lists, suggest ideas, help code, etc etc. 11..1111.. WWhhoo wwrriitteess tthhiiss FFAAQQ?? The file is maintained by Charlie Schmidt (ishamael@themes.org), with help from #afterstep, the developers, the mailing list, and anyone who finds a problem. The initial version of the FAQ was written by Frank Fejes (frank@ssax.com) and Jonathan B. Leffert (j-leffert@uchicago.edu). Major additions were made by Kragen Sittler (kragen@tcsi.com). Diego Zamboni (zamboni@cs.purdue.edu) maintained the file until Guylhem Aznar (guylhem@oeil.qc.ca) took over development and the FAQ with the release of AfterStep 1.4. Andrew Sullivan (asullivan@spring.ca) took over the FAQ after Guylhem left the development of AfterStep to pursue other things (he now runs the linuxdoc system). The AfterStep version 1.6 FAQ has major parts written by Tomas Duewiger (td@music- satellite.de), Sasha Vasko (sashav@sprintmail.com) and Andrew Ferguson (andrew@owsla.cjb.net). Naturally, the FAQ is prepared in co-operation with the program developers, but any errors or omissions are now Charlie Schmidt's responsibility, so you should contact him to compalin. Please do _n_o_t complain to the AfterStep developers that the FAQ has problems. They do not maintain it. Please note that it is likely to contain several errors, since the maintainers are only human, and the rapid pace of development often obsoletes facts quickly. 22.. RReessoouurrcceess 22..11.. WWhheerree ccaann II ffiinndd AAfftteerrSStteepp rreessoouurrcceess,, oorr hheellpp?? +o WWW Page The official AfterStep web page is at . This web site is under the excellent administration of David Mihm (webmaster@afterstep.org), and is kindly hosted by the generous people at WorkGroup Solutions, Inc . +o FTP site The FTP site, , is the best place to get AfterStep. It also supports uploads (of asapps, documentation, themes, etc) at . Please read the instructions about uploads before asking why your upload is not immediately available. +o AfterStep applets The applets (asapps) that go with AfterStep are distributed separately. The applet distribution is maintained by Albert Dorofeev, (tigr@tigr.net). You can find the applets at . +o Man pages. AfterStep is lucky to have David Mihm (webmaster@afterstep.org) as its man page author. These simple pages tell you in clear consice words how to do what with AfterStep. _P_l_e_a_s_e read the relevent man page before asking a question. Also note that the Pager man page is 'man Pager' (note the capitalization). The man pages can be read online at . +o #afterstep There is also #afterstep on EFnet IRC servers. If you need an irc client, try looking at . If you need an irc server, try irc.cdc.net, irc.mo.net, irc.txdirect.net, and . You can also view, but not participate in, #afterstep conversation at . 22..22.. WWhhaatt aarree tthhee AAfftteerrSStteepp mmaaiilliinngg lliissttss,, aanndd wwhheerree aarree tthheeiirr aarrcchhiivveess?? There are two AfterStep mailing lists. as-users, and as-devel. +o as-users. as-users is the general AfterStep mailing list, open to all AfterStep questions, concerns and ideas (_N_O LiteSTEP, Window Maker, some-x-app questions unless it really does pertain to AfterStep, please). A subscription can be obtained by emailing majordomo@afterstep.org with the content of "subscribe as-users". +o as-devel. as-devel is the development AfterStep mailing list. It is geared toward development questions, ideas and complaints. Subscribe by emailing majordomo@crystaltokyo.com with the content of "subscribe as-devel". The mailing list archives can be read at . 33.. GGeettttiinngg aanndd IInnssttaalllliinngg AAfftteerrSStteepp 11..88 33..11.. WWhheerree ccaann II ggeett AAfftteerrSStteepp 11..88?? You can download AfterStep 1.8 at any of the following locations: +o +o +o +o A more complete list of AfterStep download locations and mirrors is available at . 33..22.. WWhhaatt ddoo II nneeeedd ttoo ccoommppiillee aanndd iinnssttaallll AAfftteerrSStteepp?? Because AfterStep is an X application, you need to have X installed, and the X development libraries (note, in this case "development" means libraries need to compile things with X, not development level code). You'll also need a C compiler, and image libraries. +o libXpm +o libpng +o jpeg libraries It is suggested you have at least the xpm libraries, if not all image types. Because AfterStep comes with all of its images in xpm format, if you do not compile with libXpm, many of the default looks will appear broken or lacking in images. Save yourself the trouble of converting images, install libXpm. 33..33.. CCaann II iinnssttaallll AAfftteerrSStteepp wwiitthhoouutt bbeeiinngg rroooott?? Yes, before compiling AfterStep, do this: 1. mkdir ~/bin 2. mkdir -p ~/man/man1 3. ./configure --prefix ~/ Then follow the normal install directions, allowing you to make install without being root. 33..44.. HHooww ddoo II uuppggrraaddee AAfftteerrSStteepp?? The trick here is your ~/GNUstep/Library/AfterStep/ directory. Move it somewhere else (~/GNUstep.backup for example). Now start AfterStep, it will create a new ~/GNUstep/Library/AfterStep/ directory, and the correct directories under that. You can now move your old config back in. _N_o_t_e: This does not mean simply copying over the new ~/GNUstep/Library/AfterStep/ directory with the backed up one. Just make sure you don't copy over the new non-configurable directory. This directory is not to be moved, edited, linked to /dev/null, or anything of the sort! 33..55.. WWhhaatt''ss uupp wwiitthh aallll tthheessee ccoommppiillee eerrrroorrss?? Most likely, you don't have all the libraries AfterStep is looking for, such as libXpm, libpng, or jpeg libraries. Make sure you have the X devel package (should have come with your operating system, if not, check ), and any image libraries you want. 33..66.. WWhhaatt''ss uupp wwiitthh tthhiiss eerrrroorr aabboouutt ssggmmllttoooollss?? This FAQ is maintained in SGML, according to the Linuxdoc DTD; a version of the FAQ is included with every distribution of AfterStep. In order to make the SGML readable, a program called sgml2html (part of sgmltools ) converts it to HTML. Because many people don't have sgmltools, and don't want to bother installing them, and because AfterStep looks for sgmltools when creating the Makefiles, there are bound to be minor errors. As a result, the HTML version is also shipped with the distribution. The SGML is still incuded with AfterStep, so that users can make the FAQ in text, dvi, and PostScript formats, just use the sgmltools package to translate the SGML into whatever you please. 33..77.. WWhhaatt iiff II ddoonn''tt wwaanntt ttoo ccoommppiillee AAfftteerrSStteepp,, ccaann II ggeett aa bbiinnaarryy ppaacckkaaggee,, lliikkee rrppmm?? Yes. has a wide variety of binary packages available for download, including rpm, deb, and packages for other varients of Linux and Unix. Please keep in mind that many of these packages install AfterStep into /usr/ instead of /usr/local/, where compiling would install it. If you choose to install a package, please locate your global AfterStep directory if you plan to configure AfterStep. 33..88.. HHooww ddoo II iinnssttaallll AAfftteerrSStteepp oonn SSGGII oorr SSCCOO?? The problem with compiling on these systems was tracked down and reported by Benjamin J. Tracy (tracy@wsicorp.com) and John Koch (JKOCH1@Tandy.com). The ordering of the libraries in the link command is wrong. Just make sure that the AfterStep library appears _b_e_f_o_r_e the -lX11 argument on the link command line in the Makefile. 33..99.. HHooww ddoo II iinnssttaallll AAfftteerrSStteepp oonn MMaaccOOSS XX?? It's apparently a pain. The following was sent by Sarwat Khan (sarwat@interlog.com) to the mailing list: As a side note, installing AS on MOSXS was a royal pain in the butt (I really had nothing better to do, and I was wondering what it would take to get it done). It's not AS's fault. I guess the biggest proble m I had was because MOSXS uses Frameworks for a lot of stuff, not your standard .o or .a libraries. So I didn't have to use -ljpeg, I had to use -framework OmniJPEG. Also, maX doesn't put the X11 stuff in the usual places, it puts them in /Local/Library/Xnext/XR6.4/[usr,bin,X11,whatever]. I was able to get around that ok using configure, but then instead of using -lX11, I had to use "-F/L/L/Xnext/blah -framework X11", since he's made a bunch of libraries frameworks instead (which is ok, but getting AS's stuff to work with it was a pain in the ass). Also, he didn't include the X11 headers (?!), so I had to collect them from several places (what I downloaded from ftp.x.org was incomplete) and merge them in order to get all the headers. A few sources included 'malloc.h'. That's not kept in /usr/include (or wherever), it's in /System/Library/Frameworks/System.framework/bsd/src/). Yay. Usually you use ProjectBuilder to build tools and it handles the dumb details for you. 33..1100.. HHooww ddoo II iinnssttaallll AAfftteerrSStteepp oonn aa ssyysstteemm wwiitthh CCDDEE?? The following are instructions provided by Matthew R. Hamilton (panic@primary.net): The system wide default files for CDE configuration are located in /usr/dt/config and Sun recommends that if any personal customizations are to be done that they be placed under the /etc/dt/config directory (which does not exist by default). The first an most important file in adding new desktops to the system is located in /usr/dt/config//Xresources.d/. It is here that you will see a file called Xresources.ow (this is the entry for OpenWindows). It must start with Xresources and can have any meaningful extension. For myself I called the AfterStep file Xresources.step. There are four key resources used by dtlogin that go in this file. They are as follows: Dtlogin*altDtName -----> This is the name of the new desktop Dtlogin*altDtKey -----> This is what window manager to run Dtlogin*altDtStart -----> This is the configuration script Dtlogin*altDtLogo -----> This is the logo that appears in the dtlogin window and is a 237x237 XPM file located in /usr/dt/appconfig/icons/C/ (If that is not correct just do a find on the logo in the .ow file in the /usr/dt directory. NOTE: These files have an extension of .pm not.xpm, don't ask me why but that is the way Sun does it. Now the configuration file indicated in the Xresources.step file is located in /usr/dt/config. I stuck to Sun's naming convention and called mine Xsession.step. You can just copy the Xsession.ow to Xsession.step and customize it. There are three areas that I modified. The first was the environment variable SDT_ALT_SESSION and had it point to /usr/dt/config/Xsession.step2. You can also customize the hello message via either the DTDSPMSG or SDT_ALT_HELLO environment variables. The Xsession.step2 file is next called and is where the .Xinitrc file is run from. You can just copy the Xsession.ow2 file to Xsession.step2 and modify it to just run the .xinitrc file from the user's home directory or run a system wide .xinitrc file. On Solaris 2.5 the default .Xinitrc file is located in /usr/openwin/lib/Xinitrc while on Solars 2.6 it is in /usr/dt/config/Xinitrc. There are two other things you can modify in CDE. There is a directory /usr/dt/config/images. In that directory there are about 5 Sun raster images. The one that is of interest here is Solaris.im8. This is the image that displays the Welcome to Solaris in different languages. It is a 549x515 image and if you place any raster image of similar proportions in its place, it will be displayed instead of the one with the multi lingual welcome message. I would of course recommend keeping a backup of the original and just making symlinks to the images you want. Finally the file /usr/dt/config//Xresources contains some basic resources for the dtlogin window. You can change the messages displayed. I will leave that up to you as an exercise to figure out what the strings are and to have fun customizing your CDE desktops. 44.. PPrroobblleemmss AAfftteerr IInnssttaalllliinngg 44..11.. II kkeeeepp ggeettttiinngg tthhiiss ""CCaannnnoott ooppeenn ddiissppllaayy"" eerrrroorr wwhheenn II rruunn AAfftteerrSStteepp,, wwhhaatt ggiivveess?? Don't try to run AfterStep as a command from the console. Since it is a window manager you need to start it with X (or from X). The easiest way to do this is ______________________________________________________________________ echo "exec afterstep" > ~/.xinitrc ______________________________________________________________________ There are other ways to do this, incuding just starting an aterm in .xinitrc, and running afterstep from the terminal, xdm start scripts, and various other techniques. 44..22.. WWhhyy iissnn''tt mmyy aalltt kkeeyy wwoorrkkiinngg iinn eemmaaccss aannyymmoorree?? Because AfterStep stole it. The default feel AfterStep comes with uses the alt key in addition to other key combinations to do various tasks, such as minimize windows, bring up the startmenu, and switch desktops. Edit your feel file and remove the references to the alt key, or use the supplied feel.ICCCM. feel.ICCCM has no key combination bindings, and thus emacs will work fine. 44..33.. II uussee RReeddHHaatt LLiinnuuxx,, aanndd mmyy ssttaarrttmmeennuu cchhaannggeess kkeeeepp ddiissaappppeeaarriinngg,, wwhhyy?? RedHat, in an attempt to make your system easier to use, has a utility "wmconfig." What it is supposed to do is serve menus for all window managers, so that you can have the same startmenu in every window manager. However, since many people like to just use one window manager, or don't want to edit their menus via wmconfig, there are a variety of solutions presented: David Mihm (webmaster@afterstep.org), suggests you simply avoid wmconfig this way: ______________________________________________________________________ echo "exec afterstep" > ~/.xinitrc echo "exec afterstep" > ~/.xsession chmod 700 ~/.xsession ______________________________________________________________________ Matteo Lunardi (matteo.lunardi@usa.net) has offered a work-around in some versions. In the xinit-1.4.2.noarch.rpm, he edited the file /etc/X11/xinit/XClients: ______________________________________________________________________ if [ -f $HOME/.wm_style ] ; then WMSTYLE=Cat $HOME/.wm_style case "$WMSTYLE" in Afterstep*|AfterStep*) # we have to start up afterstep if [ -x /usr/X11R6/bin/afterstep -a -f /usr/share/afterstep/wmconfig.conf ] ; then # if [ ! -d $HOME/GNUstep/Library/AfterStep ]; then mkdir -p $HOME/GNUstep/Library/AfterStep wmconfig --output=afterstep --directories \ /usr/share/afterstep/wmconfig.conf 2>/dev/null # fi env > "$HOME"/Xrootenv.0 # if this works, we stop here eval "exec /usr/X11R6/bin/afterstep" > "$HOME"/.AfterStep-errors 2>&1 fi ______________________________________________________________________ In this case the change was to add comment marks ("#") to the "if" lines. Apparently it also works to add the comment marks to the "mkdir" and "wmconfig" lines. Chris Wood (chris@hillwood93.freeserve.co.uk), suggests that you can actually use wmconfig to make things easier for yourself. (Keep in mind that the information here is in no way a complete wmconfig guide, and that the man pages or RedHat's documentation is a much better source of information) So, if you wanted a menu item, "Mail", containing both mutt and elm, you would add two files: ______________________________________________________________________ ~/.wmconfig/mutt ~/.wmconfig/elm ______________________________________________________________________ The file "mutt" would contain the following: ______________________________________________________________________ mutt name "Mutt" mutt description "Mutt email client" mutt group Mail mutt exec "xterm -e mutt &" ______________________________________________________________________ The file "elm" would be similar: ______________________________________________________________________ elm name "Elm" elm description "Elm email client" elm group Mail elm exec "xterm -e elm &" ______________________________________________________________________ 44..44.. HHooww ddoo II rreeppoorrtt aa bbuugg oorr ssuuggggeesstt aa nneeww ffeeaattuurree?? Tell someone. Email the as-devel list, bugs@afterstep.org, jump on irc, whatever. Just make the issue known to the maintainers. If it is a bug, someone will get to fixing it. If it is an idea for a new feature, keep in mind that the developers may not want to add it for a variety of reasons. It may be difficult to add, and not worth the work, such as "shaped titlebars" (which will never happen), or it may not be a good idea in their eyes. At any rate, they key is to tell other people of your problems and ideas. 55.. AAfftteerrSStteepp CCoonnffiigguurraattiioonn 55..11.. WWhheerree aarree tthhee AAfftteerrSStteepp ccoonnffiigguurraattiioonn ffiilleess?? There are two places AfterStep configuration files could be. The global directory is usually /usr/local/share/afterstep/ (unless you installed from a binary package, or specified a different place). All configuration files should be here, and really shouldn't be edited. The preferred method for changing your configuration is copying the file you wish to change to ~/GNUstep/Library/AfterStep/, the personal configuration file directory. When AfterStep starts, it first reads ~/GNUstep/Library/AfterStep for files, and those that it does not find, it reads from /usr/local/share/afterstep. 55..22.. EExxppllaaiinn wwhhaatt aallll tthheessee ccoonnffiigguurraattiioonn ffiilleess ddoo.. The following is a list of all the AfterStep configuration files, and their purpose: +o Gnome - used to configure the Gnome module, man Gnome for more information. +o animate - animation settings. Animations take place when you iconify things +o asetroot - used to configure the asetroot module. This module controls the background for AfterStep, man asetroot for more information. +o asmail - used to configure the asmail applet. You can download the asmail applet and other AfterStep applets at . +o audio - used to configure the Audio module that supplies AfterStep with sound effects for certain events. +o autoexec - defines what is run when AfterStep starts and restarts. +o base.xxbpp - tells AfterStep where to look for its modules (ModulePath), pixmaps (PixmapPath), scripts and cursors. It also tells pager its size and dimensions. +o clean - configures the Clean module. Clean reduces clutter on your screen by Iconifying or Deleting windows after a certain period of inactivity. +o compatibility - read if AfterStep is run with -f .steprc. +o database - a list of applications and their attributes. You can tell AfterStep what icon they should iconify to, if the window has a title bar or not, if it has a vertical title bar, etc. +o feel.name - defines how AfterStep acts. +o forms - all the AfterStep forms. +o ident - configure the Ident module. Useful for finding window information. +o look.name - defines how AfterStep looks. +o pager - for configuring the Pager module. +o scroll - for configuring the Scroll module. +o wharf - Wharf module config file. +o winlist - WinList module config file. +o zharf - Zharf module configuration file. A more in-depth explanation of these files can be found in the man pages . 55..33.. WWhhaatt iiss tthhiiss ..sstteepprrcc eevveerryyoonnee kkeeeeppss ttaallkkiinngg aabboouutt?? .steprc was the old AfterStep configuration file. In eariler versions you put all your configuration (look, feel, Wharf, Pager, startmenu, etc) into the .steprc, and it was read when AfterStep started. This style has been abandoned for the split file directory structure configuration style. The current style makes it easier to configure AfterStep, and apply themes. 55..44.. HHooww ddoo II aadddd tthhiinnggss ttoo mmyy ssttaarrttmmeennuu?? Add entries in the start/ directory structure in your AfterStep configuration directory. To add an entry for Pine in an xterm, for example, you would create a file 'pine' in the correct directory, and put: ______________________________________________________________________ Exec "Pine" exec xterm -e pine ______________________________________________________________________ in it. Then update your startmenu, and there should be an entry "Pine" 55..55.. HHooww ddoo II rreemmoovvee ssoommee ooff tthheessee ttiittlleebbaarr bbuuttttoonnss?? Edit your look file. The TitleButton tags tell AfterStep which images to use for which titlebar buttons. The syntax is: ______________________________________________________________________ TitleButton button_number unclicked_image clicked_image ______________________________________________________________________ Where the button number is from 1-10: [1][3][5][7][9] (title) [10][8][6][4][2]. 55..66.. HHooww ddoo II cchhaannggee wwhhaatt hhaappppeennss wwhheenn II cclliicckk oonn aa cceerrttaaiinn ttiittlleebbaarr bbuuttttoonn?? Edit your feel file. The Mouse actions section defines what happens when you click on certain things in AfterStep. ______________________________________________________________________ Mouse mouse_button_number titlebar_button_number context action ______________________________________________________________________ is the syntax. 55..77.. HHooww ddoo II rreemmoovvee tthhee ttiittlleebbaarr ffrroomm aa wwiinnddooww?? You'll need to find the WM_CLASS of the window. AfterStep provides a tool "Ident" for finding out information about all the windows. Run Ident, and click on the window you need information on. The Class: item is the WM_CLASS. Next edit your database file. You should add an entry like this: ______________________________________________________________________ Style "WM_CLASS" NoTitle ______________________________________________________________________ The database file also changes other attributes, such as VerticalTitle, NoBorder, Sticky and others. Consult the AfterStep man page (man afterstep) for more information. 55..88.. II ddoonn''tt wwaanntt wwiinnddooww ffooccuuss ttoo ffoollllooww tthhee mmoouussee,, hhooww ddoo II cchhaannggee iitt ssoo iitt aaccttss lliikkee MMiiccrroossoofftt WWiinnddoowwss((ttmm))?? Take a look at the feel.ClickToFocus. Using this feel, you have to click on the window to give it focus, just like in Microsoft Windows(tm). If you already have a feel you like, and just want to add this feature, look through your feel file for "Raise" and "Focus" stuff, and compare the settings to those in feel.ClickToFocus. 55..99.. WWhhaatt aarree tthheessee MMyySSttyylleess II kkeeeepp hheeaarriinngg aabboouutt?? MyStyles are a new development in AfterStep configuration. Using MyStyles, all look related information (module looks, windows, icons, etc) can be put in the look file. What MyStyles provide is the ability to define a group of settings for a particular configuration option. For example, a MyStyle defining the look of a focused window can define it's font, pixmap, text color, text style, and let another MyStyle define the look of an unfocused window. Because the two MyStyles are separate, you can have focused and unfocused windows that look _c_o_m_p_l_e_t_l_y different, very easily. 55..1100.. HHooww ddoo II ggeett aapppplliiccaattiioonnss ttoo iiccoonniiffyy ttoo aa ddiiffffeerreenntt ppllaaccee?? The IconBox setting in the look file. It uses standard X geometry to define a rectangle of the screen to put icons. 55..1111.. SSuuddddeennllyy,, ssoommee wwiinnddoowwss ssttaayy oonn ttoopp ooff eevveerryytthhiinngg eellssee,, wwhhyy?? With the default feel, and many others, double-clicking on a window titlebar toggles a window's always-on-top state. Double-click again to remove it. If you want to remove this feature, locate the lines in your feel file that look similar to this (there may be several of them): ______________________________________________________________________ ToggleLayer "DoubleClick 0 1" ______________________________________________________________________ and comment them out, or change them. It is also possible that you have inadvertently changed your feel. Predictably enough, different feel files define functions such as this differently. Take a look at the supplied feel files to get an idea of their differences, and perhaps identify what feel you may unknowningly be using. Also, on many systems, using wine seems to interfere with the feel of AfterStep. Reselecting the feel file from the startmenu appears to fix this problem. 55..1122.. IIss tthheerree aa ggrraapphhiiccaall ccoonnffiigguurraattiioonn pprrooggrraamm ffoorr AAfftteerrSStteepp?? If you are using 1.6, yes. However, since 1.6 is outdated, it is suggested you upgrade. Andrew Ferguson (andrew@owsla.cjb.net) is developing a new ascp to use AfterStep's native configuration parser. There will be a new 1.8 release once this project is completed. Email him, or check the 1.9 tree to use developmental ascp (please note _d_e_v_e_l_o_p_m_e_n_t. It will not compile, nor work at this point in time.) 66.. GGNNOOMMEE 66..11.. WWhhaatt iiss GGNNOOMMEE,, aanndd wwhhyy sshhoouulldd II uussee iitt?? The GNOME project is a lot of things. The following is taken from the GNOME FAQ, GNOME is the GUI desktop of the GNU Project. To quote from the original announcement from comp.os.linux.announce, GNOME is intended to be "a free and complete set of user friendly applications and desktop tools, similar to CDE and KDE but based entirely on free software." I, your lowly FAQ maintainer, like to explain GNOME as everything that's expected in a modern programming environment. In this respect, it is approximately equivalent to CDE, Win32, NextStep, or KDE. The big difference is that, unlike any of the above-mentioned examples, every single component of GNOME is Free Software. Not only that, but GNOME is extremely customizable compared to most desktop environments. If all of this seems ambitious, that's because it is! Read on to find out more! The entire GNOME FAQ can be read online at . 66..22.. WWhhyy ddoo wwiinnddooww mmaannaaggeerrss hhaavvee ttoo bbee GGNNOOMMEE ccoommpplliiaanntt?? They don't have to be. Many popular window managers are not GNOME compliant, but because GNOME will probably be prevalent on *NIX desktops some day in the future, window managers wishing to provide as many features to users as possible should be GNOME compliant. It must be noted that GNOME compliancy is always changing, and is not finalized whatsoever. Because of the pace of GNOME development, what worked one day, may not work the next. AfterStep is not 100% compliant, in fact, no window manager is. Some aspects of compliancy with GNOME cannot be implemented in AfterStep, because the window manager is much more powerful, virtual desktops and Pager, for example. Some window managers do a better job of compliancy than others. AfterStep attempts to be compliant in as many regards at it can, but perfection is not possible. If you are looking for a window manager that can run with GNOME almost all the time, and do it well, AfterStep is a good choice. If you want something that will cooperate with GNOME to the point of being GNOME, try something else. 66..33.. HHooww ddoo II ggeett AAfftteerrSStteepp ttoo bbee GGNNOOMMEE ccoommpplliiaanntt?? The following are my (ishamael@themes.org) experiences with getting GNOME and AfterStep running together like any other window manager. If you have any suggestions or other ways to do this, please email me. While in your current window manager (be it AfterStep or another): Set the WINDOW_MANAGER variable to "afterstep" (in bash this can be done with Run "gnomecc" and go to the "Window Manager" section. "Add" +o Name: AfterStep +o Command: afterstep +o Configuration Command: xterm AfterStep is session managed, so check the box. At this point, save the settings, and close gnomecc (you might want to start it again and check it to make sure the addition is there). You will also need to make a small change to the gnome-wm script (usually at /usr/bin/gnome-wm or /usr/local/bin/gnome-wm). The line that reads: ______________________________________________________________________ exec $WINDOW_MANAGER $* ______________________________________________________________________ change to: ______________________________________________________________________ exec $WINDOW_MANAGER ______________________________________________________________________ Now, you should close X down, and put "gnome-session" in your .xinitrc (or however you start X), and start it up again. If all goes well, AfterStep and GNOME will start. Also please make sure you are using the Gnome AfterStep module, and a GNOME compliant feel (such as feel.GNOME). 77.. GGrraapphhiiccss iissssuueess 77..11.. WWhhyy ddoo SSwwaalllloowweedd aappppss aanndd iiccoonnss kkeeeepp ddiissaappppeeaarriinngg ffrroomm tthhee WWhhaarrff?? You're probably running at 8 bits per pixel, or 256 colors. If you run out of colors, some applications can't run, or don't appear correctly. Either run at a higher color depth, or reduce colors elsewhere. There is an excellent set of low color icons (21 colors total) at . 77..22.. WWhhyy aarree tthhee NNeettssccaappee bbuuttttoonnss ddeeffoorrmmeedd?? WWhhyy ddooeess NNeettssccaappee ggeett iittss oowwnn ccoolloorrmmaapp?? Again, this is probably an issue with 8bpp, either reduce colors elsewhere, or sacrifice resolution for color depth (run at a lower resolution with more colors). 77..33.. HHooww ddoo II ccrreeaattee aann iiccoonn wwiitthh aa ttrraannssppaarreenntt ppiixxeell?? The Gimp ( ) supports transparency in images, you could easily modify an existing pixmap to be transparent, or make a new image. You could also edit a .xpm file with a normal text editor, and make part of it transparent (hint, the color for transparency is "none"). 77..44.. WWhhyy aarree PPNNGGss aanndd JJPPEEGGss ddaarrkkeerr wwhheenn tthheeyy ggeett llooaaddeedd iinnttoo AAfftteerr-- SStteepp?? Try setting your $SCREEN_GAMMA to something like 2.2 (export SCREEN_GAMMA=2.2) from the shell you start AS (or put it in your .xinitrc) and stop X, then start it again. 77..55.. WWhhyy ddooeessnn''tt ssoommee pprrooggrraamm wwoorrkk iinn 1166bbpppp?? Several (although decreasingly many) 8bpp programs don't work on displays without a PseudoColor visual available. Several PC X servers don't support PseudoColor visuals on displays running in TrueColor mode. You should buy an SGI. Or run two simultaneous X servers, if you're on Linux. Note for SGI users willing to play with their bpp : One has to tweak the arguments to X in /usr/lib/X11/xdm/Xservers. The following worked for Tim Buller (buller@math.ukans.edu) :0 secure /usr/bin/X11/X -bs -c -nobitscale -visid 0x34 Where Visual ID 0x34 (reported by xdpyinfo) is: visual: visual id: 0x34 class: TrueColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff, 0xff00, 0xff0000 significant bits in color specification: 8 bits 77..66.. HHooww ddoo II cchhaannggee tthhee bbaacckkggrroouunndd iinn AAfftteerrSStteepp?? Using asetroot, the AfterStep desktop background management module. asetroot sets images to the background, but can also modify them before doing so. It is compliant with "transparent" terminals, such as aterm or Eterm, and with AfterStep transparency effects. The simplest way to set a new background, is to place the image in the backgrounds/ directory of an AfterStep configuration directory (~/GNUstep/Library/AfterStep/, usually), and update the startmenu. The new image should be selectable from the startmenu under start->Desktop->Pictures. You can select it, and asetroot will tile it as the background. 77..77.. HHooww ccaann II mmaakkee tthhee bbaacckkggrroouunndd cceenntteerreedd,, iinnsstteeaadd ooff ttiilleedd?? Because asetroot can modify an image, or display it different ways, centering a background is a simple task. Edit your "asetroot" configuration file, and put: ______________________________________________________________________ MyBackground "back0" Use 0 "~/GNUstep/Library/AfterStep/non-configurable/0_background" Pad 4 black Align 4 ~MyBackground *asetrootDeskBack 0 "back0" ______________________________________________________________________ This will center the image, and pad the other unused space with black. More information about changing how the image is displayed can be read in the asetroot man page. 77..88.. WWhhyy ddoo ssoommee aapppplliiccaattiioonnss nnoott hhaavvee iiccoonnss?? Application icons are set in the "database" configuration file. Since the developers don't use every application ever made, obviously they can't provide settings for icons for all of them. What is provided are settings for commonly used programs. Add your own for your applications by looking at the provided examples. 77..99.. WWhhaatt iiss tthhiiss ttrraannssppaarreenntt tteerrmmiinnaall II kkeeeepp sseeeeiinngg?? Probably aterm if you're looking at AfterStep screenshots, or Eterm. Both aterm and Eterm emulate transparency by aligning the background pixmap correctly in their own backgrounds.Thus making it seem like the desktop background is showing through. aterm can be downloaded at or , Eterm can be downloaded wherever you can find Enlightenment . aterm is preferred, as it was developed with AfterStep in mind, and uses considerably less resources than Eterm. 77..1100.. HHooww ccoommee ssoommee ppiixxmmaappss llooookk mmeesssseedd uupp wwhheenn II sseett tthheemm aass tthhee aatteerrmm bbaacckkggrroouunndd?? The image you're setting to the background probably isn't indexed, Benjamin Tovar (al707198@academ01.ccm.itesm.mx) informs me: advise to index the colors of the xpm. Unless you are an eagle, you wont notice much difference if you index the images (with the Index: Optimal Palette, in Gimp for example) for instance with 64 levels. With this, the time from when you call xiterm and appears reduces very much, and allows the use of "complex" images in xiterm. If the image is not that complex, also you can try to index with very few levels and obtain an "optimal" speed. 88.. AAfftteerrSStteepp MMoodduulleess 88..11.. WWhhaatt aarree AAfftteerrSStteepp mmoodduulleess?? AfterStep modules are programs that work with AfterStep, but aren't required by the window manager. Commonly seen modules are the Wharf, Pager, WinList, and asetroot. 88..22.. HHooww ccaann II ggeett mmuullttiippllee WWhhaarrffss oorr PPaaggeerrss?? This procedure is outlined in depth at . Briefly: Make a symbolic link from the Wharf binary to a new MyWharf. Edit your "wharf" configuration file so that it has *MyWharf tags similar to existing *Wharf tags. Make sure you edit the "autoexec" file if you want this new MyWharf to start with AfterStep. Also be sure to edit the "database" file so that there is a MyWharf Style exactly like the existing Wharf Style. You can create multiple Pagers in a similar fashion. 88..33.. WWhhyy ccaann''tt II ffiinndd tthhee mmaann ppaaggee ffoorr WWhhaarrff?? Spell it "Wharf" not "wharf" Similarly the "Pager", "WinList" and "afterstep" man pages [the key here is capitalization]. 88..44.. WWhhaatt iiss tthhee ddiiffffeerreennccee bbeettwweeeenn WWhhaarrff aanndd ZZhhaarrff?? The Wharf module can use pixmaps for buttons, the Zharf module can only use text. 88..55.. HHooww ddoo II cchhaannggee tthhee PPaaggeerr''ss ssiizzee?? There are really two questions here. Do you want to change the number of desks or views? Or do you want to change the physical geometry of Pager? In the "base.xxbpp" file, look at DeskTopSize. This defines the number of columns of views by the number of rows (2x2 would give you 4 views in a square). In the "pager" file, edit the *PagerGeometry tag (standard X geometry). 88..66.. IIss iitt ppoossssiibbllee ffoorr aann aapppplliiccaattiioonn ttoo wwaaiitt ffoorr tthhee bbaacckkggrroouunndd ttoo ggeett llooaaddeedd?? I put the rt [root tail] command as the last one to be executed in autoexec. So far, so good, it executes last. But when my background is loaded it covers the tailed text, until another message appears in the file. Is it possible for rt to wait for the background to get loaded? It is possible. The background is displayed by the asetroot module. So, you should wait for asetroot to start before running any root window/background dependent applications (like rt or Eterm). Add the following line to your autoexec file (or check that it's there): ______________________________________________________________________ Module "I" asetroot 0 3 Wait "I" asetroot ______________________________________________________________________ The "Wait" line _m_u_s_t precede the startup lines for the relevant applications (in our example, rt). By default, the "Wait" line will cause AfterStep to wait for asetroot to load all of its backgrounds for all desks. 88..77.. HHooww ccaann II ggeett rriidd ooff tthhee ddeesskk nnaammee iinn mmyy PPaaggeerr?? Set *PagerDecoration NoDeskLabel in the "pager" configuration file. 88..88.. HHooww ddoo II ssttaarrtt aann aapppplliiccaattiioonn oonn aa ssppeecciiffiicc ddeesskk oorr ppaaggee?? This is defined in the "database" configuration file. There are three paramaters one can use. +o StartsOnDesk desk_number This one will specify the desk number that applications with this tay will start on. Don't forget that desks are numbered starting with 0. +o VeiwportX x_coord You can use this one to start an application on a specific page of a desk. The value should be the x coordinate of the page, relative to the top-left corner of the desk. For instance, with a screen size of 1024x768, the argument value would be "1024" in order to open an application on the second column of pages. +o ViewportY y_coord This does the same thing as ViewportX, but in the Y axis. 99.. TThheemmeess 99..11.. WWhhaatt iiss aa ""tthheemmee""?? Simply put, a theme is a group of configuration settings and images that when used together looks good. Themes are pre-made, complete settings for your window manager. AfterStep themes are new feature of the window manager, and since 1.7.160, are completly implemented. 99..22.. WWhheerree ccaann II ffiinndd AAfftteerrSStteepp tthheemmeess?? +o +o Both of these locations allow users to download a variety of themes, and upload their own. 99..33.. HHooww ddoo II iinnssttaallll aann AAfftteerrSStteepp tthheemmee?? It is _v_e_r_y easy to install a theme. Simply download the theme.tar.gz file and put it in ~/GNUstep/Library/AfterStep/themes/, update your startmenu, and select the theme from the start->Desktop->Theme menu. 99..44.. HHooww ddoo II mmaakkee aann AAfftteerrSStteepp tthheemmee?? Edit your look file, pager, wharf, and winlist configurations so that it all looks good. Make some images to go with it, and select Create Theme from the menu. The new theme.tar.gz will appear in ~/GNUstep/Library/AfterStep/. 99..55.. WWhheerree ccaann II ggeett hheellpp oonn tthheemmeess?? Read the documentation provided on , if you still have a question, email the mailing list or as@themes.org. 1100.. MMiisscceellllaannyy 1100..11.. WWhhaatt iiss tthhiiss ""sshhaaddee"" tthhiinngg?? Shade is a window feature that many prefer to iconifying. Instead of minimizing a window into an icon, it scrolls the window contents up into the titlebar. It is nice because you do not have to define an icon for the window in the "database" file, and many find it easier to keep track of windows if they still appear in the middle of the screen. 1100..22.. HHooww ddoo II uussee MMiiccrroossoofftt WWiinnddoowwss((ttmm)) TTrruueeTTyyppee ffoonnttss iinn AAfftteerrSStteepp?? This isn't really an AfterStep issue, rather an X question. Download and install a TrueType font server, such as xfstt . Many distributions are now shipping with some sort of TrueType font server. Consult your documentation to use this feature of your distribution.