Re: [clutter] Asynchronous Lazy Actor and Containers API design

2007/8/27, Matthew Allum <mallum@openedhand.com>:
>
> Hi;
>
> On Sun, 2007-08-26 at 05:40 +0100, Alberto Ruiz wrote:
> [snip - all interesting]
> >
> > - What should I do to make an actor not to waste any video memory
> > - Should I implement the Async/LazyActor as an interface? May I
> > implement it as a ClutterContainer to be able to show the
> > PendingTaskActor as well?
> > - How can I make the PendingTaskActor not to waste any video memory
> > once the content is loaded?
> > - Should I split the AsyncActor and the LazyActor as different
> > interfaces?
> > - Am I on crack?
>
> No, definitely not - But Im not sure what the best solution is to
> handling and managing things like texture memory better. One idea I've
> had is a ClutterTextureProxy which would release texture memory under
> defined conditions (i.e goes to position offscreen) by unrealizing an
> underlying texture to free memory but still behave API wise like it was
> still there. Still thinking about this..
>
> The best I can suggest is implement it and experiment so we get a better
> understanding. Just note we want to keep the clutter core pretty raw and
> generic but very flexible. For very high level and very specific
> functionality we've talked about creating a separate clutter-extras or
> some such package.
>
> Many thanks;
>
> -- Matthew
>
>

-- 
Un saludo,
Alberto Ruiz
------=_Part_155912_7630719.1188265713130
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">2007/8/27, Matthew Allum &lt;<a href="mailto:mallum@openedhand.com">mallum@openedhand.com</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi;<br><br>On Sun, 2007-08-26 at 05:40 +0100, Alberto Ruiz wrote:<br>[snip - all interesting]<br>&gt;<br>&gt; - What should I do to make an actor not to waste any video memory<br>&gt; - Should I implement the Async/LazyActor as an interface? May I
<br>&gt; implement it as a ClutterContainer to be able to show the<br>&gt; PendingTaskActor as well?<br>&gt; - How can I make the PendingTaskActor not to waste any video memory<br>&gt; once the content is loaded?<br>&gt; - Should I split the AsyncActor and the LazyActor as different
<br>&gt; interfaces?<br>&gt; - Am I on crack?<br><br>No, definitely not - But Im not sure what the best solution is to<br>handling and managing things like texture memory better. One idea I&#39;ve<br>had is a ClutterTextureProxy which would release texture memory under
<br>defined conditions (i.e goes to position offscreen) by unrealizing an<br>underlying texture to free memory but still behave API wise like it was<br>still there. Still thinking about this..<br><br>The best I can suggest is implement it and experiment so we get a better
<br>understanding. Just note we want to keep the clutter core pretty raw and<br>generic but very flexible. For very high level and very specific<br>functionality we&#39;ve talked about creating a separate clutter-extras or
<br>some such package.<br><br>Many thanks;<br><br>&nbsp;&nbsp;-- Matthew<br><br></blockquote></div><br><br clear="all"><br>-- <br>Un saludo,<br>Alberto Ruiz
------=_Part_155912_7630719.1188265713130--
-- 
To unsubscribe send a mail to clutter+unsubscribe@o-hand.com