[Gnash-dev] release status

2007-05-30 Thread strk
It's about time to get release 0.8.0 out.
I'm currenlty busy on stabilizing youtube/lulu.tv.
What I'm tracking right now is the FFMPEG implementation,
not giving much attention to GST atm.

As a reference for show-stopper I'm using savannah, in particular
bug with severity from BLOCKER to SECURITY. We have 4 of them:

 #20002 Linking gnash against current ffmpeg SVN fails  build   
 #19913 Youtube: the movie stops playing while streaming after 10-15 
secs
 #19898 lulu.tv segfault on OpenBSD 
 #19886 segfault playing rtmp-v7.swf from testsuite (NetStreamGst)

All except #20002 are NetStream related so that seems the part needing some 
focus/help
by everyone. Today Thomas and me extracted a design document from current
implementation and made a plan for a redesign we belive would make things 
cleaner/safer.
See the server/asobj/README.NetStream file for more info.
Comments on that document are welcome.

Any followup on the above bugs is also welcome. Note that the FFMPEG version of 
NetStream
has been cleaned up in the past couple of days.

At the moment we just care about segfaults, threading issues and build errors, 
so if you find
any please file a bug report so it's clear what's left.

Thanks.

--strk;

 ()   ASCII Ribbon Campaign
 /\   Keep it simple! 



___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev


[Gnash-dev] release status

2006-10-11 Thread strk
An update on current status:

- fix font anti-aliasing;

STILL TO DO

- implement new SDL-based sound backend;

DONE, might need more testing

- warning-free builds;

some warnings left in amf.cpp and a lot
in render_handler_agg.cpp

- involve more tests in `make check'.

we'd need a better dejagnu test to run all
tests. currently there's a mix of doxygen
and automake default testing. this makes
any error under testsuite/actionscript.all
to interrupt the 'make check', and also
and error under testsuite/libbase or
testsuite/server or testsuite/misc-ming.all
to abort.
I guess a single site.exp file that runs *all*
tests and prints a *single* report would be
more acceptable.

--strk;



___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev


Re: [Gnash-dev] release status

2006-10-11 Thread Rob Savoye
strk wrote:

   DONE, might need more testing

  It needs more testing. There was the comment (bug report) from a few
days ago than mention issues with the volume of music and sound effects.

 - involve more tests in `make check'.
 
   we'd need a better dejagnu test to run all
   tests. currently there's a mix of doxygen
   and automake default testing. this makes

  Doxygen testing ? I can look into the test cases aborting.

   I guess a single site.exp file that runs *all*
   tests and prints a *single* report would be
   more acceptable.

  Typically the site.exp file is just a post configuration data file.
The test driver is swf_exists.exp, and it was originally only created
for the does this class and method test cases, much of which don't do
more than this. For a better test driver I'd probably want to wrap an
other test cases that use a different style of testing.

- rob -


___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev


Re: [Gnash-dev] release status

2006-10-11 Thread Tomas Groth

--- Rob Savoye [EMAIL PROTECTED] skrev:

 strk wrote:
 
  DONE, might need more testing
 
   It needs more testing. There was the comment (bug report) from a few
 days ago than mention issues with the volume of music and sound effects.
 

There are known solutions for reported issues, but I haven't had time to
actually implement it, but will within a few days...

cheers,

Tomas


___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev


Re: [Gnash-dev] release status

2006-10-11 Thread strk
On Wed, Oct 11, 2006 at 07:13:25PM +0200, Udo Giacomozzi wrote:
 Hello strk,
 
 Wednesday, October 11, 2006, 7:00:02 PM, you wrote:
 s - fix font anti-aliasing;
 s STILL TO DO
 
 I proposed a solution...
 Thread: Re[2]: [Gnash-dev] GTK-AGG GUI
 Date: Tue, 10 Oct 2006 18:57:56 +0200
 
 No response so far.

mm.. I'll check that out (links to the archives are better for this
kind of references: see http://lists.gnu.org/archive/html/gnash-dev/)

 And another one:
 Does the parser really start reading everything? Can't it stop after
 the header so that the stage size is known and the renderer can be
 initialized (and after that become multithreaded)?

I guess we can do that, but it won't fix the antialiasing problem.
That is due to the fact that the generation of textured glyphs
must currently happen once at end of parsing, while we need them
during play and cannot wait for end of parsing.

 s - warning-free builds;
 s some warnings left in amf.cpp and a lot
 s in render_handler_agg.cpp
 
 I know, hopefully I have some time for that tomorrow.
 
 
 I think I found a bothering bug involving buttons. Still need to
 make a testcase for it. It really affects interaction with movies.
 Will tell you more ASAP.

Be aware that the new MovieTester class might be also used for
existing SWF (no need for Ming) so eventually I'd put SWF
somewhere (movies.all ? samples ?)

--strk;



___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev


Re: [Gnash-dev] release status

2006-10-11 Thread strk
On Wed, Oct 11, 2006 at 11:29:07AM -0600, Rob Savoye wrote:

  we'd need a better dejagnu test to run all
  tests. currently there's a mix of doxygen
  and automake default testing. this makes
 
   Doxygen testing ? I can look into the test cases aborting.

Ehm.. sorry, dejagnu of course.

  I guess a single site.exp file that runs *all*
  tests and prints a *single* report would be
  more acceptable.
 
   Typically the site.exp file is just a post configuration data file.
 The test driver is swf_exists.exp, and it was originally only created
 for the does this class and method test cases, much of which don't do
 more than this. For a better test driver I'd probably want to wrap an
 other test cases that use a different style of testing.

I've had most test conform to the dejagnu printing of PASSED
and FAILED so the output parsing of swf_exists.exp can be used
the way it is, maybe the swf_exist (build .swf and run gprocessor)
part might be a subroutine for use only under actionscript.all
and have different subroutines for other dirs ?

--strk;


___
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev