• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

00READMEH A D14-Jun-20072.5 KiB8563

BUGSH A D14-Jun-2007844 2415

COPYRIGHTH A D14-Jun-2007303 119

MakefileH A D03-May-20221.8 KiB8857

gfx-x.cH A D13-Aug-200714 KiB444346

gfx-x.hH A D09-Jun-20071.4 KiB5440

helpfile.xbmH A D23-Nov-2006361.4 KiB5,0055,004

main.cH A D09-Jun-20079.7 KiB324236

psys2d.cH A D03-Jul-200714 KiB519381

psys2d.hH A D09-Jun-20072.8 KiB8962

xglurbules.1H A D09-Jun-20072.8 KiB11272

00README

10) COPYRIGHT
2------------
3Please read the COPYRIGHT file.
4
51) BUILDING
6-----------
7On FreeBSD you should be able to get the port/package from
8
9http://stephenroome.com/xglurbules/
10
11On your run of the mill Unix box, you should just be able to type
12
13make
14
15This may not work for you, if you can edit the Makefile and get it to
16work then that's cool, if not send me the output that you get with
17make and I'll try and fix it.
18
19Just so you know: you may not like my code. That's okay, I don't either.
20
212) RUNNING IT
22-------------
23Assuming it built fine, which is possible, if not likely, then you
24should have two executable :
25
26	xglurbules
27and
28	xglurbules_noshm
29
30You could try running either, both should catch (most) signals and
31clear up after themselves. I'm not promising anything, but they should
32be fine.
33
34However with any program that uses shared memory check out "ipcs(1)",
35hopefully you have a manpage there. It will show if you've shared
36memory segments not being cleared up. It *could* happen, if you kill
37an XSHM program in a way it can't handle.
38 e.g. kill -9 pid_of_xglurbules
39
40
413) USAGE
42--------
43keyboard controls are explained on screen (in the terminal you run it
44from)
45
46Command Line Switches for both xglurbules and xshmglurbules :
47(were at one time...)
48
49        -h        : Show help
50        -l <num>  : Only show <num> frames (before quitting)
51        -n <num>  : set number of particles to <num>
52        -x <xres> : set x resolution
53        -y <yres> : set y resolution
54        -r        : run in root window
55        -m        : randomly change force modes
56        -b <0-255>: Set particle brightness
57        -f        : Show frames per second
58        -c <color>: Run with a colormap based on a given color
59                  : e.g. -c 0xffaa66 for shades of orange
60                  :      -c 0xaaccff for shades of something?!
61
62e.g.
63./xshmglurbules -x 640 -y 512 -n 20000 -f -c 0xfce3f6
64	(wow, what a vile colour that is!)
65
664) LUCK
67-------
68of the Good and best of varieties.
69
70
715) FEEDBACK
72-----------
73Comments, suggestions, bug reports, are all welcome. Please don't
74flame me if it doesn't work or unexpectedly trashes your system, it's
75not intended to and I apologise in advance if something goes wrong and
76causes you a problem, I'm only trying to write something that looks
77nice and is a bit of fun not destroy the world (or your computer!).
78
79It does have a frame rate limit of 30fps now, which means that on
80"modern" (this year) computers is can run fullscreen without putting
81a murderous load on your top of the range P100.
82
83This was never the case with my Pentium 100.
84
85