Puppy Linux Discussion Forum

[01micko]

Hello vovchik,

So far it all works nice except that if I try to use lock as a parameter I get the clock! Curiously, I tried "ock".. got a clock!

Thanks for your work, oh, if it makes a difference I'm using fatdog with 32 bit compat and your binary (no bacon in fatdog as yet).

[vovchik]

Thanks 01micko!

There was a little bug in my FIND routine. It has now been fixed. It really pays to have people test. Thanks again.

With kind regards,
vovchik

[technosaurus]

I wouldn't say the bacon version is inherently faster or smaller considering that it will likely be called from a script and ops can be done using only builtins (typically faster than sourcing and executing an external program)... Then considering that it will be on a compressed squashfs, the script will get compressed without the additional overhead. It's still good to have alternative though, for native bacon apps. A C only version is pretty easy to do, as it would basically only need strcmp and (f)printf. The things that I left stubbed out that would really improve the look, need some input from graphically oriented designers. Backgrounds that can help tie them together with a unified look and feel that also complement foregrounds that can be informative while being graphically appealing and unified. If I had written it in C I was afraid I would lose input due to inaccessibility.

[vovchik]

Dear technosaurus,

The BaCon is certainly faster at coming up with the icon and color lists at the moment, but those bits could be optimized in bash. What I am interested in most is collecting more of these simple icons for inclusion and including a few more arguments (scaling and gradients come to mind), as well as text generation (with a few effects). It would really be possible to code a little SVG Factory. And it might just be useful to implement object overlays/compositing. Just food for thought

With kind regards,
vovchik

[technosaurus]

I made a quick mod of the code to incorporate the ICON= into a case statement which both speeds it up and reduces memory usage. Also added color support based solely on positional parameters $2, $3... I need to find one of my old examples to incorporate text. For colors, I assume svg can use anything in rgb.txt.. or hex values of course. The backgrounds I am thinking could be an exported VAR so they can unify across the platform. I saw that vovchick had upscaled the image, I guess I should add a parameter to allow that to be adjustable (gtk doesn't do a great job scaling)

[technosaurus]

Forgot to upload.

decided it would be better to use stdout for the icon, that way it can be sent anywhere - got everything but the background complete (unless you export the applicable environment variables to valid SVG code)... todo
but execution time is still <0.05s

Edit: no time to sort through these, but it may have links to some usable icons:
http://wiki.inkscape.org/wiki/index.php/Galleries

[seaside]

Is this going viral?

How about a GUI to try out the icons in the notiification area - but then I guess we'd have to call it SIN (get's more attention
that way )

[vovchik]

Dear seaside,

I like the gui very much. Thanks. I see that you use bsvg, so I just made a new version that outputs to stdout if you use "-" as the last argument after the color args (run without parameters and bsvg will show you how). No need to copy to and from /tmp now, just redirect. Also, I have simplified your parsing by adding "-C" and "-I" parameters. They output unformatted lists (1 item per line). The archive contains a new UPX'd binary and the revised source.

It is going viral indeed, and nicely!

With kind regards,
vovchik

[seaside]

Technosaurus and Vovchik - thanks for those simplifications and additions. Much better.

It seems to me at this point that the icon draw files should be separate from the icon creation mechanism. If more icons are brought in or existing ones changed, considerable extra work is involved with updating.

A simple "grep firefox raphaeljs.txt (holding the draw files)" seems reasonably quick and perhaps might be considered as a way to have any number of "draw" files at the ready.

Best regards,
s

[seaside]

Here's a version that seems reasonably responsive. (I'm sure technosaurus would make it absolutely fly )Placing the svg draw in a separate file (svgs).

[01micko]

Viral [ ]

I guess we could almost make a script to generate rox desktop icon themes in any colour combination. Just need a few more icons.

yeah, nothing to do with sit, new thread?

I have found some [possibly] suitable icons, lots of them have spaces/new lines in the string starting with "M", any work around?

http://somerandomdude.com/work/iconic/

[technosaurus]

I was thinking about the "what should puppy look like?" thread when I came across these.
http://murga-linux.com/puppy/viewtopic.php?t=78080
I wanted a way to make the desktop look like the menu, look like the apps, look like the tray. We'd still need to generate pngs for jwm - anyone want to patch jwm to just use imlib2?

[vovchik]

Dear all,

I have revised bsvg again and added heaps of new svgs (now 410). I have also included a script that dumps all the icons in the library to your current directory as svg files - and you can specify colors. Incorporated in this version is a set by P.J. Onori (http://somerandomdude.com/work/iconic/), but I first had to modify all his polygons and other shape macros to full svg paths and to standardize all views to 128x128. His icons start with "I_". A real pain, that transformation exercise, but at least all the icons are now one size. I also added a few of my own (icon names starting with V_).

Have fun...

With kind regards,
vovchik

PS. Thanks technosaurus. That was a very nice find:)

PPS. The archive contains the source, a 32-bit UPX'd binary compiled on Lucid and the dump script. I would place the binary and dump script in /usr/local/bin.

PPPS. @ technosaurus, seaside and 01micko. You can now parse my source to grab the icon definitions for use in bash or another language. The new ones (named I_ and V_) need a new svg "<g transform=>" line, which is the last field in each line.[/url]

[seaside]

[vovchik]

Dear seaside,

Thanks. Conversion is a royal pain in the arse. You have to ungroup the image in Inkscape (several times) and then use Item->Convert to paths for every object. I suppose this could be done algorithmically, but I did it the ugly manual way, with some preliminary programmed parsing to throw out prolix metadata and other unnecessary garbage. Nominal scaling is also another pain, but it is important to have one viewport for all icons of the same dimensions, particularly if you later want to convert to png or something else. It will save work later on. With the transform statement I have included, and the path data, you should now be able to use the data in bash or something else to make your own generator or gui.

With kind regards,
vovchik