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.
