On Wed, Mar 11, 2015 at 7:00 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Tue, 10 Mar 2015 19:41:34 +0900 (KST) ChunEon Park <her...@naver.com> said: >> it's totally depends on app/design and scenarios. >> please imagine in point of their side. >> it's enough to capture the screen to use as the thumbnail / profile resource >> (debug) / any post - effects etc... > > i am trying to imagine and i can see the only reason an app may want to > capture > content is for doing a screencast - the compositor would be the one doing it, > and this involves a far different api than just a screenshot. the other > examples i can think of are examples of doing thsi in the wrong place. the > wm/compositor should be storing screenshots of an pp and showing them on app > launch before the app has started,m and replacing the "placeholder > image" (screenshot) with the app window when it finally appears. so this is a > case where the api isn't needed unless this is being "done wrong".
Another use case is exactness. We could actually check that a backend behave the same as the reference software implementation. That use case is very close to the one of actually doing screen cast I think. -- Cedric BAIL ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
