[Moonlight-list] Moonlight as a primary Mono GUI (+ about rendering engine)

[Kosenko Max]

Alan McGovern-2 wrote:
> While I definitely don't speak for everyone, I'd assume our position is
> this:
> 
> 1) We're not feature complete yet.
> 2) The existing rendering engine works
> 3) We still have to do some optimisation passes to improve perf because we
> do suck in certain cases.
> 
> So why would we waste man days/weeks rewriting code to use a slower less
> mature engine when we already have perf issues and known bugs? If you want
> to discuss the idea in detail you could join the #moonlight irc channel,
> or
> maybe someone else will respond here, but for now I sincerely doubt the
> idea
> would even be considered ;)

1. Agg-sharp is not worse than 50% of native AGG. I believe it's faster than
Cairo, but that need to be proved. Anyone with Cairo under Mono knowledge
will help in that a lot.

2. I'm not talking about moving your attention from feature development. I'm
talking about future plans. From what I've heard - hardware use of Cairo for
Moonlight still not proved to be achievable at all. And Cairo is much bigger
than agg-sharp and native project.

3. Aren't there real benefits for Moonlight to use managed rendering engine
and be less dependent?
-- 
View this message in context: http://www.nabble.com/Moonlight-as-a-primary-Mono-GUI-%28%2B-about-rendering-engine%29-tp24446791p24460760.html
Sent from the Moonlight mailing list archive at Nabble.com.