Suggestion for drive icon "mounted" indicator placement

[Sit Heel Speak]

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]

make it configurable, then everyone should be happy

[stu90]

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]

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.

Yes. The suggestion is meant for icon-designers, and for any Puppy or Puplet creator who is deciding what default icon-set to include in his/her release.

[technosaurus]

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]

put me on ritalin and draw me a picture

a t rex on ritalin...good heavens, lock up your stegosauruses!

Openbox is the default window manager in Quirky. I happen to like it in Luci and Lighthouse as well. (...however, when eventually I produce my own Puplet for public consumption, it will probably carry Fluxbox, for the sake of simplicity).

(scroll both screencaps linked below, to the bottom)

Wrong style of drive icon mounted indicator: Quirky (a Sept. 5 local woofbuild) with its default icon set:
http://i52.tinypic.com/favccy.png

Right: Luci-237 using Openbox:
http://i56.tinypic.com/k2k2d.png

Note the gain of 27 pixels at the bottom margin, as shown in the "bottom" field in Openbox Configuration Manager, resulting in that much bigger of a maximized Opera window, and yet still able to see which partition(s) is/are mounted.

[technosaurus]

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]

Hey techno! I LIKE that idea . I think it would look really nice and fixes this issue no matter what WM you use.

[Flash]

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

[technosaurus]

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

[Sit Heel Speak]

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

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]

sheer idio--er, I mean "mom-friendliness"

Hey, it's fine to imply that idiots are incompetent, but insinuating such about Moms-in-general is uncool. Please help make the world a safe and welcoming place for nerd-grrrls.

[Sit Heel Speak]

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]

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,h,o,cmd} files?
The entirety of /lib/modules/fglrx/build_mod/?
What else?

if you look in the new2dir script it should be fairly clear, but .o files are only an intermediate step 99.9% of the time (they either end up linked into a static or shared library or a binary ) make install _shouldn't_ actually install them ... same for .c files (you can pretty much ignore all the files in your source tree that get picked up too)

For the kernel modules, I'm not sure. I bought my hardware planning to run linux on it, so I've never needed to build extra modules ... look inside a similar existing pet (note the kernel version number in lib modules though)

[amigo]

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.

[Sit Heel Speak]

sheer idio--er, I mean "mom-friendliness"

Hey, it's fine to imply that idiots are incompetent, but insinuating such about Moms-in-general is uncool. Please help make the world a safe and welcoming place for nerd-grrrls.

...but...but...doesn't everyone like Berkeley Breathed cartoons???
http://www.berkeleybreathed.com/pages/F ... .asp?ID=11