AfterStep 1.8 FAQ: General Information

Next Previous Contents

## 1. General Information

## 1.1 About this Document.

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:

- http://afterstep.davidv.net/
- http://www.afterstep.org/FAQ/
- ftp://ftp.afterstep.org/FAQ/
- http://www.linuxdoc.org/ (may be outdated)
- http://www.tigr.net/afterstep/faq/ (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.

## 1.2 What is AfterStep?

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.

## 1.3 What is AfterStep's history?

The following is taken from the AfterStep man page ( http://www.afterstep.org/man/stable/afterstep.html)

> `

>            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.

> `

## 1.4 Fine, what if I'm not running AfterStep 1.8? Is there a FAQ for me?

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.

## 1.5 What is X? What are these "window managers" ?

"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 http://www.x.org.

A window manager is a program that manages your windows during your X session. AfterStep is one of many available window managers.

## 1.6 What are AfterStep's main features?

- The Wharf. Similar to NeXTSTEP's(tm) Dock, it allows applications to be Swallowed, shortcuts with icons, and many other things.
- 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.
- 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.
- NeXTSTEP(tm) like look, feel, icons, and menus.
- Very configurable. Almost anything can be changed.

## 1.7 Is AfterStep 1.8 GNOME and/or KDE compliant?

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.

## 1.8 Can I run it in Microsoft Windows(tm)?

Not unless you get an X server. Take a look at http://www.rahul.net/kenton/xsites.html#XMicrosoft 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 http://www.litestep.net. Note: please do note send LiteSTEP related questions to the AfterStep mailing list, the AfterStep developers, or the maintainers of this FAQ, they cannot help you.

## 1.9 Who develops AfterStep?

Many people. Take a look at http://www.afterstep.org/Team.shtml for a list of current developers. Read the TEAM file distributed with AfterStep for a list of all contributors.

## 1.10 AfterStep is awesome! How can I help?

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.

## 1.11 Who writes this FAQ?

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 not 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.

Next Previous Contents