Hans Meine wrote:
> Am Montag, 02. April 2007 17:59:03 schrieb Dirk Meyer:
>> Right, that is why I used plugin_pause and plugin_resume. But you
>> could not call this functions on applications. So suspend could be an
>> idea for a name, but what about resume? Is it pause/resume for
>> playback or suspend/resume for ressource handling?
>>
>> Now it is still easy to fix:
>> | find ui/src -name \*.py | xargs egrep '(pause|resume|suspend)'
>>
>> Another question is: do we need pause/resume in other ways than
>> ressource handing? There are events for ir pause/resume.
>
> Yeah, I mentioned them before - they are also for freeing/reallocating a
> resource.
>
> Compared with my proposal, I liked your idea of resource_ prefixing, which
> can
> also be used for both plugins and applications. How about resource_list,
> resource_suspend, and resource_resume?
>
> (Although suspend_resource("audio") reads better, a prefix has advantages
> when
> sorting/grouping or for completion in IDEs.)
>
I think the use would be more like this:
list = self.get_resources('audio')
answer = list[0][0].resource_suspend()
...
list[0][0].resource_resume()
other wise we (the resource handler) would need to hold count of witch
one was running before. this way only the one that suspends an other one
needs to now how he has suspended.
The answer would be like dischi proposed before. The list would be like
yet a dict with the resource users and the resource type they are holding.
Mathias
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
