Hello Rob, Monday, June 4, 2007, 6:01:00 PM, you wrote: RS> If people cared about quality, they wouldn't waste their time watching RS> YouTube... Seriously, although we all care about the quality, most other RS> people (read, not developers) will just use Gnash for ads on web pages, RS> navigating web sites, or wasting time watching video. We are only really RS> talking about people that build Gnash from source, and just use all the RS> configure defaults.
It's just about knowing in what direction we want to go. As you said, it is *not* performance what we want right now, but you make an exception for OpenGL... So, I can't follow your argumentation. There is not only YouTube, Flash is used for a lot of other movies ;) Just like your commit that slowed Gnash down by 75% (!) and nobody seems to care about. It's okay for me since we (as a team, I personally have other priorities) decided to not focus on performance but then we should decide what we want. BTW, is AGG really so much slower when playing YouTube so that one notices the difference? RS> The people that build binary distributions of Gnash RS> will configure it however they feel like, as my experience is they RS> prefer to supply all relevant options themselves, and not rely on the RS> default behavior being correct. So all this discussion is unnecessary? RS> So we can argue all we want about the default, but the fact is RS> it's a minor issue. Agree. I personally don't care about the release details, but I'd like that we all agree on priorities. It's pointless to fiddle with tiny details (TimelineInfo) when the render fails on simple rendering tasks. RS> Quinn's tasks for Gnash are to focus on the graphics end of Gnash. RS> Initially fixing OpenGL and Cairo, but ultimately maintaining all the RS> renderer backends, so we can all focus on other parts of Gnash. Great! Good to know :) Udo _______________________________________________ Gnash-commit mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-commit
