Page 5 of 15
Re: forked fast momanager
Posted: Sat 08 Jun 2013, 12:19
by Bert
L18L wrote:
What else is required for next release?
- basename. not PATH
- I liked the proposal by don570: some kind of warning when a .pot file from /usr/share/doc/nls will be used by Momanager. Checking the pot creation date is not so straightforward for poedit users as it is for Geany users.
I don't know if your new "up-to-date?"code (the idea by rodin.s) covers this or if/how it deals with pot files taken from /usr/share/doc/nls.
Off-topic: I saw the German floods images. Brrr.
Hope your house and area are safe!
Posted: Sat 08 Jun 2013, 12:42
by vicmz
Fast and Furious Marilyn Monroe running fine here. Thank you for your hard work, L18L.
forked fast momanager
Posted: Sat 08 Jun 2013, 13:56
by L18L
Poor Victor, more and more stuff for
MM for dummies
Bert, we live high up in the mountains here
Bert wrote:- I liked the proposal by don570: some kind of warning when a .pot file from /usr/share/doc/nls will be used by Momanager. Checking the pot creation date is not so straightforward for poedit users as it is for Geany users.
I don't know if your new "up-to-date?"code (the idea by rodin.s) covers this or if/how it deals with pot files taken from /usr/share/doc/nls.!
Date of mo file is compared with date of script resulting in _ or +. That's all.
Now trying to find a pot file
41 pot files !
1 example: peasyscan.po
"POT-Creation-Date: 2013-02-26 19:09+0800\n"
"PO-Revision-Date: 2013-02-26 19:59+0100\n"
I will delete the pot file and its directory and there is no problem anymore
Code: Select all
rm -r /usr/share/doc/nls/peasyscan
Storing pot files is from
pre_MM-ages
Invented by shinobar IIRC.
But now only necessary
if momanager cannot produce an actual pot file. The only known case is alsaconf.....
The same is valid for
po files:
Code: Select all
# ls /usr/share/doc/nls/*/*.po
/usr/share/doc/nls/get_libreoffice/de.po /usr/share/doc/nls/obconf/de.po
/usr/share/doc/nls/grub4dosconfig/de.po
#
oops again
get_libreoffice/ deleted
obconf is binary
grub4dosconfig/ deleted
Thank you, langpack_de is going to become a bit less bloated.
Bert wrote: - basename. not PATH
All right. I was also having some trouble to find a script.....
Posted: Sat 08 Jun 2013, 19:25
by Bert
vicmz wrote: Thank you for your hard work, L18L.
+1
L18L wrote:Poor Victor, more and more stuff for MM for dummies
Yeah, but cover ready for printing press:
FFMM
Posted: Sun 09 Jun 2013, 07:39
by L18L
forked fast momanager
Posted: Sun 09 Jun 2013, 11:48
by L18L
New:
Scripts displayed as base name → path
→ is configurable
Making
find of any Script in drop down lists easy now
edit
momanager-20130609.pet deleted
please use recent pet at
http://www.murga-linux.com/puppy/viewto ... &start=137
Posted: Sun 09 Jun 2013, 13:02
by Bert
A mi gusto!
Nice to see the left column full of smilies...
This improvement is even better than I had imagined. Really very nice!
The only place where it gets a bit more difficult is with the many "func_" entries (Pburn, Pmusic)
But the ease of the rest of the sorting more than makes up for this.
Thank You!
FFMM
Posted: Mon 10 Jun 2013, 14:04
by L18L
New:
Sort of Binary executables same as Scripts
Highlight search term in search result
2 more configuration variables,
SHOW_SEARCH_RESULT and
HIGH_BG which is a background colour.
Code: Select all
### edit between = and #
showINTRO=no # anything other than yes will skip the intro
transLANG=de # de_DE or de
myEMAIL=fido@localhost # used when create a mo file
ISIN=☺ # 1 printable character to indivate mo file newer than script: ☺ or _
NOTIN=↻ # other 1 printable character to indicate mo file older than script: ↻ or X
SEPARATOR=⇔ # or → or : different from ISIN and NOTIN
SHOW_SEARCH_RESULT=1 # =0 in Xdialog without highlight or =1 highlighted in defaulthtmlviewer
HIGH_BG='lightyellow' # background colour for search term in search result
# or choose colour with Gcolor2 (Menu > Graphics)
HIGH_BG='rgb(255,255,204)' # background colour for search term in search result
Have fun
edit
No wait some moments:
I am going to make it easier, without html using builtin --colour of grep
FFMM
Posted: Mon 10 Jun 2013, 17:30
by L18L
L18L wrote:... I am going to make it easier, without html using builtin --colour of grep
Proudly presenting FFMM 130610
Binary executables in same sort order like Scripts
Search result highlighted in console
Search configurable context lines and geometry of result
Fun
edit
momanager-20130610.pet deleted
please use recent pet at
http://www.murga-linux.com/puppy/viewto ... &start=137
Posted: Mon 10 Jun 2013, 20:27
by Bert
Let me be the first one to admit I'm not clever enough for this L18L guy
He proudly presents FFMM 130610:
Binary executables in same sort order like Scripts
Search result highlighted in console
Search configurable context lines and geometry of result
The first two I understand, but I cannot digest the third one without a (polite) burb
If I'm allowed some humour, I think his coding
voodoo is now also infecting his human-readable-output
I've been staring at this screenshot, wondering how it was done:
,
because here it looks like this, also in the latest FFMM:
Apologies if I missed the obvious.
Preferences-questions:
"ISIN" would be understandable if named "ISUP2D8"?
(same for "NOTIN": NOTUP2D8"?)
SEPARATOR: Will it change from '<=>' to '->' at some point and why? And how to interpret 'different from ISIN and NOTIN' ?
Written with the greatest respect L18L !
And again, thanks for your work!
FFMM20130610
Posted: Tue 11 Jun 2013, 09:20
by L18L
Bert wrote: Search configurable context lines and geometry of result
The first two I understand, but I cannot digest the third one without a (polite) burb
If I'm allowed some humour, I think his coding
voodoo is now also infecting his human-readable-output
Search: the "new" way to find anything inside mo files
configurable context lines: number of lines before found search term and number of lines before found search term
configurable geometry of result: geometry of a rectanlgle is WiDTH and HEIGHT
Bert wrote: I've been staring at this screenshot, wondering how it was done
,
because here it looks like this, also in the latest FFMM:
Apologies if I missed the obvious.
I am not sure if I understand your question.
It was done using with mtPaint-snapshot. I do not see any relevant difference in the two images.
Bert wrote:Preferences-questions:
"ISIN" would be understandable if named "ISUP2D8"?
(same for "NOTIN": NOTUP2D8"?)
But a smiley and the symbol for refresh are understandable?
I could change the configuration file saying something like
If you do not understand anything then do not touch.
Bert wrote:SEPARATOR: Will it change from '<=>' to '->' at some point and why? And how to interpret 'different from ISIN and NOTIN' ?
SEPARATOR is
one character and separates "base name" from "path/base name".
Change it for example to ☺ (which is NOT different from ISIN) and momanager could not work as before.
Thinking about next version now
which will have
no choices of changing SEPARATOR ISIN and NOTIN
Answered with the greatest respect!
And again, thanks for your feed back
momanager
Posted: Tue 11 Jun 2013, 11:58
by L18L
simplified configuration now, thanks Bert
have fun
edit
momanager-20130611.pet deleted
please use recent pet at
http://www.murga-linux.com/puppy/viewto ... &start=137
Posted: Tue 11 Jun 2013, 12:35
by AbdelAziz
Hi L18L
Using latest version, in SSS domain, i select desk_string.ar
when i click Edit the Momanager windows hide then show and nothing else happens!
momanager
Posted: Tue 11 Jun 2013, 13:59
by L18L
AbdelAziz wrote:Using latest version, in SSS domain, i select desk_string.ar
when i click Edit the Momanager windows hide then show and nothing else happens!
Thanks for reporting this.
Repairing this might take some time for me.
But if you like you now can simply use yudit
and edit your file
/usr/share/sss/desk_strings/desk_strings.ar
example:
change
s%"paint"%%
to
s%"paint"%طلاء%
Then you can test this translation in console before you have a langpack:
Code: Select all
fixdesk
rox -p /root/Choices/ROX-Filer/PuppyPin
... and you shouls see طلاء below your desktop icon for
paint.
[edit] found the (my) fault:
change in /usr/sbin/momanager line ~ 1473 from
Code: Select all
[ "$SSSFILES" ] || LANG=$ORIGLANG exec momanager restart # 130604 --empty--
to
Code: Select all
[ "$SSSFILE" ] || LANG=$ORIGLANG exec momanager restart # 130604 --empty--
... and the editor should open that file.
.. and momanager will continue after editor is closed.
Posted: Tue 11 Jun 2013, 15:47
by AbdelAziz
[edit] found the (my) fault:
change in /usr//sbin/momanager line ~ 1473 from
Now it work fine
By the way don't you think version number should be somewhere in momanager gui ?
Re: FFMM20130610
Posted: Tue 11 Jun 2013, 15:57
by Bert
L18L wrote:
Bert wrote: I've been staring at this screenshot, wondering how it was done
,
because here it looks like this, also in the latest FFMM:
Apologies if I missed the obvious.
I am not sure if I understand your question.
It was done using with mtPaint-snapshot. I do not see any relevant difference in the two images.
Thanks for your reply.
Concerning the above: I saw an interesting difference, that made me think you found a way to sort alphabetically, while having the 'mother program' to the left. So 'ADF' is sorted, but 'peasyscan' is shown first. I wondered how you achieved that and why I didn't see the same.
Running FFMM20130611 now: yes the many smilies were nice, but the three dots are indeed much better for contrast.
And yes, even I understand the preferences now
Re: FFMM20130610
Posted: Tue 11 Jun 2013, 16:49
by L18L
Bert wrote:... Concerning the above: I saw an interesting difference, that made me think you found a way to sort alphabetically, while having the 'mother program' to the left. So 'ADF' is sorted, but 'peasyscan' is shown first. I wondered how you achieved that and why I didn't see the same...
The only differences see :
1- nl vs. de
2- different font sizes so that I see in my "de window" a bit more than you can see in your "nl window".
'peasyscan' is shown first
No that is an optical illusion
But the entire data is:
______________…ADF→/usr/local/peasyscan/ADF (de peasyscan.mo peasyscan)
…ADF→/usr/local/peasyscan/ADF (nl peasyscan.mo peasyscan)
=============================
edit
I missed the obvious:
-3 The width of the combo fields are different
But that is something to solve for gtk gurus
momanager
Posted: Tue 11 Jun 2013, 17:29
by L18L
AbdelAziz wrote:By the way don't you think version number should be somewhere in momanager gui ?
Good question.
Momanager was, is and will stay Barry's baby.
He does not use versions and thus I did not.
Look into the script
to see latest change.
Actually latest change in
my script is:
#130612 L18L fix for desk_strings not showing up in editor reported by AbdelAziz
Maybe I will show date of last change in the GUI next pet .
Re: FFMM20130610
Posted: Tue 11 Jun 2013, 19:26
by Bert
L18L wrote:
The only differences see :
1- nl vs. de
2- different font sizes so that I see in my "de window" a bit more than you can see in your "nl window".
'peasyscan' is shown first
No that is an optical illusion
But the entire data is:
______________…ADF→/usr/local/peasyscan/ADF (de peasyscan.mo peasyscan)
…ADF→/usr/local/peasyscan/ADF (nl peasyscan.mo peasyscan)
=============================
edit
I missed the obvious:
-3 The width of the combo fields are different
But that is something to solve for gtk gurus
Hi L18L,
I discovered it's only a matter of global font size:
I changed it from 96 to 78 and got the same combo field width as in your .de version:
(because of eye problems I prefer the 96 size..)
Solved
Re: FFMM20130610
Posted: Wed 12 Jun 2013, 18:00
by L18L
Bert wrote:(because of eye problems I prefer the 96 size..)
Me too
Next "version"
designed for small screens
smaller height by 2 lines header and less frames
smaller width by moving some text to tooltips
tooltops added for
- search
- Preferences
- editor
- about ("version")
will upload tomorrow
