Page 3 of 3

Posted: Sat 02 Feb 2013, 22:59
by disciple
technosaurus wrote:I messed around with the sources to remove xml file dependency (converted with glade-2.12), but localization needs fixed now - LC_ALL wasn't defined, so I changed it to "C" so it would build.

(btw it is smaller than the puppy default one which is upx'd in /usr/local/bin)
How much of that space have you saved by disabling localization though? ;)

Posted: Sat 02 Feb 2013, 23:04
by technosaurus
none AFAIK, I just changed the LC_ALL to "C" to get it to compile ... I'm sure I could get it back by watching a full build of the full glipper (though any localized glade files will need to be po'ed too, since those strings are now in source)

Posted: Sun 03 Feb 2013, 01:52
by disciple
This probably doesn't mean anything in real life, but it is interesting that your version ("glipper" in the attached screenshot) seems to initially use more resources, I guess maybe because you replaced the xml with code.
After opening the history menu or the preferences dialogue mine uses exactly the same :( and it doesn't drop down again after these are closed, either. I wonder if it would if I was running out of ram...
fixed ability to change keybinding
I guess that only needed fixing because it broke in refactoring or something... it has always worked for me :)

For the sake of the casual reader, other than the NLS, the only functional differences I can see between yours and mine are:
- your executable is standalone, so will still run without an xml file or an icon file.
- mine still works with older gtk versions e.g. in unmodified Puppy 4.x series
- mine doesn't load properly on my current up-to-date system when the system tray is provided by lxpanelx, which produces an `X Error: BadMatch (invalid parameter attributes)`. It runs fine with JWM.

Posted: Fri 08 Feb 2013, 10:48
by disciple
technosaurus wrote:p.s. aside from the global keybinding (which could be assigned by the wm), all of glipper could be emulated with a small gtkdialog + sit app that uses xclip (I'll add it to my todo list for my sit suite along with battery, temperature, memory, cpu, volume, network, cups, save file and others - so we can have just 1 tray app and 1 shell daemon running)
You might want to look at clipbored...

Posted: Sun 10 Feb 2013, 00:25
by disciple
For the record, compiling Technosaurus' version on my Arch system I needed to add this to the build script:

Code: Select all

-lgdk-x11-2.0 -lX11 -lgobject-2.0 -lglib-2.0
Naturally the -lX11 can break it on older systems :roll:
I guess this is why people use autotools...

Posted: Tue 19 Mar 2013, 09:03
by jamesbond
glipper-lite revision 284 will replace glipper in the next release of Fatdog. Thank you.

Posted: Tue 18 Nov 2014, 18:59
by Rope
Is there any new pet for Glipper-lite (Latest Glipper version is 2.4 and has plugins)

Posted: Tue 18 Nov 2014, 20:42
by disciple
Glipper is now written in Python, so no, there won't be a version corresponding to it.
Amigo did say he saw the plugin support was added before the switch to Python, but I didn't look at it because the plugins were still in Python I think. I guess I can have another look after my current project. But you may find the "action" support in Parcellite suits your purposes...

Posted: Sat 25 Jun 2016, 02:06
by scsijon
disciple, hi!

?do you have the lateat source code for this packages up somewhere, I'm trying to build on T2 system and it's failing badly with the version up there.
I thought maybe it's a version thing as i'm trying to build on x86-64.

thanks

Posted: Sat 25 Jun 2016, 03:35
by technosaurus
I know of at least this fork:
https://github.com/AlisterH/glipper-lit ... ipper-lite
Which uses the builtin gtkbuilder xml instead of glade xml (or my C code version)
I think that was from the latest google code repo source.

Posted: Sat 25 Jun 2016, 04:15
by disciple
That one's me, and you're right, I haven't done anything more since I put it up on google code.

Posted: Sun 26 Jun 2016, 03:22
by scsijon
OK thanks i'll have a go with that one before trying your patience further as it's technosaurus's one that is failing to build x86-64, but it's ok 32bit.

Posted: Mon 26 Aug 2019, 07:56
by 01micko
disciple wrote:That one's me, and you're right, I haven't done anything more since I put it up on google code.
Until yesterday

:)

It will be in the upcoming raspup buster which I'm working on as we read.

Posted: Sun 15 Sep 2019, 10:14
by disciple
Thanks for that micko. I'm surprised I only partially stripped help out of the gui - maybe I intended to reimplement it, but I think it is actually completely unnecessarily.