Re: Icon for gnucap?

Justin Fuhrer <[email protected]>
Newsgroups gmane.comp.gnu.gnucap.devel
Message-ID <[email protected]>
Peter Clifton wrote:
> On Sun, 2009-06-07 at 20:23 -0700, Justin Fuhrer wrote:
>> Justin Fuhrer wrote:
> 
>> Sorry, looks like the mailing list stripped my attachments.  See here 
>> instead:
>>
>> http://fb.xenostarz.com/index.php?fpp=10&did=3
> 
> If you wanted to include some anti-aliased elements, draw up the
> schematic portion of the symbol in a git HEAD gschem, (which features
> anti-aliased rendering), switch the grid off, and screen-capture at an
> appropriate size.

That's a good idea.  I avoided anti-aliasing altogether and redrew the 
wiring/components/graph by hand in pixel form for the 48x48 version.

> The symbology looks fine to me - although I guess implying that gnucap
> draws graphs is an aspiration to better plotting integration ;).
> 
> Doing icons for text based apps can be a challenge. Some kind of
> abstract logo (rather than program icon) would have also been another
> option - which avoids the need to design so it can be simplified to a
> scaled version (down to about 21x21px). I guess it just depends if
> anyone thinks gnucap ought to have a launcher in a GUI desktop's menu,
> or whether it only makes sense to run from a command line.

Thanks for this input, Peter, you're exactly right.  It's hard to 
reasonably represent a console-only data/analysis tool.  First try, 
anyway. :P

> The only concept I managed to come up with for gnucap would have been a
> circuit fragment, with a component (or perhaps the whole fragment
> graphic), hooked up to a graphic element looking like an ECG /
> oscilloscope / chart of some kind.

This isn't a bad idea, a circuit hooked up to a measurement machine. 
Works better than schematic + graph, in my mind.  I'll be back...

Thanks,

Justin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.