2018-01-19 5:21 GMT+01:00 SungTaek Hong <taxi...@gmail.com>: > Hello, sorry for being late. > > 2018. 1. 17. 오전 5:15에 "Davide Andreoli" <d...@gurumeditation.it>님이 작성: > > 2018-01-16 14:08 GMT+01:00 Sungtaek Hong <sth253.h...@samsung.com>: > > > jpeg pushed a commit to branch master. > > > > http://git.enlightenment.org/core/efl.git/commit/?id= > > 588995da317520fc92660b89b0864bb1f25abc09 > > > > commit 588995da317520fc92660b89b0864bb1f25abc09 > > Author: Sungtaek Hong <sth253.h...@samsung.com> > > Date: Tue Jan 16 20:31:15 2018 +0900 > > > > efl_playable: split Efl.Player interface to Efl.Playable interface > > > > Summary: > > Efl.Player interface simply provides play functions, > > but another interface which indicates Efl.Player will play is also > > needed. > > > > > This seems to me higly confusing, looking at the 2 eo files didn't help > either, > the 2 classes description are: > "Efl media player interface" > and > "Efl media playable interface" > > witch clearly state "media" so I assume audio or video, while this seems > used in Animations :/ > > The Goal of the playable interflace was to indicate that a class can be > played by player interface. So actually playable is "added", not "splitted" > from player. I left the word "media" because I thought Animation was a part > of media but I think I was wrong. I will change the documentation soon. >
What I cannot understand is why we need 2 different ifaces at all. IMHO just a single iface (Efl.Playable) is enougth and should contain methods and props from both Player and Playable. is there a case where a class can inherit from just one of the two? > > > Another issue I can see (not really related to this commit) is that I can > see "volume" and "mute" > in the Player iface, does this means that the Player iface will also > provide more advanced stuff like: > audio/video/subs_tracks_list, audio/video/subs_track_select, etc.. ? > > I think player can provide property that it supports sound, like seekable. > > > Maybe are just that the 2 classes descriptions are wrong, but I really > cannot unserstand the > intent of this split/api design. > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel