Hello all.
Please receive version 0.9.2.1. Lots of refinements in code (one thanks to
Lazy Puppy, above), and some in design.
Aside from fine-tuning some code and reworking the internal script present-
ation in order to make it more readable even for myself (no kidding!)
,
most noticeable to the average user will be
the addition of 16 Color
Schemes. (Please see attached screen capture.)
I'm certainly no graphic designer; my son is, but not me!!! So go ahead
and criticize my choices of colors all you want!
The important thing is
that I now know how to implement color schemes. We have a simple way
to do it.
I do invite those who have talent in this area to suggest more pleasant
Color Schemes directly in a post here or in the form of little files (such as
those in /usr/local/share/MRUF). They should be easy to incorporate.
If you need inspiration, here is an excellent site about color combinations:
http://www.colorcombos.com/index.html.
(This added feature is a late answer to Puppus Dogfellow's concern a
couple of pages back.)
~~~~~~~~~
Speaking of /usr/local/share/MRUF, that's where all the data that the script
uses is now stored. /var/tmp is just not constant enough. (That's a late
answer to Mike Walsh's concern a couple of pages back.) So no surprises,
if you choose a color scheme for this MRUF/MRUD utility today, that same
color scheme will be preserved for your session tomorrow.
~~~~~~~~~
New feature: access of the Vivaldi browser history. Since Vivaldi is a
Chromium-type browser, perhaps in a coming version access to the
Chromium history could be added using similar code. You're welcome to
contribute info on how to do it.
(Since I'm not a Chromium user and know nothing about it, I didn't want
to code anything silly. I'm just launching the idea. As I mentioned, any
help on how to do it will be welcome.)
~~~~~~~~~
An expanded xdg-open script is included, to play it safe in particular with
the bash scripts. If you don't like it, or if you're a risk-taker, at the bottom
of that new xdg-open file, I mention how to get the old one back.
(But now you've been warned! For example: there is indeed a risk involved
in re-running a "remove" script of any kind. So any script is treated as a
text in the context of this utility.)
Before you ask:
using this new < xdg-open > does NOT affect any
regular launching of any app or script outside this MRUF utility, from any
WM menu or from any terminal.
To me, it was a matter of approach, of philosophy: in this script, I put my
weight more on memory-jogging and less on the re-running of executables.
I'm sure some devs have approached their MRUF/MRUD utility mainly from
the re-running perspective: let them take responsibility for it. I just didn't
feel comfortable personally with the idea of helping a user re-run an app or
script that could do damage to his work or OS.
~~~~~~~~~
Coding may look easy from the outside, but there's always an effort
involved, mental but even physical. And this project in particular demanded
a lot of effort because of the great extension of the subject: to successfully
complete a script tackling program histories, not only do you need to know
the apps, but you need to get handle
s (plural form intentional) on how
they are launched, how they store data and how to fish out this data.
So I'll be "hanging my coding skates" for a few days to be able to enjoy
the fresh air. You're of course welcome to leave bug reports -- or praises
-- below, but I won't be responding immediately: musher0 will be out
enjoying life
for a while.
"See" you then!