Puppy Linux Discussion Forum

[LazY Puppy]

[musher0]

Many thanks for this advice, LazY Puppy. Code now modified to:

[peebee]

[musher0]

[musher0]

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 handles (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!

[musher0]

I just updated/edited the post above. BFN.

[musher0]

Hello gang!

This is version 0.9.3, I consider this one good enough to be a beta version
("betas" are the versions just before official publication).

That's why I'm going to ask you to try to run this script into the ground, to
give it a rough time, to have it cough up all it's got. Be nasty, please, in
your use of this version. And report the bugs of course. Only
way this thing is going to be near-perfect for final publication.

What's new:

-- a few more Color Schemes (now 11 in all)

-- you can now define the font size for the menu titles (these two features
made available to us thanks to vovchik's new aemenu-pango)

-- access to Chromium and Vivaldi browsers' histories, in addition to those
of the MZ browsers and the old opera 12.16. If you have an sqlite app on
board, the histories will be accessed off line through your sqlite utility;
otherwise, you'll be able to do it on line, from within the browser.

-- your sqlite application can be defined as a one-liner in file
/usr/local/share/MRUF/SqlitE. The default is the sqlitemanager from the
Mozilla galaxy; you know, the one that can be added to firefox, Pale Moon
or seamonkey. There are other very good sqlite utilities available of
course, and you can specify the one you prefer/are using in that little file.

-- back-up option offered for the history files, not just erase

-- a great many number of silly dev details were remembered, and typos
corrected: things no user of sane mind wants to hear about!

-- option to launch less, console, defaultimageeditor, defaultimageviewer,
defaulttexteditor, defaulttextviewer, the four browsers above (if you have
them installed), in short: any app related to a session's history.

If the above sounds redundant, it's because it is. In short, the main
theme of this version edit was "add some redundancy". like you add oil to
a motor, to make it run more smoothly.

As communication theory goes, remove any and all redundancy from a
text or a speech, and nobody will be able to understand it. It's a bit of the
same with a menu script, if you view it as implementing (communicating)
an idea about doing this or that on your computer.

So some options in this script will appear to be offered twice, but it's only
an appearance, the contexts are different, and it's intentional to the point
of giving this menu script enough "oil", so the user feels comfortable with
it and enjoys using it.

Part of the redundancy is because I asked myself: "What would the user
think logical to go at such and such a place in this menu?" Hopefully I
provided the right answers. If not, talk to me: I'm all ears!

In conclusion, this is a menu for Puppyists and Linuxians who take
managing their apps' histories seriously, who know that managing their
apps' histories properly may save them much time and frustration during
their computer sessions. Additionally, good control of your browser
history does increase your computing safety.

BFN.
~~~~~~~~~~~~
Note -- No pics this time, I'm letting you discover!

[LazY Puppy]

Since version later 0.9.1 (2?) it doesn't "work" anymore over here.

Most entries coming with <span>... in front of the name.

Looks bad.

[musher0]

[LazY Puppy]

I'm using this from .sfs file, so I did NOT overwrite the original existing aemenu files inside of the extracted and then rebuilt .sfs file.

Missed that information about the new aemenu somehow...

Thanks

[musher0]

@Lazy Puppy: No problem. Thanks for the thanks.

@all: Please find attached MRUF version 0.9.4.

This will probably be the last version, since I ran out of ideas on how to
optimize the code!!! That said, constructive ideas from young and / or
rested brains on how to improve this menu script are still welcome!

I used as many tricks of the trade as I could master or remember to
make this version a fat 20 Kb, but still this side of 21 Kb!!!

In particular,
-- the backup and the find routines for each sub-menu have been made
into internal functions. This has saved a lot of lines.

-- I generally reduced to one instance as many repeats as I could find.

Visible to the user:

-- the "accordeon" effect has been improved. It follows the principle: no
app, no sub-menu. It is now mentioned in the Help section as well.

For example:
-- if you don't have Chromium on your Puppy at this time, the Chromium
sub-menu will not show. If later you load peebee's sfs for Chromium-44,
refresh the menu, and the Chromium sub-menu will show automatically.

-- A line in the parameters sub-menu has been added to indicate when
you last updated your MRUF list. Please see attached screen capture.

One could sort of use this as an unofficial session timer, I suppose, but
it's meant for the Recent Documents menu primarily. Check this "time
line" once in a while to see if you need to refresh your MRUF menu.

-- A new transparent icon is included. (Again, thanks to Puppus Dogfellow
for the original icon.)

-- The reduced size of the pet is due to the fact that I replaced the big
OpenSans font that was previously included with the smaller Peignot font.

To change the font manually, please find Mike Walsh's post at the top of
page 5 in this thread on how to do it. It's really simple to do.

For those of you who also use my DefaultMenu script: you can change the
font in this script from the "Dress-up/Font" section in the DefaultMenu
script. (Explanation: the MRUF script can pick up the font variable set by
the DefaultMenu script.)

~~~~~~~~~~
Before you post a new question below, please read my posts above to
make sure your subject hasn't been already answered: a lot of ground
related to this MRUF/MRUD menu has been covered in previous posts.

I guess that's it for now. Enjoy!

~~~~~~~~~~~
P.S. Attachment removed. Please use version 0.9.5
from post further down on page 7. Thanks.

[LazY Puppy]

What about less?

is it still needed?

[LazY Puppy]

Ok.

I'd just done a usual installation of the .pet package, to check this out.

Menu background is very light in color plus white text.

This is really an ugly interface to start for a new user testing this program out.

No way to find the menu to change the design to make it look like in the your screenshot.

Preferred themes/designs should NOT annoy the user and it should NOT make the user stop using the program.

Sorry, but white text on almost white backgrounds may be useful for canadians - though, it's not for the Germans!

[musher0]

[LazY Puppy]

Sorry for reverse description of text color and background color in previous post.