The PNGs that have been autogenerated are good, both in terms of
appearance and in terms of file size. I don't think we need to add a
manual task here; a script to clean things up would be great.
Next step for a designer would be to create a new skin for the
components as a whole. But that's a non-trivial task.
- D.
On May 27, 2008, at 10:48 AM, P T Withington wrote:
This seems like a fine idea to me, but shouldn't we actually get
some designer resources to create optimal .png's, rather than rely
on the auto-generated ones?
And then we just need to prioritize this w.r.t. everything else that
is going on...
On 2008-05-23, at 15:33 EDT, David Temkin wrote:
Is it time to remove the SWF resources altogether from the
components and the non-SWF specific sample apps, and move the
contents of the autoPng directories up a level?
The SWFs add confusion both to the source code ("I see SWF
resources -- how could that work in DHTML?") and in the way the
directories are laid out. And the autoPng mechanism is magic.
I don't think there's a benefit in keeping the SWFs around. While
SWFs in some cases may be smaller and/or may stretch better, the
confusion and difference between runtimes outweigh the benefits.
Thoughts?
- D.
