Posted: Wed 21 Sep 2016, 08:56
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!
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!