Thank you, Charles.<br><br>Bryan, to your original point:<br>> There are a lot of great education activities done in Flash and <br>> their # will only increase simply because it is very easy to <br>> develop animations using flash. Check out <br>
> <a href="http://www.eshikshaindia.in/" target="_blank">www.eshikshaindia.in</a> for more great learning<br>> animations. Those did not work w/ Gnash when I tried it last month.<br><br>We /do/ want people making great education activities to make them compatible with open source Flash players, now that Gnash is becoming a viable instance of one. You don't have time to convert them youreslf, but the people who made them do, if they are maintaining their work.<br>
<br>We also want to make customization of machines in a local deployment easier. I am not sure that your suggestion of adding a symlink to all builds that points to a subdirectory of /home/olpc for mozilla plugins is the way to go, but if you have specific requests of that nature you should file a ticket with the request. That seems to have been lost in the email exchange.<br>
<br>SJ<br><br><div class="gmail_quote">On Tue, Mar 25, 2008 at 1:38 AM, Charles Merriam <<a href="mailto:charles.merriam@gmail.com">charles.merriam@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br>
<br>
I think I added all the substance from this thread into the wiki<br>
(<a href="http://wiki.laptop.org/go/Gnash" target="_blank">http://wiki.laptop.org/go/Gnash</a>). It's late, so I would apprecate<br>
Rob et al doing a quick read. Also, can someone add more information<br>
about the specific gnash version/codecs being installed on which XOs<br>
and confirm that the primary issue in developing Flash for Gnash is<br>
picking open codecs?<br>
<br>
Have a great day! or evening!<br>
<font color="#888888"><br>
Charles Merriam<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
On Mon, Mar 24, 2008 at 10:41 AM, Rob Savoye <<a href="mailto:rob@welcomehome.org">rob@welcomehome.org</a>> wrote:<br>
> Steve Holton wrote:<br>
><br>
> > Gnash will *never* be fully compatible with Flash because the closer<br>
> > Gnash gets to being a viable free Flash replacement, the more<br>
> > incentive there is for Adobe to change the Flash specification in a<br>
> > way to break compatibility.<br>
><br>
> They've already changed the format in a big, hence all our hard work<br>
> to reverse engineer SWF v9. ActionScript 3 is finally ECMAScript<br>
> compatible, same as JavaScript, so I doubt that'll change much in the<br>
> future. Also all the changes in SWF v9 were performance oriented, and<br>
> that required a new VM. Gnash now does support the SWF v9 format<br>
> changes, that was easy. It's implementing the ActionScript class<br>
> libraries that's much of the work left. SWF has evolved very slowly, so<br>
> I don't feel we'll be chasing Adobe for long.<br>
><br>
><br>
> > Two decades in the Microsoft format wars should have taught that<br>
> > lesson to everyone by now. Look how long (and how much) it's taken ODF<br>
> > to get where it's at.<br>
><br>
> Yes, but as far as I can tell, OpenOffice works well enough with M$<br>
> Office, compatibility wise, that I haven't had to use M$ Office for many<br>
> years. Not everything converts in OO 100% all the time, but what doesn't<br>
> work I can easily live with.<br>
><br>
><br>
> > OTOH, the XO offers us an opportunity to create a new standard among<br>
> > an audience which has no investment in the old. But this is a limited<br>
> > opportunity.<br>
><br>
> New standards still don't solve the problem of playing existing<br>
> content (often proprietary), which is what I though we were discussing.<br>
> Also playing SWF files in the future is not something we worry about,<br>
> since that will only effect new content, which doesn't exist yet. :-)<br>
><br>
> My point is that we want people to work with us. Most of the time all<br>
> I hear is "Gnash sucks, it's not 100% compatible yet". We know that<br>
> already... What we want to do is identify what "sucks", produce test<br>
> cases, and then fix the problems. Bitching about the problem and dumping<br>
> Gnash does not solve the problem, it merely ignores it. It's the easy<br>
> way out.<br>
><br>
> Yes, it can take some time for an end user with a problem to work with<br>
> us till we identify what is wrong. As none of us can use the Adobe<br>
> player due to clean room problems, it's our end users that help us work<br>
> on testing compatibility. Many people have helped contribute to the<br>
> development of Gnash merely by helping answer questions about what's<br>
> wrong, and trying patches, and most of them were not professional engineers.<br>
><br>
> All we are asking for is help beyond just griping, and patience as our<br>
> small team pushes forward.<br>
><br>
> - rob -<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
><br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br>