Puppy Linux Discussion Forum

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Suggestion: it would bless us Openbox users slightly, if the "mounted" indicator were at the bottom of each drive icon, rather than the top. Then, in Openbox Obconfig, Margins, we would have another 10 to 15 pixels of height for our fully-maximized apps, and still be able to see at-a-glance whether a partition is mounted or not.

darkcity · Joined: 23 May 2010 Posts: 2215 Location: near here

make it configurable, then everyone should be happy

stu90 · Posted: Wed 17 Nov 2010, 12:14 Post subject:

Do you mean the drive icons that are on the desktop? If so the drive icons are located in usr/local/lib/x11/themes you can just swap them out with what ever icons you like.

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

technosaurus · Joined: 18 May 2008 Posts: 3843

just to try to clarify??? not sure what the underlying issue is

1 - it has to do with the mounted icon itself depending on placement
2 - it is only if you are using (non-standard) openbox
3 - is there a screenshot showing the problem / proposed solution?
4 - you propose that the source code is hacked to be able to place the icon text above icons instead of below (the defacto standard across every desktop environment I've ever seen)
5 - None of the above ... I guess you'll have to put me on ritalin and draw me a picture - I'm confused.

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

technosaurus · Joined: 18 May 2008 Posts: 3843

they are just the regular drive icons with /usr/share/mini-icons/mini-{red,green}ball pasted on
...you are saying that you want your balls to hang low

maybe better than that would be to have unmounted drives faded out and mounted icons bright and crisp - then it would be apparent for any position

plankenstein · Joined: 15 Nov 2008 Posts: 118 Location: Arkansas, USA

Hey techno! I LIKE that Idea

idea

. I think it would look really nice and fixes this issue no matter what WM you use. Very Happy

Flash · Posted: Wed 17 Nov 2010, 20:19 Post subject:

Or change color from restful blue to throbbing hot pink! (Just kidding. Laughing

)

technosaurus · Joined: 18 May 2008 Posts: 3843

here is what simply applying a grey-scale filter looks - it takes like 10 seconds in mtpaint

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Greyscaling them might not work in the case where they're already transparent or translucent, i.e. ghostly, such as in Luci Laughing

Remember to distinguish the home partition from other mounted partitions.

Hey, t, while you're here...

I have just used my Clipper script to build an automated buildscript for Catalyst (fglrx) .pet's.

Before I unleash several Catalyst .pets on the world, I need a 5-second evolutionary lesson on what the buildscript should split off into the DEV .pet.

The .c files?
The .h files?
The .o files?
The .cmd files?
The entirety of /lib/modules/fglrx/build_mod/?
What else?

jemimah · Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL

Sit Heel Speak · Joined: 30 Mar 2006 Posts: 2595 Location: downwind

Astonishing...if you google "Traditions cigarettes" you would get no clue that the Squaxin Tribe is manufacturing them...but they do...here is a scan of the front and back of the pack...
http://i51.tinypic.com/2q15ldu.png

technosaurus · Joined: 18 May 2008 Posts: 3843

amigo · Joined: 02 Apr 2007 Posts: 1759

SHS, generally, the devel files are composed of:
1. header files usually: *.h, but sometimes *.hh or other for C++ stuff
2. static libraries: *.a files
3. libtool files which go with above static libs: *.la files
4. pkg-config files: *.pc
5. sometimes aclocal files or directory

It might be helpful to examine a few typical binary deb or rpm packages alongside their *-devel counterparts to see how they are split.