The compiler turns PNGs into native SWF resources within the compiled
SWF, so the fact that the player cannot load PNGs is not relevant.
Shouldn't be an issue -- though you're right, there was a bug in this
area.
Also, and on a separate issue, perhaps it's time to dump SWF7 support.
Not sure there's any substantial utility to this any more.
- D.
On May 27, 2008, at 11:32 AM, André Bargull wrote:
swf7 can't display png-images natively, that feature was added in
swf8.
And there is still a png-display bug for swf7 caused by jgenerator
(reported a few times on the forum, e.g. this thread "http://forum.openlaszlo.org/showthread.php?t=9203
"). So, I don't think we can easily drop the swf-resources.
- André
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.
/>/
/
