#x11cp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #x11cp, aggregated by home.social.
-
https://www.xteddy.org/xwinman/
I mirrored this some time ago, hoping that the original (https://www.xwinman.org) never went away.
Alas, it has.
Matt Chapman created xwinman.org at just the right time, to allow for a good selection of DEs and WMs to be documented -- with screenshots -- and where applicable -- configuration files as well.
I know that for many, it was a really good resource to discover what was out there and for people to reuse components from config files to customise their own environment.
Good luck trying to do this on Wayland...
It's a snapshot in time when things were simpler and the choice for the user was at its peak. Again... Wayland will never offer this degree of flexibility because XServer needed you to handle window management.
Nowadays, Giles Orr provides a more up-to-date list of WMs which you can see here:
https://www.gilesorr.com/wm/xwmtable.html
Although some of curation is arguably opinionated.
But I wanted to raise the fact that xwinman.org is mirrored, and that it's a very interesting resource.
As it happens, one of Matt Chapman's programs, xtt, is something I've included #x11cp:
-
https://www.xteddy.org/xwinman/
I mirrored this some time ago, hoping that the original (https://www.xwinman.org) never went away.
Alas, it has.
Matt Chapman created xwinman.org at just the right time, to allow for a good selection of DEs and WMs to be documented -- with screenshots -- and where applicable -- configuration files as well.
I know that for many, it was a really good resource to discover what was out there and for people to reuse components from config files to customise their own environment.
Good luck trying to do this on Wayland...
It's a snapshot in time when things were simpler and the choice for the user was at its peak. Again... Wayland will never offer this degree of flexibility because XServer needed you to handle window management.
Nowadays, Giles Orr provides a more up-to-date list of WMs which you can see here:
https://www.gilesorr.com/wm/xwmtable.html
Although some of curation is arguably opinionated.
But I wanted to raise the fact that xwinman.org is mirrored, and that it's a very interesting resource.
As it happens, one of Matt Chapman's programs, xtt, is something I've included #x11cp:
-
#xmeltdown is an application written by David Lemke, released in 1990.
Its purpose is to create a melting effect on all connected monitors. Nothing serious, it seems, but a lot of fun!
For more information, see: https://x11cp.org/apps/xmeltdown/
This application was the first by a contributor. Whoo!
-
#xmeltdown is an application written by David Lemke, released in 1990.
Its purpose is to create a melting effect on all connected monitors. Nothing serious, it seems, but a lot of fun!
For more information, see: https://x11cp.org/apps/xmeltdown/
This application was the first by a contributor. Whoo!
-
#xtt (XTimeTable) is an application written by Matt Chapman (of www.xwinman.org fame).
It's a simple application written in #x11 (using #libxpm) to display recurring events throughout the working week -- which in this case is a static timetable of university lectures.
The entries shown can be colour-coded (via X11 colour names - which would have been in rgb.txt).
The day's schedule is assumed to be static -- that is, one entry per hour, and a working day of 09:05 - 17:05 -- hence there can only ever be 9 entries per day at most.
I really like this application as it shows just how versatile this application could be - as well as it not being over-engineered to use #electron, which is precisely what many people writing something like this now would use.
Fools!
-
#xtt (XTimeTable) is an application written by Matt Chapman (of www.xwinman.org fame).
It's a simple application written in #x11 (using #libxpm) to display recurring events throughout the working week -- which in this case is a static timetable of university lectures.
The entries shown can be colour-coded (via X11 colour names - which would have been in rgb.txt).
The day's schedule is assumed to be static -- that is, one entry per hour, and a working day of 09:05 - 17:05 -- hence there can only ever be 9 entries per day at most.
I really like this application as it shows just how versatile this application could be - as well as it not being over-engineered to use #electron, which is precisely what many people writing something like this now would use.
Fools!
-
#xtt (XTimeTable) is an application written by Matt Chapman (of www.xwinman.org fame).
It's a simple application written in #x11 (using #libxpm) to display recurring events throughout the working week -- which in this case is a static timetable of university lectures.
The entries shown can be colour-coded (via X11 colour names - which would have been in rgb.txt).
The day's schedule is assumed to be static -- that is, one entry per hour, and a working day of 09:05 - 17:05 -- hence there can only ever be 9 entries per day at most.
I really like this application as it shows just how versatile this application could be - as well as it not being over-engineered to use #electron, which is precisely what many people writing something like this now would use.
Fools!
-
#xtt (XTimeTable) is an application written by Matt Chapman (of www.xwinman.org fame).
It's a simple application written in #x11 (using #libxpm) to display recurring events throughout the working week -- which in this case is a static timetable of university lectures.
The entries shown can be colour-coded (via X11 colour names - which would have been in rgb.txt).
The day's schedule is assumed to be static -- that is, one entry per hour, and a working day of 09:05 - 17:05 -- hence there can only ever be 9 entries per day at most.
I really like this application as it shows just how versatile this application could be - as well as it not being over-engineered to use #electron, which is precisely what many people writing something like this now would use.
Fools!
-
#xtt (XTimeTable) is an application written by Matt Chapman (of www.xwinman.org fame).
It's a simple application written in #x11 (using #libxpm) to display recurring events throughout the working week -- which in this case is a static timetable of university lectures.
The entries shown can be colour-coded (via X11 colour names - which would have been in rgb.txt).
The day's schedule is assumed to be static -- that is, one entry per hour, and a working day of 09:05 - 17:05 -- hence there can only ever be 9 entries per day at most.
I really like this application as it shows just how versatile this application could be - as well as it not being over-engineered to use #electron, which is precisely what many people writing something like this now would use.
Fools!
-
From the README:
#icao is an interactive program running under #x11 #motif. Its input is a so
called "world file", which is an ASCII file containing descriptions of objects
such as airports, roads, towns, radio beacons and the like. ICAO will use
either Lambert or Mercator projection to generate a map from this world file,
either on your screen or as PostScript output.ICAO allows you to interactively work with the map on the screen, i.e. scroll
it, use a rubber line to measure distances and tracks etc. Additional features
are available for both motorized flights and soaring. -
From the README:
#icao is an interactive program running under #x11 #motif. Its input is a so
called "world file", which is an ASCII file containing descriptions of objects
such as airports, roads, towns, radio beacons and the like. ICAO will use
either Lambert or Mercator projection to generate a map from this world file,
either on your screen or as PostScript output.ICAO allows you to interactively work with the map on the screen, i.e. scroll
it, use a rubber line to measure distances and tracks etc. Additional features
are available for both motorized flights and soaring. -
As part of the #x11cp I'm working on, I have also begun getting #mgr working. It's a slightly difficult task, but worth it
So far, I'm working through fixing compiler issues.
More info here:. https://hack.org/~mc/mgr/
Historically this is important. I hope @mc agrees. I'm sure he won't mind me resurrecting this.
It's going to be fun!
-
As part of the #x11cp I'm working on, I have also begun getting #mgr working. It's a slightly difficult task, but worth it
So far, I'm working through fixing compiler issues.
More info here:. https://hack.org/~mc/mgr/
Historically this is important. I hope @mc agrees. I'm sure he won't mind me resurrecting this.
It's going to be fun!
-
It's time (yes, literally) for another clock application.
This time (heh!), it's #xdotclock which as the name suggests, draws a digital clock from a series of dots. It does this using nothing more than xlib.
It was originally written by Haran Shivanan, sometime in 2003-July-07
The README highlights the following:
"It runs in both 12 hour and 24 hour modes and is somewhat configurable. You can display the clock in arbitrary colors or have it continuously shift colors, control the speed at which the particles move around and the size of the particles."
To get this to compile, I had to remove the GCC flag of `-m486` -- that's no longer supported.
What's interesting here though is the effect that has on the cycling between colours. That's now *very* fast, and although you can control that with the `-speed` option to introduce a delay, this isn't now working, since the CPU power has increased so much since the 486, that I'm going to have to modify the code to bring this option inline with more modern hardware.
Anyhow, screenshots attached! The "green" clock is meant to represent the cycling between colours -- and don't get me wrong, it does work, it's just *fast*! :)
-
It's time (yes, literally) for another clock application.
This time (heh!), it's #xdotclock which as the name suggests, draws a digital clock from a series of dots. It does this using nothing more than xlib.
It was originally written by Haran Shivanan, sometime in 2003-July-07
The README highlights the following:
"It runs in both 12 hour and 24 hour modes and is somewhat configurable. You can display the clock in arbitrary colors or have it continuously shift colors, control the speed at which the particles move around and the size of the particles."
To get this to compile, I had to remove the GCC flag of `-m486` -- that's no longer supported.
What's interesting here though is the effect that has on the cycling between colours. That's now *very* fast, and although you can control that with the `-speed` option to introduce a delay, this isn't now working, since the CPU power has increased so much since the 486, that I'm going to have to modify the code to bring this option inline with more modern hardware.
Anyhow, screenshots attached! The "green" clock is meant to represent the cycling between colours -- and don't get me wrong, it does work, it's just *fast*! :)
-
It's time (yes, literally) for another clock application.
This time (heh!), it's #xdotclock which as the name suggests, draws a digital clock from a series of dots. It does this using nothing more than xlib.
It was originally written by Haran Shivanan, sometime in 2003-July-07
The README highlights the following:
"It runs in both 12 hour and 24 hour modes and is somewhat configurable. You can display the clock in arbitrary colors or have it continuously shift colors, control the speed at which the particles move around and the size of the particles."
To get this to compile, I had to remove the GCC flag of `-m486` -- that's no longer supported.
What's interesting here though is the effect that has on the cycling between colours. That's now *very* fast, and although you can control that with the `-speed` option to introduce a delay, this isn't now working, since the CPU power has increased so much since the 486, that I'm going to have to modify the code to bring this option inline with more modern hardware.
Anyhow, screenshots attached! The "green" clock is meant to represent the cycling between colours -- and don't get me wrong, it does work, it's just *fast*! :)
-
It's time (yes, literally) for another clock application.
This time (heh!), it's #xdotclock which as the name suggests, draws a digital clock from a series of dots. It does this using nothing more than xlib.
It was originally written by Haran Shivanan, sometime in 2003-July-07
The README highlights the following:
"It runs in both 12 hour and 24 hour modes and is somewhat configurable. You can display the clock in arbitrary colors or have it continuously shift colors, control the speed at which the particles move around and the size of the particles."
To get this to compile, I had to remove the GCC flag of `-m486` -- that's no longer supported.
What's interesting here though is the effect that has on the cycling between colours. That's now *very* fast, and although you can control that with the `-speed` option to introduce a delay, this isn't now working, since the CPU power has increased so much since the 486, that I'm going to have to modify the code to bring this option inline with more modern hardware.
Anyhow, screenshots attached! The "green" clock is meant to represent the cycling between colours -- and don't get me wrong, it does work, it's just *fast*! :)
-
It's time (yes, literally) for another clock application.
This time (heh!), it's #xdotclock which as the name suggests, draws a digital clock from a series of dots. It does this using nothing more than xlib.
It was originally written by Haran Shivanan, sometime in 2003-July-07
The README highlights the following:
"It runs in both 12 hour and 24 hour modes and is somewhat configurable. You can display the clock in arbitrary colors or have it continuously shift colors, control the speed at which the particles move around and the size of the particles."
To get this to compile, I had to remove the GCC flag of `-m486` -- that's no longer supported.
What's interesting here though is the effect that has on the cycling between colours. That's now *very* fast, and although you can control that with the `-speed` option to introduce a delay, this isn't now working, since the CPU power has increased so much since the 486, that I'm going to have to modify the code to bring this option inline with more modern hardware.
Anyhow, screenshots attached! The "green" clock is meant to represent the cycling between colours -- and don't get me wrong, it does work, it's just *fast*! :)
-
#x11cp #x11 #archaic application.
Another clock application! This time, it's #xarclock, written by Jaime Garcia Ghirelli, somtime in April 1994.
The README says:
"If clocks had been invented in Argentina (southern hemisphere), they would run anti-clockwise. Down there a sundial runs the other way around!
The program is an extension of the standard X clock widget. New features are: Configurable direction of rotation and font support in analog mode."
Interesting, indeed! So here's a screenshot showing a clock with roman numerals going clockwise, and a different clock showing the time going anti-clockwise.
You can also change the colours of the hands and render the clock in reverse colour (think b&w displays).
Fun!
-
#x11cp #x11 #archaic application.
This time, it's #xsclock which is a 56x56 #dockapp intended to be used in #afterstep's wharf module, but equally applies to #fvwmbuttons as well.
Originally written by Namio MATUDA, around 1999-Nov-24. The version I have here is 0.22
There is only one option `--day` which shows the day/month in the window.
Screenshots attached.
-
#x11cp #x11 #archaic application.
This time, it's #xsclock which is a 56x56 #dockapp intended to be used in #afterstep's wharf module, but equally applies to #fvwmbuttons as well.
Originally written by Namio MATUDA, around 1999-Nov-24. The version I have here is 0.22
There is only one option `--day` which shows the day/month in the window.
Screenshots attached.
-
#x11cp #x11 #archaic application.
This time, it's #xsclock which is a 56x56 #dockapp intended to be used in #afterstep's wharf module, but equally applies to #fvwmbuttons as well.
Originally written by Namio MATUDA, around 1999-Nov-24. The version I have here is 0.22
There is only one option `--day` which shows the day/month in the window.
Screenshots attached.
-
#x11cp #x11 #archaic application.
This time, it's #xsclock which is a 56x56 #dockapp intended to be used in #afterstep's wharf module, but equally applies to #fvwmbuttons as well.
Originally written by Namio MATUDA, around 1999-Nov-24. The version I have here is 0.22
There is only one option `--day` which shows the day/month in the window.
Screenshots attached.
-
#x11cp #archaic #x11 application.
This time it's a #toolbar written in #motif. #xmtoolbar
#xmtoolbar was written sometime in 1995 -- I cannot find the author's name, apart from 'Spiff'.
It's a catchy name, but there were quite a few toolbars like this which emulated #fvwm goodstuff, which was a forerunner to what is now #FvwmButtons
With #xmtoolbar you can build up a panel with pixmap icons (XPMs) and launch programs. In #xmtoolbar's case, this can be done interactively and then the running configuration can be saved to disk for #xmtoolbar to load next time.
What do I mean by this? Well...
-
#x11cp #archaic #x11 application time!
#Plotmtv is a multipurpose X11 plotting program.
It is not responsible for drawing graphs relating to the popular music TV channel.
Originally written by Kenny Toh (1995-07-16).
The graphics library is just using raw X11. Amazing.
The plot-types supported are as follows:
* contour plots (rectangular grid, as well as triangular mesh)
* 2D line and scatter plots (x vs-y)
* 3D surface , line and scatter plots
* vector plots
* probability plots
* histograms
* barchartsThe program has an rough but functional Graphical User
Interface, through which it is possible to zoom in, zoom out, pan, toggle between 2D and 3D plots, and rotate 3D plots. Both color and grayscale postscript output are
supported.I, for one, really like it! Move over, #gnuplot! :)
-
#x11cp #archaic #x11 application time!
#Plotmtv is a multipurpose X11 plotting program.
It is not responsible for drawing graphs relating to the popular music TV channel.
Originally written by Kenny Toh (1995-07-16).
The graphics library is just using raw X11. Amazing.
The plot-types supported are as follows:
* contour plots (rectangular grid, as well as triangular mesh)
* 2D line and scatter plots (x vs-y)
* 3D surface , line and scatter plots
* vector plots
* probability plots
* histograms
* barchartsThe program has an rough but functional Graphical User
Interface, through which it is possible to zoom in, zoom out, pan, toggle between 2D and 3D plots, and rotate 3D plots. Both color and grayscale postscript output are
supported.I, for one, really like it! Move over, #gnuplot! :)
-
#x11cp #X11 #archaic application time!
#xzoom is a magnifier for X11, allowing for portions of windows or the desktop to be magnified.
#xzoom was originally written May 30th 1996, by Itai Nahshon.
Version 0.3 only supported 8-bit colour displays, but version 0.4 onward is maintained, and this supports upto 24-bit displays, and it's this version which most Linux distributions, and *BSD still ship to this day.
I've been using this program for years, and I find it really useful debugging window decorations in #fvwm3, as I can zoom in at detail to see how the rendering looks pixel-by-pixel.
-
Hey all,
I've had a lot of interest in my recent #archaic #x11 application posts, which is nice to see.
Given that, I've now launched the #x11cp "X11 Conservancy Project" which is going to be me adding and maintaining these sources so that they hopefully live on in a meaningful way.
More information can be found here: https://x11cp.org/
If anyone's interested in helping, let me know. As you can probably tell, HTML is not my strong point at all, so if anyone wants to help with that, do let me know.
-
Hey all,
I've had a lot of interest in my recent #archaic #x11 application posts, which is nice to see.
Given that, I've now launched the #x11cp "X11 Conservancy Project" which is going to be me adding and maintaining these sources so that they hopefully live on in a meaningful way.
More information can be found here: https://x11cp.org/
If anyone's interested in helping, let me know. As you can probably tell, HTML is not my strong point at all, so if anyone wants to help with that, do let me know.
-
#x11cp #archaic #x11 application
This time, it's #vgp
#vgp is a Vector Globe Projection application, which allows for visualising vectors which change over time.
It's designed for engineers or scientists to model how different vectors can change across three different axis.
Originally written by Frederick A. Niles, November 1995.
The program accepts a data file parameter on the command line, and the data file itself consists of rows (vectors) of three parts each, describing the X, Y and Z axis. For example:
0.000000 0.000000 0.000000
-0.376300 -0.537412 0.754710
-0.381369 -0.565402 0.731354The default dataset represents a globe which can be rotated in real time.
I love this -- a really niche yet interesting program which solves a very specific purpose, but can be reused to visualise anything that's vector-based.
-
This time it's #mgdiff
#mgdiff is a graphical frontend to the #diff command, written using #motif. It was originally inspired by a program called #gdiff which only ran on SGI machines.
It allows for viewing the difference between two files and to write out the merged result to a third file, if desired.
This is version 1.0, 1994, by Daniel Williams.
#mgdiff implements the implements the Scrolled Region recommendations of Section 2.3.4 of the OSF/Motif Style Guide (release 1.1), meaning that the arrow and paging keys will work to scroll as well.
I had to tweak the code only a little to override a custom getline() implementation.
I also recall using this application in ~1996.
Fun times!
-
This time it's #mgdiff
#mgdiff is a graphical frontend to the #diff command, written using #motif. It was originally inspired by a program called #gdiff which only ran on SGI machines.
It allows for viewing the difference between two files and to write out the merged result to a third file, if desired.
This is version 1.0, 1994, by Daniel Williams.
#mgdiff implements the implements the Scrolled Region recommendations of Section 2.3.4 of the OSF/Motif Style Guide (release 1.1), meaning that the arrow and paging keys will work to scroll as well.
I had to tweak the code only a little to override a custom getline() implementation.
I also recall using this application in ~1996.
Fun times!
-
#x11cp #archaic #x11 #application
This time, it's #xmgf.
#xmgf is an interactive tool for manipulating gf files (postscript). It uses #motif as its widget library.
This is version 2.4, released on 1994/09/05, ny Paul Hoad of Godalming, Surrey, England. He originally worked as part of the department of Electronic Engineering.
This program can be considered an early form of CAD application (Computer Aided Design).
-
@ephemeris -- indeed. #sunclock (and #xtide) are on my list, as they're #x11 applications I've used a lot in the past.
#sunclock is "a fancy clock for the X Window system, providing local time a fancy clock for the X Window system, providing local time (legal time and solar time), sunrise, sunset and various geographical data through a point and click interface".
Translated -- this means it has an interface, which even after reading the manpage makes bugger all sense. ;)
I do love it though -- and it's still packaged my most Linux distros, and you can certainly still find it on the BSDs.
This application is worth exploring as it can do a lot of things I wouldn't know where to begin to highlight here.
Screenshot below. For me (in England), it's night-time, but perhaps not too long now until dawn? :)
-
@ephemeris -- indeed. #sunclock (and #xtide) are on my list, as they're #x11 applications I've used a lot in the past.
#sunclock is "a fancy clock for the X Window system, providing local time a fancy clock for the X Window system, providing local time (legal time and solar time), sunrise, sunset and various geographical data through a point and click interface".
Translated -- this means it has an interface, which even after reading the manpage makes bugger all sense. ;)
I do love it though -- and it's still packaged my most Linux distros, and you can certainly still find it on the BSDs.
This application is worth exploring as it can do a lot of things I wouldn't know where to begin to highlight here.
Screenshot below. For me (in England), it's night-time, but perhaps not too long now until dawn? :)
-
"And the moonbeams kissed the sea: what is all this sweet work worth" -- Shelley
#xmoontool is an #x11 application displaying real time information about the moon.
It uses #Xt and #motif as its main widgets.
Written by John Walker and Ron Hutchins, sometime in 1989, although this version originally ported to "OpenWindows" turned up sometime in December 1991.
I didn't have to modify the code to get it to compile.
When it is iconified, it shows what the moon looks like in the sky (see images attached).
This only works on 8-bit colour-depth displays due to how the XVisuals are used to render the pixmaps.
Interestingly, the following books were used as a mathematical aid for the program to calculate moon things:
"Practical Astronomy With Your Calculator" by Peter Duffett-Smith, Second Edition, Cambridge University Press, 1981.
"Astronomical Formulae for Calculators" by Jean Meeus, Third Edition, Willmann-Bell, 1985.
"Planetary Programs and Tables from -4000 to +2800" by Pierre Bretagnon and Jean-Louis Simon, Willmann-Bell, 1986.
"Celestial BASIC" by Eric Burgess, Revised Edition, Sybex, 1985.
"Astronomy: From the Earth to the Universe" by Jay M. Pasachoff, Second Edition, Saunders College Publishing, 1983The red dot you can see on the iconified window is commemorative, showing Tranquility Base, to mark the 20th anniversary of Apollo 11 (at the time).
What lunatics! #x11cp
-
#x11 application time!
This is #xdtm which is a "graphical shell for X". It appears to be a file manager and application launcher combined.
Originally written by Edward Groenendaal, Ramon J. Santiago, and Lionel Mallet, circa 1991 - 1995.
It uses the X Toolkit widgets.
It comes with a standard set of XBM icon files to represent most file types. Some of the builtin application shortcuts assume #csh as the default shell, but this can be changed.
The xdtmrc configuration file has its own grammar, courtesy of a lovely lex/yacc grammar definition. #x11cp
-
All the colours! (#colors).
This is another #archaic #x11 program, which follows on from #xmcolor in many respects, and one which I recall using a lot!
#xcolors is both a visualisation of all the colours availabe (via rgb.txt) as well as a means of seeing how background and foreground colours interact -- which is the main purpose of this program.
Originally written in 1989 by Paul Vixie (of cron(1) fame), the version here is written by Stephen Gildea, in 1991.
To this day, I did not have to modify the code, everything just worked!
It's a program written using Xt (the X Intrinsics Library).
Here are all the colours in their glory! #x11cp
-
Invest wisely!
#Xinvest is an #x11 #motif program which provides personal finance tracking and performance capabilities.
Originally written by Mark Buser, 1997.
The financial data was stored separately in an external text file, and once loaded into #Xinvest, could then be used to draw charts, perform financial forecasting, etc. (The panel on the top-left shows the format).
There appears to be support for #CDE. It looks as though it hooked into CDE's session manager so it could be launched under CDE. Nice.
-
It's #archaic #x11 application time!
This time, it's #xmcolor (the Motif Color Picker), written by Ti Kan. I believe this was written sometime in 1994. The embedded ident marker indicates: `@(#)xmcolor.c 1.11 94/12/05`
This was developed using Xt and #motif, and provides a means of mixing one's own colours, as well as using pre-defined colours from `rgb.txt`. One could then select the hexadecimal string for that colour.
It operates on 8-bit colour-depth displays only, which is why I have been running this inside #Xephyr so I can emulate this.
To this day, it compiles just fine -- only very minor tweaking from myself. Not bad for a program that's ~28 years old!
I really like how simple and self-contained so many of these applications were, and how much of a teaching aid it meant for someone to write them. The source file has 1066 lines in it -- quite a lot when you consider how much of that is Xt/Xm boilerplate.
These days, you'd just use a colour-picker from google without giving it a second thought. #x11cp
-
I can count!
Well, with the help of #xabacus, an #x11 "game" which simulates how an #abacus works, and also how powerful computers have become!
https://www.ibiblio.org/pub/X11/contrib/applications/xabacus.README
This version I'm running is 5.5.2 released in late 1999. It still compiles to this day without any modification from myself.
In fact, out of the same code base, I have two versions. One using the X Intrinsic Toolkit, and the other using #motif. #x11cp