How to show MRU Most Recently Used Documents on Start Menu?

[ASD]

To musher0, M walsh, bigpup, P Dogfellow, RSH, peebee et al,

Please try v 0.9.5.2 (or v 0.9.5.1) on tahr-64-6.0.5 (where they ruined my respective save files) or wherever and kindly report here on your installation success or failure(s).

[musher0]

Hello ASD.

You may say whatever you like. But without evidence, your statement
has no value. If true, it only proves that you do not take backing up your
Puppies seriously. If false, everyone can draw conclusions about what
bearing false witness means.

Most of all it means that you do not know what testing a script in
development means.

MochiMoppei has answered me and he does not know you.

Is he acting on your behalf at all, or is he just a troll?

I sometimes see his posts, but I don't know him. I thought he were French.

~~~~~~~~~~
@all:

Any serious tester please get in touch with me by PM. I would like to
continue developing this menu script, but only with honest Puppy-ists
presenting serious and at least minimally documented reports. I have
found a couple of sites where true collaboration and exchange on
projects such as this one are possible.

Thanks in advance and thanks for your understanding.

[musher0]

Before this gets out of hand: this is a 32-bit package. For methodological
reasons, a 64-bit version will be considered only when the development of
this 32-bit version has been finalized.

[LazY Puppy]

To musher0, M walsh, bigpup, P Dogfellow, RSH, peebee et al,

Please try v 0.9.5.2 (or v 0.9.5.1) on tahr-64-6.0.5 (where they ruined my respective save files) or wherever and kindly report here on your installation success or failure(s).

I thought I would leave this alone until the final version would be available.

The machine I'm currently on doesn't have tahr64 605 installed, but tahr64 604 - which shouldn't make a difference at all on the mruf installation. I tried version 0.9.5.2 of mruf.

Here's the results:

- it installs fine
- though it took appr. one minute to appear on the screen at first call
- later calls it appears quite fast on the screen

Since I don't use save files/folders in general, I could not test using such save options.

Colors?

Still ugly!

Screenshot attached.

Edit:

I found the colored lines a bit annoying.

@musher0

Doesn't aemenu or aemenu-pango provide true separators for its menus?

[musher0]

To musher0, M walsh, bigpup, P Dogfellow, RSH, peebee et al,

Please try v 0.9.5.2 (or v 0.9.5.1) on tahr-64-6.0.5 (where they ruined my respective save files) or wherever and kindly report here on your installation success or failure(s).

I thought I would leave this alone until the final version would be available.

The machine I'm currently on doesn't have tahr64 605 installed, but tahr64 604 - which shouldn't make a difference at all on the mruf installation. I tried version 0.9.5.2 of mruf.

Here's the results:

- it installs fine
- though it took appr. one minute to appear on the screen at first call
- later calls it appears quite fast on the screen

Since I don't use save files/folders in general, I could not test using such save options.

Colors?

Still ugly!

Screenshot attached.

Edit:

I found the colored lines a bit annoying.

@musher0

Doesn't aemenu or aemenu-pango provide true separators for its menus?

Hello Lazy Puppy.

Many thanks for testing.
Glad to see you have the menu up, even if ugly!

I too found that version 0.9.5.2 took longer than the previous one on
initial load. My hunch is it's because I added the fonts sub-menu. The
script has to read to the list of fonts in the TTF directory before coming on
line. If you have many fonts there, it takes longer.

Also, in my DefaultMenuPlus script (on vovchik's "hacked aemenu" thread,
I have separate lists 1) of colors for titles and 2) of colors for separators,
and it is very fast, even at first launch. Granted, that one only processes
the default* files in /usr/local/bin, but still.

< time > tests on version 0.9.2 (it doesn't have the fonts sub-menu)
indicated a process time of +/- 6 seconds on first launch to get to the
menu display line (the last line of the script).

As to your last question: no, neither the original aemenu nor vovchik's
aemenu-pango provide separators. Me I like being able to create my own
separators!

Those thick separators come from the pango. I will ask vovchik if the
pango has thinner, more elegant separators. A while back, he mentioned
something about a "pango collection" of special characters.

I must say these new pango mark-ups are not easy to master. I think the
secret for beauty in such menus is sobriety: not to put in too much effects.

Again, many thanks for your test and report. Very helpful.

BFN.

[musher0]

More elegant with em-dashes?

[musher0]

Hello all.

I am quite satisfied with this new version, 0.9.5.3.

Removed:
-- the GTK & Rox Bookmarks section, as one experienced Puppyist
mentioned in a Private Message, that section was not, strictly speaking,
a "history" section. Besides, it had one parsing code problem -- which
could be solved -- and one social problem -- which could not be solved.
I hate social problems.

-- the fonts section introduced in version 0.9.5.2. While it was sane code,
depending on the number of TTF fonts you have, it occupied so much RAM
when active that it prevented changing ColorSchemes.

As I mentioned already, the fonts can be controlled from a one-liner or
from the "cousin" script MenuDefaultPlus. So a call to the latter has been
included in the Help section, to replace the fonts section. If you have this
script, it will have its entry (using the same accordion effect as described
earlier for the Chromium and other browsers).

Changed:
-- as Lazy Puppy remarked above, something had to be done to lighten
the "separators". While aemenu does not offer "separators" per se, like
for ex. jwm, pekwm or icewm, one can use the en- or em-dashes, the
regular dash "-", the wiggly "~", the underscore "_", even the letter "o".

With aemenu-pango, you also have the underline function, with options
for single, double and low underlines. The nice thing is that you can have
an underline function underlining... void.

No, this is not nihilist philosophy!!! I mean: "underlining space".
I used the double underline pango function as separator in sub-menus.

-- Finally, the thick separator between the time and the main title is
replaced with the "low underline" underneath the time.

You be the final judges, but for me, I find the new result very elegant.

So until further notice, this will be the last version of my MRUF/MRUD
script. Warm and sincere thanks to all who contributed!

Other projects await!

TWYL.

[ASD]

musher0,

Testily, only yesterday, you wrote "this is a 32 bit package".
-------------------------------------------------------------------

[musher0]

musher0,

Testily, only yesterday, you wrote "this is a 32 bit package".
-------------------------------------------------------------------

What is your point exactly?

On my very first post on this thread , I wrote:

> So here's my attempt, in view that Puppy does not seem to have a
MRU utility per se.

Ever since then I have been trying to make the script better, but these
script evolutions are still "attempts".

And before you start nit-picking at my choice of the word, here is a
definition from dictionary.com:

attempt:
noun
4.
an effort made to accomplish something:

What is it of the word "attempt" that you do not understand?

Where were you when I wrote that first message? You're a bit late now to
criticize any part of my efforts regarding this MRUF/MRUD script.

If you test any new script or software, you're expected to know the risks
involved. Even more so while these scripts or software are still in
development.

When you test a script or anything done by one of our Puppy developers,
you are expected to have read or at least perused the entire thread.

So... you don't like my script, or you don't like me personally, or you
don't like Austrians like vovchik, you don't like French-Canadians like me,
or you don't like Puppy-ists, or you don't like Linux, or you don't like 32-
bit computers, or you don't like being on planet Earth, or your mother did
not give you enough love:

"Frankly, my dear, I don't give a damn."

~~~~~~~~~~~~~
P.S. The word "testily" does not exist.

[ASD]

Flash,

Upon installation, I see a blank window, RSH sees a blank window, Puppus Dogfellow may still see a blank window.

Evidently, it's not for 64 bit use (as may be obvious) and if it's for beginners heaven help us and all Puppy versions.

Might I suggest you might consider moving this thread to another location.

[musher0]

Flash,

Upon installation, I see a blank window, RSH sees a blank window, Puppus Dogfellow may still see a blank window.

Evidently, it's not for 64 bit use (as may be obvious) and if it's for beginners heaven help us and all Puppy versions.

Might I suggest you might consider moving this thread to another location.

Hello ASD.

Now which is it? Do you see a blank window -- as you mention in your
post immediately above this one --, or did my script ruin your pupsaves
-- as you mention in your post on top of this page?

Perhaps both situations? Please provide specific details. I am unclear
about your real problem with this script.

Because technically, if it ruined your pupsaves, you wouldn't have seen
a blank window: you would have seen no window at all.

And what is the attached picture taken from your post on page 7? Is that
what you call a "blank window"? It isn't blank.

So just stop playing your psychological game. Everybody can see that
you are inventing untrue situations to spite me. In doing so, you are
hurting your own reputation, not mine.

And speaking of moderator Flash, you are infringing the second
rule of the forum:
> No starting trouble with other members - Don't post just to start
trouble with another member. All posts are to be "real" topics.

If you don't stop spreading lies about my work, I will complain to Flash
until he sees fit to suspend you.

BFN.

[ASD]

musher0,

Yet again, you write testily. Please do contact Flash - I can easily provide him with full information, but since you insist upon being obtuse just be content with your claim that I'm a liar and a fool.

[musher0]

musher0,

Yet again, you write testily. Please do contact Flash - I can easily provide him with full information, but since you insist upon being obtuse just be content with your claim that I'm a liar and a fool.

What's preventing you from posting the full information here? As I have
asked you to do at least two times. Are you afraid that your falsities will
kick you back in the face publicly?

I think by now it is clear to everyone that you are out to make me a "son-
of-a-bitch", and that you will use any and all lies and means to achieve
your goal.

You claim that you obtain a blank window with my script when you have
previously provided -- for all to see -- a screen capture in nice contrasting
colors of my script working on your computer.

What is that claim of yours if not a lie?

Please prove that I am obtuse -- when on your part you are not taking
the usual precautionary measures that all testers on this forum have
known how to take since Puppy exists; when on your part you do not
seem to suspect that there is a difference between a work in the making
and a finalized, polished, application.

I am not writing "testily". You are attacking my reputation as a developer
with lies, and I am defending myself with logical arguments. As I should.

You blame someone publicly, you provide the evidence publicly: that is
the customary rule of society. Nobody stains someone else's reputation
without evidence: no autistic person, no "regular" person, nobody. Ethics
apply to everyone.

Count yourself lucky that I am not the moderator.

[musher0]

Hello all.

I did test the script on Fatdog 701 and JL 604, which are both 64-bit
Puppies. It installs without problem under JL 604, with the icon right in
the middle of the screen, but apparently Fatdog 701 does not know what
to do with pet archives.

It seems that this version of vovchik's aemenu-pango is not 64-bit
capable. I will ask him about it.

In neither case, however, did the installation or the script "ruin" any
pupsave file or the Puppy OS. In the case of the JL 604, clicking on the
script icon or trying to run it from the console simply did nothing.

By contrast, I had nice success on Moat's beautiful ChloePup-R27, a
derivative of Precise Pup-5.27, I believe. Please see attached.

TWYL.

[Puppus Dogfellow]

tested in tahr64 605 (a derivative, but i don't think i added (as yet) anything to make it more than typically robust)--your script didn't kill it, or my save folder, but it gave me no gui and i had to reboot to get responsiveness back. no error messages in the terminal. i think it was processing things because after i activated it the machine began to slow to a crawl (took 5 minutes to merely close unsaved documents and exit geany), but no popup menu or usable functionality, so it appears it's a no go on tahr64 605 as of 9.5.3. uninstalled and rebooted (after starting an installation of 707-64 because i hit enter instead of down--i guess there were technically two reboots) and everything was back to normal.


hth

(haven't tested in 32bit but that appears to be sorted out. new menu in one of the last screenies looks good and clear to my eyes).

[musher0]

tested in tahr64 605 (a derivative, but i don't think i added (as yet) anything to make it more than typically robust)--your script didn't kill it, or my save folder, but it gave me no gui and i had to reboot to get responsiveness back. no error messages in the terminal. i think it was processing things because after i activated it the machine began to slow to a crawl (took 5 minutes to merely close unsaved documents and exit geany), but no popup menu or usable functionality, so it appears it's a no go on tahr64 605 as of 9.5.3. uninstalled and rebooted (after starting an installation of 707-64 because i hit enter instead of down--i guess there were technically two reboots) and everything was back to normal.

hth

(haven't tested in 32bit but that appears to be sorted out. new menu in one of the last screenies looks good and clear to my eyes).

Hi Puppus.

Quoting you:
>"It gave me no gui"
Do you mean no menu? Please forgive me that I do not understand: in
my mind, either you have a gui or you have a terminal.

>"i think it was processing things because after i activated it the machine
began to slow to a crawl"
That is strange. I think I read somewhere that tahpup64 comes with a 32-
bit sort of patch, like a "32-bit compatibility" sfs?

Because in JL 604 it just did nothing, as I said. I rebooted with no waiting.

This MRUD script has a lot of variables, and it does take perhaps a little
over a minute sometimes on my computer, at first launch, before the
menu pops up. So maybe the aemenu-pango was actually trying to
operate with the 32-bit compatibility patch when you rebooted?

(I may be talking through my hat here, but by comparison, trying to
launch my script on the JL 604 did absolutely nothing.)

~~~~~~~~~~
In any case, do you think you could try to compile vovchilk's aemenu-
pango on your TahrPup64? I do not have this 64-bit TahrPup.

I think a successful compile of the aemenu-pango on TahrPup 64-bit
would save a lot of people a lot of grief -- if it was offered as an option.
Thanks in advance.

(Vovchilk's source for the aemenu-pango is in one of the first posts of his
"Hacked aemenu" thread.)
~~~~~~~~~~

TWYL

[LazY Puppy]

It won't compile in tahr64 6.0.5.

It is complaining about missing a file: glibconfig.h

File /usr/include/glib-2.0/glib/gtypes.h wants include glibconfig.h.

Code: Select all

#include <glibconfig.h>

The devx doesn't contain glibconfig.h.

[Puppus Dogfellow]

Hi Puppus.

Quoting you:
>"It gave me no gui"
Do you mean no menu? Please forgive me that I do not understand: in
my mind, either you have a gui or you have a terminal.
>"i think it was processing things because after i activated it the machine
began to slow to a crawl"
That is strange. I think I read somewhere that tahpup64 comes with a 32-
bit sort of patch, like a "32-bit compatibility" sfs?

Because in JL 604 it just did nothing, as I said. I rebooted with no waiting.

hello, musher

two options in your mind but you listed three in your response, and it was a fourth--visually there was no usable interface, whether menu, popup box, terminal, console, window around a box that's supposed to resemble an old fashioned --were those things consoles or terminals, those screens? i got no window, i didn't get a menu. i just got a machine that was on its way to checking out.

This MRUD script has a lot of variables, and it does take perhaps a little
over a minute sometimes on my computer, at first launch, before the
menu pops up. So maybe the aemenu-pango was actually trying to
operate with the 32-bit compatibility patch when you rebooted?

no 32 bit compatibility sfs installed. i have a working 64 bit aemenu, though. it crippled the machine--couldn't do anything and trying to escape without losing work was a bit of a chore. doing nothing (option three above) would've been preferable.

(I may be talking through my hat here, but by comparison, trying to
launch my script on the JL 604 did absolutely nothing.)

if you want a wild shot in the dark to hit something else to blame--i saw sh in lx task--it could've been that slocate update script--that thing has ill effects on my machine when it's searching /home and or /root. maybe both were going at the same time? more than one unadorned "sh"es. slocate update definitely appears as a "sh" in the lxtask window...

didn't realize the 32bit compatibility sfs was a prerequisite (is it? it's 100mb...) as i hadn't really read over the thread in months.

In any case, do you think you could try to compile vovchilk's aemenu-
pango on your TahrPup64? I do not have this 64-bit TahrPup.

i see LazyPuppy's already on it, though i actually had little inclination to do so--the default aemenu black on light gray goes with my themes and is very readable. i've been looking at what vovchik's done with some interest (and less understanding), and maybe one day soon (old people time) i'll get on it...

i like your idea of making the menus customizable using the menu itself, but since this script already "has a lot of variables" and "does take perhaps a little over a minute sometimes on [your] computer, at first launch, before the menu pops up" due to its complexity and involvement with the system, i think it would be better to get the functionality part ironed out first. it more than does nothing ( ) in tahr64, but as i said, i didn't load the 100 meg sfs file.

if you want to focus on the eye candy aspect, maybe write a script to offer all preexisting aemenus a chance to add a dress up slot?

sorry if not as helpful as you'd hoped.

[musher0]

Hello Puppus.

I thank you for the description you have provided.

And I consider you a friend. You have contributed an icon to this script,
and we had a couple of interesting and friendly exchanges in the past.

So please do not take the following the wrong way.

-- I find it strange that you are using my slocate wrapper when you don't
appear to be comfortable with it. I would never use a script or program
that I am not comfortable with.

I've been using that slocate script every day since I produced it without
problems. It does slow down some processes when it's active, only for
what, a minute?, every three hours, if I am working on the same drive
that it's indexing, it seems. I find that I can live with that inconvenience
given the benefit of having my computer files indexed and searchable at
a moment's notice.

Also, are you saying that my slocate wrapper is working OOTB on a
64-bit Puppy?

-- What made you --or anyone -- believe that what has been a 32-bit
script from its beginning five years ago could run on any 64-bit Puppy at
this time? Besides, it is not uncommon even on 32-bit Puppies that a
certain app or script will run on this Puppy but not on that other one.

Again, forgive me if I sound dumb, but I really do not understand this
"quasi-demand" all of a sudden (to me it seems so) from a number of
persons on this thread that a script developed on 32-bit Puppies off and
on for the past five years should have to run without fail on any 64-bit
Puppy.

I do not want to get in a fight with you, I want to preserve good
camaraderie. Also I know that you are sincere.

Thanks in advance for any "enlightenment".

Bye for now.

[musher0]

It won't compile in tahr64 6.0.5.

It is complaining about missing a file: glibconfig.h

File /usr/include/glib-2.0/glib/gtypes.h wants include glibconfig.h.

Code: Select all

#include <glibconfig.h>

The devx doesn't contain glibconfig.h.

Hi Lazy Puppy.

Just a note to let you know that I have just sent a "heads-up" about the
problem to vovhick.
http://murga-linux.com/puppy/viewtopic. ... ost#924498

BFN.