Puppy Linux Discussion Forum

[musher0]

@Lazy Puppy:

Have you read vovhick's reply in the Hacked aemenu thread about a 64-
bit aemenu-pango? I have put the link above.

I understand from his message that he is not equipped for 64-bit
compiling at this time.

You can easily enough find the entire aewm package for 64-bit. (aemenu
is part of the aewm package, but can be used separately.) For ex., here:
https://pkgs.org/debian-jessie/debian-main-amd64/aewm_1.3.12-3_amd64.deb.html

But only vovchik has the recipe to turn the regular aemenu into
aemenu-pango!

BFN.

[LazY Puppy]

Yes, I had read this already.

I hoped he would attach the glibconfig.h, though it probably doesn't make sense as it may differ from the version for 64bit.

I would like to compile but no chance without that .h file.

Probably there's some more .h files missing in devx's of 64bit puppies.

At least Slacko64 630 is missing it too.

Users needs the firmware, developers needs the .h files - anything else is crap.

Puppy turns more and more into crap lately rather than evolving to a true USER's OS.

Windows users stuck on the double click (disaster) and Puppy developers stuck an SMALL SMALL SMALL SAVEFILE SAVEFILE SAVEFILE (folder).

Puppy's FUN FUN FUN FUN FUN FUN FUN FUN is decreasing.

[LazY Puppy]

Checked the devx's of

- lucid 528-4
- precise 571
- tahr 602, 605
- tahr64 605
- vivid beta2
- unicorn 60
- xenial 704
- xenial64 707
- slacko64 630

All of them are missing the glibconfig.h !!!

I wonder how vovchick could compile...

[musher0]

Hello, Lazy Puppy.

FYI: Using vovchik's source directory, I just tried the same compile as
you on JL64-604 and got the same error message about that
glib-bla-bla.h file missing.

Also I had the error message that the .pc package file pango.pc was
missing. Is this particular to JL64-604? Ot did you get that error
message also?

However I got aewm's aedesk and aesession secondary files compiled in
64-bit using simply the usual < make > command.

Moral of this story: a 64 version is possible. But no aemenu-pango-64
yet, ha-ha. (Strum big guitar or hit big piano chord on the last "ha"!)

BFN.

[musher0]

Another ha-ha, this one with "eureka" meaning!

http://www.ask.com/web?qsrc=1&o=0&l=dir&q=glibconfig.h&qo=serpSearchTopBox

See the first two entries.

(Stop complaining about Puppy being less and less fun!
The Ubuntu people have the problem too!!! )

BFN.

[musher0]

Hello all.

Please find attached version 0.9.5.4.

This one has significant improvements, I think, in particular at the
presentation level.

New:
-- At first run, it will look for usable settings in your current gtkrc theme
file and use them for your first display. (You can recreate the first run
situation by going to dir. /usr/local/share/MRUF and copying the back-up
template file named "FirstRun.txt" to "FirstRun".)

More details about trying to pick up the colors of the current GTK theme
below, but it works +/- 75 % of the time, which is a significant statistic,
given the diversity of GTK themes and theme engines.

-- A few sub-menus now have information lines, in particular to help the
user distinguish between the images in the mtpaint history and those in
the "recently used" xbel history file. (With EN<->FR translations.)

-- Some subtle, cosmetic changes in the placement of some bullets to
improve the consistency of the look.

-- The script code itself is now down to 16 k (optimization mostly through
the use of internal functions)

-- A splash panel is shown at every update of color theme or history data.

-- The secondary color for the separators is now taken from either the GTK
theme or the provided color schemes. Previously it was static, always
"SeaGreen2".

-- As I explained above to RSH, I am now using the pango's underline
function as separators in the sub-menus and for the time display.

~~~~~~~~~
About the colors, which created some frustration earlier:

There is a new GetGtkTheme script that probes and parses the chosen
(current) GTK theme colors.

Using this script, 75 % of the 96 themes on my Pup load correctly (please
see attached gnumeric test sheet). That said, your results may vary, 'cause
GTK themes are like plants in the jungle, there are so many of them.

The rendition of some of them is pale (not much contrast), but readable,
which enables you to install one of the provided color themes for better
readability.

A few themes will trigger the error panel in the script, but will nevertheless
use your chosen theme colors -- with the foreground and background
colors of the previous theme, however. So again, you have something
readable and you can then go choose a suitable contrasting Color Scheme
from those provided. The samples on that list are colored as they will
appear in your menu.

Finally, in some cases the script just gives you exactly the colors and
contrast you need without you having to do anything. (Wow.)


~~~~~~~~~~~~~~~~~

The experience of the past few days have made me a little less naive about
the intentions of people, so here it is in clear:

-- this is a 32-bit script

-- there have been some reports of strange behavior on the 64-bit TahrPup
after using this script (why TahrPup in particular I do not know; I have had
no problem at all trying to run this script on the JL64-604, which is my 64-
bit Puppy [it simply didn't run; it didn't affect anything in the system])

-- you are expected to have perused the previous pages of this thread
before testing this script

-- you are expected to have some Linux and/or Puppy experience to be able
to test this script properly. Testing is not recommended for newbies.

-- you are expected to test intelligently, with a bit of methodical doubt.

-- yes this script is still experimental (alpha, or whatever you want to call it).
This script is not for production use yet.

-- this thread is a lab for this script

-- like in any lab, you the tester are expected to use due diligence and
"protective gear". In computer terms: backup your Pup OS and data and
computer properly before you start testing this or any new script.

-- I have taken great care in writing and testing this script, and I have run it
through all kinds of situations, but there is an almost infinite variety of
Puppies and hardware out there. Your results may vary.

-- I am only human. "Errare humanum est." (To err is human.)
Meaning: there are likely still involuntary bugs in there. That's why i'm
putting this script out there, so we can at some point with your help evolve
a script that is as perfect as possible.

-- Moral of this insert: Use at your own risk. I'm sure I forgot a few
items but you get the idea.

-- i almost forgot: I believe in collaboration and in co-operation. If you try
to take advantage of me or to prove me a lesser person because of that, or
to be generally a "free rider", as that's called in the jargon of co-ops:
it will be on you.

~~~~

-- If you encounter problems using this script, please report back with as
many details as possible: that's your part of the deal.

Please be polite in your report and please do not suppose I am out to get
your goat or your computer. I am not and here's why:

Vovchik's aemenu-pango is only a few months old, we are very fortunate
to have a person of such talent on Puppy, and we are all (including me)
gathering information and experience about the use of his new
"typographical features menu" (for lack of a better expression!).

-- Finally, "pango" is part of the Gnome environment; it is not new by any
stretch of the imagination. Nor is aemenu, which has been around for 15
years. But the two together, used in this context: yes, this is new.

~~~~~~~~~~~~
Attached:

-- the script

-- the list of files in this package

-- the list of my GTK themes, with an evaluation of their usability related to
the aemenu-pango (the results of my test, in other words, of my "Get Gtk
Theme" support script)

-- a couple of screen caps, illustrating the three steps to take to make this
history menu as beautiful as can be.

BFN.
~~~~~~~~
P.S. Don't enjoy this version too much, BTW!

[bigpup]

musher0,

Too bad you did not start this topic.
All of the above information could be in the first post.
You would also be able to edit that first post at anytime you wanted to.

[musher0]

[MochiMoppel]

[musher0]

Self-censored.

[LazY Puppy]

The aemenu binary compiled in tahr64 605

[musher0]

Got it! Many thanks.

[LazY Puppy]

@MochiMoppel

The term "Menu Pipe" was taken from a forum member who had (I think it was stu90, a few years ago) invented a "Menu Pipe" for Openbox WM to have the installed wallpapers present at the openbox menu. That way (after stu90 invented walle, the wallpaper setter/changer) one could change the current wallpaper just by clicking its menu entry in that "Menu Pipe".

I'd used this for years when using LazY Puppy and Openbox.

Later I examined this script and created "Menu Pipes" for almost all of my external files, scripts, roxapps, wine portables and many more for the use in Openbox and much later also for the use in JWM. I found it a bit more comfortable that JWM is not updating those "Menu Pipes" each time when entering the menu (as the original for openbox does).

Did not like JWM very much from the first day I joined the forum. After doing those JWM menu pipes this has changed. Love it!

The times when musher0 came up (when I discovered this topic) with this here mruf I examined those scripts and found it useful to have also a "Menu Pipe" for recently used programs and directories (the pipe for recently used docs was already there).

I could provide the complete package which is around 30 scripts, though I doubt it would work out of the box in any else Puppy apart from a T.O.P.L.E.S.S. made Puppy Linux. Though you could at least examine the code.

I have placed these scripts in /root/my-applications/bin/jwm-menu-pipes

Oh, and recently-used-lst is some sort of a typo for recently-used.xbel. Sorry for that.

[musher0]

MRUF-lst-0.9.5.4-64 first test, on JustLightHouse64-604: basically works!

However the support executable called "bcm" also needs to be compiled for
64-bit. That's why we see funny characters instead of bullets, I think.

Attached: LP's compile of aemenu-pango64, zipped, & screen cap.

BFN

[Puppus Dogfellow]