 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
scott <sco### [at] scott com> wrote:
> > I was wondering how much I could reduce the file size of your PNG if
> > lossiness is allowed, but without degrading the image quality noticeably.
> > I was able to reduce your original 138408 bytes png to a 49074 bytes one:
> The AA on the diagonal lines certainly looks noticeably worse...
I don't think it reduces the readability and clarity of the graph in
any way.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
You know, the longer I stare at this diagram, the more features and
concepts I realise I've left out. It's true: when you know a subject
well, it really becomes very difficult to avoid overlooking things that
have become completely "obvious" to you...
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> And now, colour-coded by priority...
If I run it through optipng and pngout, it gets reduced from 66135 bytes
to 61569 bytes losslessly.
If I reduce it to 64 colors first, it gets reduced to 50843 bytes without
noticeable loss.
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible <voi### [at] dev null> wrote:
> You know, the longer I stare at this diagram, the more features and
> concepts I realise I've left out. It's true: when you know a subject
> well, it really becomes very difficult to avoid overlooking things that
> have become completely "obvious" to you...
And then they say C++ is complicated...
--
- Warp
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp wrote:
> And then they say C++ is complicated...
Perhaps you could try drawing up a similar diagram for C++? I'm sure
that between integer type modifiers, pointers & references, const &
volatile, the new operator, implicit conversions, default
constructors/descructors, templates, the preprocessor, function
overriding, and everything else C++ has to offer, it'll come out
similarly tangled. ;-)
The difference, I think, is that in C++ you don't need to know so many
things to start writing useful code, whereas in Haskell, since
everything is related to almost everything else, you need to actually
know quite a lot of stuff all at once before you can "get going".
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Warp escreveu:
> Invisible <voi### [at] dev null> wrote:
>> Warp wrote:
>>> I was wondering how much I could reduce the file size of your PNG if
>>> lossiness is allowed, but without degrading the image quality noticeably.
>>> I was able to reduce your original 138408 bytes png to a 49074 bytes one:
>
>> Impressive. How did you manage that?
>
> Reduced to 8 colors (without dithering) and then ran through optipng and
> pngout.
>
5+ GeekPoints
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible escreveu:
> I just sat down and attempted to draw a chart representing all the most
> important topic of the Haskell programming language, and how they relate
> to each other.
>
> Unfortunately, it looks like this:
>
> ------------------------------------------------------------------------
>
I'm sure I spotted a WTF somewhere...
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
"Warp" <war### [at] tag povray org> wrote in message
news:48f892ff@news.povray.org...
> I was wondering how much I could reduce the file size of your PNG if
> lossiness is allowed, but without degrading the image quality noticeably.
> I was able to reduce your original 138408 bytes png to a 49074 bytes one:
>
>
28461 bytes, who does better :p
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
Attachments:
Download 'Haskell1-2.png' (28 KB)
Preview of image 'Haskell1-2.png'

|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
"Zeger Knaepen" <zeg### [at] povplace com> wrote in message
news:48f8f356@news.povray.org...
> "Warp" <war### [at] tag povray org> wrote in message
> news:48f892ff@news.povray.org...
>> I was wondering how much I could reduce the file size of your PNG if
>> lossiness is allowed, but without degrading the image quality noticeably.
>> I was able to reduce your original 138408 bytes png to a 49074 bytes one:
>>
>>
>
> 28461 bytes, who does better :p
on second thought, readability isn't as good anymore :)
cu!
--
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x) // ZK http://www.povplace.com
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
Invisible wrote:
> Warp wrote:
>> I was wondering how much I could reduce the file size of your PNG if
>> lossiness is allowed, but without degrading the image quality noticeably.
>> I was able to reduce your original 138408 bytes png to a 49074 bytes one:
>
> Impressive. How did you manage that?
Could get smaller size and of higher resolution.
(compressed SVG :P)
Post a reply to this message
|
 |
|  |
|  |
|
 |
|
 |
|  |