By the way, if you puy .desktop files on the rox pinboard then their icons will follow the gtk theme.
I put in a feature request on the rox mailing list a long time back to allow specifying an icon in AppInfo.xml, when creating AppDir's. Currently the icon can only be set by placing an icon file inside and naming it .DirIcon. I'm pretty sure the project was already dying by that time though, and the request wasn't even acknowledged. The latest release is now pretty old in the tooth. Which is a crying shame.
Icepipes - my pipe menus collection for icewm
Hello, Nathan F.
Upon checking, I re-discovered that the icon path problem is a non problem in icewm. Icewm provides a distro-neutral way of specifying icon paths. You simply specify your icon path(s) in ~/.icewm/prefoverride. For example:
One should read the icewm manual before complaining about any distro's particular placement of its icons.
If you find fault with one distro, to be fair, you must complain about all of them. If you complain about Puppy's icon placement, you must also complain about Debian's way of throwing most menu items in the "Other" category, about the the fact that Scientific Linux Live provides no programs to speak of (only a browser), about the fact that Arch is not for the general public, about the fact that Fedora's atrocious LVM approach destroys anything non-Fedora on the disks without proper warning, and so on, and so forth.
A good critic maintains perspective. Otherwise, it's just ideology, or bone-picking, or revenge, or some such basic instinct.
No distro follows the ideal Linux model. Period. Don't throw BK and Puppy to the lions for some frivolous reason. If you do, you may some day end up between their teeth as well.
As to "enlightening" you, this: I work best when task-centered or community-centered. On the other hand, you use the 1st person singular a lot, and do not seem keen on maintaining a dialogue: you ask questions on this thread when you seem to already have your answers. IMO, there is no point anymore in contributing to this thread.
Regards.
musher0
Upon checking, I re-discovered that the icon path problem is a non problem in icewm. Icewm provides a distro-neutral way of specifying icon paths. You simply specify your icon path(s) in ~/.icewm/prefoverride. For example:
Code: Select all
#prefoverride
# Icon search path (colon separated)
IconPath="/usr/local/lib/X11/pixmaps:/usr/local/lib/X11/mini-icons:/usr/share/pixmaps:/usr/share/icons/hicolor/16x16/apps:/usr/share/icons/hicolor/48x48/apps"
(...)If you find fault with one distro, to be fair, you must complain about all of them. If you complain about Puppy's icon placement, you must also complain about Debian's way of throwing most menu items in the "Other" category, about the the fact that Scientific Linux Live provides no programs to speak of (only a browser), about the fact that Arch is not for the general public, about the fact that Fedora's atrocious LVM approach destroys anything non-Fedora on the disks without proper warning, and so on, and so forth.
A good critic maintains perspective. Otherwise, it's just ideology, or bone-picking, or revenge, or some such basic instinct.
No distro follows the ideal Linux model. Period. Don't throw BK and Puppy to the lions for some frivolous reason. If you do, you may some day end up between their teeth as well.
As to "enlightening" you, this: I work best when task-centered or community-centered. On the other hand, you use the 1st person singular a lot, and do not seem keen on maintaining a dialogue: you ask questions on this thread when you seem to already have your answers. IMO, there is no point anymore in contributing to this thread.
Regards.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
-
Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
You do realize that you basically just told me to rtfm?
Which I have, by the way. The issue is not icon paths, and not icewm, but icon naming IN PUPPY. When choosing names for icons to display I chose basic/generic icon names that are expected to be present - everywhere except in Puppy. I'm not willing to adjust my icon naming to what puppy uses as it would break the scripts on virtually every other distro or os. I am willing to help implement symlinks that would help make Puppy more compatible with other distros and programs, including mine, without breaking anything internal to Puppy. But if the main response is flaming, maybe it's better if I just stop now.
I'm also not trying to trash Puppy or Barry. I have an enormous amount of respect for both. But I also see issues here and there and don't feel a need to gloss over them or tout them as "features". Barry is a great guy and incredibly creative. He also loves reinventing the wheel. Sometimes this is great and his solutions are astoundingly simple, other times it creates unforeseen complications. If my telling it like I see it is a bad thing, maybe your doing the same towards me is too...
You seem very intent on seeing me as a bad guy, but have misunderstood quite a few things all along so far. Maybe I could communicate better. But the fact that your tone continues to be accusatory is not encouraging me here. To the best of my knowledge I haven't criticized you in this entire thread, until this post. On the other hand, you have several times now accused me of being self centered in various ways. I'm not going to continue after this post because it's just plain bad etiquette to air out personal grievance, but I'm not going to leave all your comments about my "bad behavior" and supposed self centered attitude up for all the world to see without saying something back. Not when all I was trying to do was post something I thought might be useful, and then do some revision in order to satisfy other's needs and wishlists.
For the record, what I said about syncing rox bookmarks with gtk bookmarks had nothing to do with wanting code to add rox bookmarks to a pipemenu. It was all about the fact that rox has it's own bookmark implementation which is separate and incompatible with gtk bookmarks, so your gtk bookmarks don't show up in rox and your rox bookmarks don't show up in -any- other gtk app. What I was expressing was that it would be nice to have a program to merge the two. You completely misunderstood what I wrote and posted some code that I then chose not to use, because I already had a solution to the problem you -thought- I was asking about in mind and it was, in my opinion, more elegant. So then you took offense and expressed it quite publicly. I could just as easily accuse you of being an egomaniac for getting your feathers all ruffled over that.
My last word (really) is this: you say you have nothing more to contribute to this thread. I say maybe you're right and if it's a choice between you continuing to cop an attitude or just going away, I'd rather you just went away. However, if you're able to get back to civility then SO AM I and I'd much prefer that option. I don't hold grudges.
That is all.
Which I have, by the way. The issue is not icon paths, and not icewm, but icon naming IN PUPPY. When choosing names for icons to display I chose basic/generic icon names that are expected to be present - everywhere except in Puppy. I'm not willing to adjust my icon naming to what puppy uses as it would break the scripts on virtually every other distro or os. I am willing to help implement symlinks that would help make Puppy more compatible with other distros and programs, including mine, without breaking anything internal to Puppy. But if the main response is flaming, maybe it's better if I just stop now.
I'm also not trying to trash Puppy or Barry. I have an enormous amount of respect for both. But I also see issues here and there and don't feel a need to gloss over them or tout them as "features". Barry is a great guy and incredibly creative. He also loves reinventing the wheel. Sometimes this is great and his solutions are astoundingly simple, other times it creates unforeseen complications. If my telling it like I see it is a bad thing, maybe your doing the same towards me is too...
You seem very intent on seeing me as a bad guy, but have misunderstood quite a few things all along so far. Maybe I could communicate better. But the fact that your tone continues to be accusatory is not encouraging me here. To the best of my knowledge I haven't criticized you in this entire thread, until this post. On the other hand, you have several times now accused me of being self centered in various ways. I'm not going to continue after this post because it's just plain bad etiquette to air out personal grievance, but I'm not going to leave all your comments about my "bad behavior" and supposed self centered attitude up for all the world to see without saying something back. Not when all I was trying to do was post something I thought might be useful, and then do some revision in order to satisfy other's needs and wishlists.
For the record, what I said about syncing rox bookmarks with gtk bookmarks had nothing to do with wanting code to add rox bookmarks to a pipemenu. It was all about the fact that rox has it's own bookmark implementation which is separate and incompatible with gtk bookmarks, so your gtk bookmarks don't show up in rox and your rox bookmarks don't show up in -any- other gtk app. What I was expressing was that it would be nice to have a program to merge the two. You completely misunderstood what I wrote and posted some code that I then chose not to use, because I already had a solution to the problem you -thought- I was asking about in mind and it was, in my opinion, more elegant. So then you took offense and expressed it quite publicly. I could just as easily accuse you of being an egomaniac for getting your feathers all ruffled over that.
My last word (really) is this: you say you have nothing more to contribute to this thread. I say maybe you're right and if it's a choice between you continuing to cop an attitude or just going away, I'd rather you just went away. However, if you're able to get back to civility then SO AM I and I'd much prefer that option. I don't hold grudges.
That is all.
Bring on the locusts ...
Hello.
Thanks for your frank reply.
With pekplaces.sh, you obviously have succeeded in 4,15 Kb where the 691 Kb pekwm_ls_menu has fallen short. (Please see https://projects.pekdon.net/projects/11). Your pekplaces script is as slow as molasses at this point (at least on this older computer) and the sub-directories listing certainly needs refinements (the menu cannot remain so clogged; proper sub-menus listings need to be implemented), but basically it works.
Thus, you are not the free-rider the wording of some of your messages led me to perceive you were. What threw me off if that you have not indicated whether you had consulted / reviewed any previous attempts at what you presenting.
Hopefully you already know that some of what you are presenting has been done or at least attempted, that people in or close to the pekwm community have suggested scripts with the same goals as yours. A single line comparing your take with theirs would have worked wonders in removing obstacles to communication, in my mind anyway.
From that context and perceived standpoint, maybe you can now understand why I did indeed tell you to read the fabulous manual.
I can only observe that our communication styles are quite different and end up being oppositional. For the time being, I have no wish of refining that analysis to discover whether that "angular" communication has generational, cultural, methodological or other roots.
Maybe our exchanges will be more fruitful at a later time. For now, I'll leave it at that and get out of your way.
Regards.
Thanks for your frank reply.
With pekplaces.sh, you obviously have succeeded in 4,15 Kb where the 691 Kb pekwm_ls_menu has fallen short. (Please see https://projects.pekdon.net/projects/11). Your pekplaces script is as slow as molasses at this point (at least on this older computer) and the sub-directories listing certainly needs refinements (the menu cannot remain so clogged; proper sub-menus listings need to be implemented), but basically it works.
Thus, you are not the free-rider the wording of some of your messages led me to perceive you were. What threw me off if that you have not indicated whether you had consulted / reviewed any previous attempts at what you presenting.
Hopefully you already know that some of what you are presenting has been done or at least attempted, that people in or close to the pekwm community have suggested scripts with the same goals as yours. A single line comparing your take with theirs would have worked wonders in removing obstacles to communication, in my mind anyway.
From that context and perceived standpoint, maybe you can now understand why I did indeed tell you to read the fabulous manual.
I can only observe that our communication styles are quite different and end up being oppositional. For the time being, I have no wish of refining that analysis to discover whether that "angular" communication has generational, cultural, methodological or other roots.
Maybe our exchanges will be more fruitful at a later time. For now, I'll leave it at that and get out of your way.
Regards.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
-
Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
Honest feedback there, that is appreciated. Maybe we're not friends yet, but it seems like progress. Thank you.
A couple small points relating to the technical details.
There's no way it's going to be fast implemented in the shell, particularly if you try to browse the entire filesystem. This is for those not wishing to install python|boost or whatever other odd libs and thus enter dependency and upgrade hell. You can also disable a couple features and make it behave more like the gnome2 places menu, which was more along the lines of the original intent. That in itself should make it feel snappier.
My other comment would be that yes, I am aware of a number of other implementations. In fact I use a directory browser in openbox created by Xyne that is quite a bit faster than mine and packs in a few more features to boot. The point, once again, was to try to do it completely in the shell.
A couple small points relating to the technical details.
There's no way it's going to be fast implemented in the shell, particularly if you try to browse the entire filesystem. This is for those not wishing to install python|boost or whatever other odd libs and thus enter dependency and upgrade hell. You can also disable a couple features and make it behave more like the gnome2 places menu, which was more along the lines of the original intent. That in itself should make it feel snappier.
My other comment would be that yes, I am aware of a number of other implementations. In fact I use a directory browser in openbox created by Xyne that is quite a bit faster than mine and packs in a few more features to boot. The point, once again, was to try to do it completely in the shell.
Bring on the locusts ...