Ports 搜索

This program is a software package for programming the X22C12 EEPROM in the GE Phoenix SX radios (specifically the VHF and UHF 16 channel scanning versions). The X2212 is removed from the radio, placed in the parallel port adaper socket and can be read/written/verified or archived. The prom contents can be saved in a hex file format or exported as a text file for printing. Changing frequencies and channel guard settings is as easy as filling in the blanks.

Tiling window manager for X, based on David Hogan's 9wm. It provides virtual desktops, support for tiled and untiled windows, keyboard shortcuts and more, while using very little system resources.

This package contains xdm, the X.Org X Display manager.

from the Web page: evilwm is a minimalist window manager for X. The name evil came from Stuart 'Stuii' Ford, who reckons any window manager I use has to be evil and masochistic. This is not the case at all, but I liked the name. It features movement, killing, lowering, raising, and moving windows by keyboard control. It supports virtual desktops. Trevor Johnson

This package contains fonttosfnt, an application used for wrapping a bitmap font in a sfnt (TrueType) wrapper.

This package contains the X11 library.

i3lock improves slock by making it fork() and therefore combinable with commands to suspend your computer. Additionally, instead of turning off your screen via DPMS and/or displaying a black screen, i3lock displays a white screen so you can see if your computer failed to resume from suspend or if your screen is just locked. Also, when entering a wrong password, i3lock does not call XBell(). This is important because i3lock/slock think you have entered a password when resuming from suspend, at least sometimes. i3lock was forked from slock-0.9

i3status is a small program (about 1500 SLOC) for generating a status bar for dzen2, xmobar or similar programs. It is designed to be very efficient by issuing a very small number of system calls, as one generally wants to update such a status line every second. This ensures that even under high load, your status bar is updated correctly. Also, it saves a bit of energy by not hogging your CPU as much as spawning the corresponding amount of shell commands would.

Aewm is a modern, minimal window manager for X11. It is controlled entirely with the mouse, but contains no visible UI apart from window frames. It builds complex operations by chaining together primitives aewm does not try to do everything; there are plenty of better clients for defining hotkeys, menus, setting your background image, etc. Aewm makes it easy for you to keep the edges of the root window unobscured, so that you have essentially infinite space to click without having to aim (this principle is based on Fitts's Law). There is intentionally no panel or dock to get in the way. Aewm does not make decisions about where your windows should go. It can be used as an ordinary overlapping window manager, but is powerful enough to let you "tile" windows ad hoc if you prefer; maximizing space usage and removing overlaps are basic commands. You can also optionally take control of window mapping and change where windows will appear (including stacking and tiling) before they are actually shown. This port installs not only the window manager, but also the aemenu and aepanel applets. These provide a list of windows by title (vertically for aemenu, horizontally for aepanel) and a menu from which programs may be run.

TetriNET is an addictive 6 player tetr*s game What this program does is set up a TetriNET server that ordinary TetriNET clients can connect to. It attempts to fix some of the "glaring" holes in the TetriNET protocol that I discovered, and which I'm sure some people use as cheats, but I now see why it is nearly impossible to fix ;), without a modification to the client. I've kept the server as close to the same as the original TetriNET server, but I've added some extras that I've often wanted, such as the "/kick" and "/ban" keywords. Please note, this server in no way encompasses the whole game. The clients are the ones that do most of the work, with the server just passing suitable packets between each client, and of course adding some of it's own.