Re: [public-houdini] <none>

On Tue, Mar 17, 2015 at 12:41 AM Ian Vollick <vollick@chromium.org> wrote:

> On Tue, Mar 17, 2015 at 12:34 AM Robert O'Callahan <robert@ocallahan.org>
> wrote:
>
>> On Tue, Mar 17, 2015 at 4:48 PM, Ian Vollick <vollick@chromium.org>
>> wrote:
>>
>>> Sure. I have an API sketch here: http://goo.gl/UoeWz0. It's very rough,
>>> high-level, and it's changing regularly, but please do feel free to
>>> comment. I'd appreciate any feedback.
>>>
>>
>> Can you make that public? I think it was, for a moment, and then suddenly
>> it wasn't :-).
>>
>
> Ack, sorry! Please try http://goo.gl/ePFWxI and let me know if you have
> trouble accessing (and commenting).
>
>>
>> One thing I noticed before I lost access was that it mentions running
>> UIWorkers on "the compositor thread". I don't think we need to say that
>> UIWorkers run on the compositor thread, which sounds a bit scary to some
>> people. For example it would probably work just fine to have UIWorkers
>> running in a dedicated thread, which feeds prepared frames to a separate
>> compositor thread, so you can run UIWorkers for frame N while compositing
>> frame N-1.
>>
>
> That makes sense. I'll take another look at the wording.
>
Looks like I'd pointed you at stale content. The second link I posted
should be the _actual_ latest version of the sketch. :) If you have a
chance, please take a look at that one.

>
>> Rob
>> --
>> oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo
>> owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo
>> osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo
>> owohooo
>> osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o
>> oioso
>> oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo
>> owohooo
>> osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro
>> ooofo
>> otohoeo ofoioroeo ooofo ohoeololo.
>>
>