Starting to test gnash slowly

May 14th, 2008

One of my projects, Internet Floor Plans, uses ming to generate swf-powered interactive floor plans. I recently decided to open source the project, and it only made sense to get it working with gnash.

I sent a note to the gnash mailing list that I'd been involved with ming, and would like to help out gnash. Strk suggest I work on testing, and it made perfect sense.

I just wrote a small test using some old code I wrote as a ming example, and the cpu pegged. Doh! This was the problem:


I guess it makes the movie play as fast as possible. I removed that line and the cpu in not 100% for the gtk-gnash process. Good!

After a quick irc conversation with strk on #gnash, I'm going to test the same movie on Windows using a debugging flash player, hopefully available from Adobe, and an actionscript to monitor fps.

Also want to test the rate of 100 down to 80.

I'm also going to test building gnash against a few different versions of ming, 0.3 - 0.6, as well as reviewing actionscript.all, and

Wow, its been years since I've used irc, but its pretty amazing! Strk just helped me figure out the gnash tests really well. I'm going to try wrapping asm {} blocks with #ifdef MING_SUPPORTS_ASM.


Yearly Indexes: 2003 2004 2006 2007 2008 2009 2010 2011 2012 2013 2015 2019 2020 2022