Just drag the files onto the app and it does its best.
Mats
8 jan 2007 kl. 22.05 skrev Mike Filippone:
This doesn't seem to have any effect on the memory leak, but I
noticed your images folder is quite large when I was looking around
the bundle. I'm not sure if anyone has talked about this before,
so sorry if I'm being repetitive, but it was pretty useful when I
found out about it.
At least from what I gather, most image programs don't seem to get
the maximum compression out of png's that is possible, and
Photoshop (which I'm guessing you used) seems to be one of the
worst offenders. So I use a terminal utility called PNGCrush that
really helps out with compressing pngs both for my widgets and my
website. I posted some info about it on my site back in the day as
well: http://www.donkeyentertainment.com/software/news.php?post=2
I tried compressing your image folder using that utility, and it
went from 2.9 MB to 272 KB. Normally you don't get that kind of
reduction in file size... I'm guessing it's mostly because
Photoshop is really bad at compressing png's. The zipped size also
went from like 690KB to 160KB.
And since it took me a really long time to figure out how to get
PNGCrush installed because I'm stupid with anything that doesn't
have a GUI, here's an overview that may make it easier:
The easiest way I've found is to install PNGCrush using
DarwinPorts. First install DarwinPorts (http://darwinports.com/) if
you don't already have it. After that, go into terminal, and type:
sudo port install pngcrush
You'll be prompted for your password, and after that, it will
install. You also need to be connected to the internet for it to
work. Once that happens, navigate to the folder with your png's in
terminal and type:
pngcrush -rem gAMA -rem cHRM -rem iCCP -rem sRGB -d exp *.png
That will go through all the png's, get rid of a bunch of stupid
metadata, compress them, and put the results in a folder named
exp. The utility has a bunch more options, and I think there's
documentation on their Sourceforge site, but that seems to work
well for me, and it removes problems with the color being different
across multiple computers. There's also a drag and drop app called
PNGCrusher (http://www.macupdate.com/info.php/id/17768)... (drop
the png's onto the application icon to use it), but as far as I
know it just compresses and doesn't remove the gamma metadata, so
you still run into the color problems.
I found that saving images as .psd's, opening them in Preview and
saving them as .png's there, and then running the PNGCrush commands
seems to result in the best color, or at least the color is exactly
the same as it looks in the document you're editing. Photoshop
kept making my images lighter, and it was really annoying. I never
tried running the PNGCrush command on the Photoshop-exported png's
though, which would have removed the gAMA tag, and may have
resolved it. I'm also running my Apple display at a gamma of 2.1,
instead of the native 1.8, which could have been the problem (or at
least let me notice the problem).
As I watch the Activity monitor the memory usage went from 200mb to
575mb and counting (real memory)...
There is an additional version which I can email individually upon
request, I don't want to put the link up because its not ready for
release, and all of the mailing list threads are archived online
where
google can find it.
wow memory requirements are still rising.
Thanks
-js
On 1/8/07, Nelson Darkwah Oppong <email@hidden> wrote:
Maybe you can upload some code, or even better the whole widget,
so I
(we) can take a look at it and test it on our machines?!
Nelson
> Technically all the functions of my widget are user-initiated,
so when
> hidden my widget shouldn't be doing anything, that I am aware
of, but
> if I open the activity monitor the memory usage kept going up
and up.
> I also noticed a slow down when I had the widget open.
>
> At this point right now my widget is using 418.45 MB of Real
Memory
> and 884.88 MB of virtual memory.
>
> On 1/8/07, Nelson Darkwah Oppong <email@hidden>
wrote:
>>
>> > Previously there was a discussion on Widget memory usage, I was
>> > curious if that ever got resolved.
>> >
>> > I noticed that my widget's memory usage has been increasing
>> > exponentially even when the Dashboard is in the background.
>> >
>> > When the Dashboard is in the background is it technically idle?
>>
>> I am not a pro, but I think, it isn't idle, because there are the
>> onhide and onshow functions, some months ago I read that the
deloper
>> should use them to decrease the update time when the widget is
>> hidden. I think my FTP widget works when hidden, too.
>>
>> Nelson
>>
>>
>>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Dashboard-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/dashboard-dev/filipm2%
40rpi.edu
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Dashboard-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/dashboard-dev/p02mm%
40efd.lth.se
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Dashboard-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/dashboard-dev/email@hidden
This email sent to email@hidden
