Hi, I believe a not too intrusive way to display metadata would be below the current preview. Transition wise, the preview could shrink a bit after a couple of seconds to make space for metadata text that could fade in. What do you think?
Florian El lun, 07-01-2008 a las 10:24 -0800, Kevin Fox escribió: > On Mon, 2008-01-07 at 18:58 +0100, Philippe Normand wrote: > > Le lundi 07 janvier 2008 à 18:39 +0100, Patrick Dessalle a écrit : > > > Hello, > > > > > > I don't know if it's the right place to ask question but I don't like > > > IRC ^^ > > > > > > I've tested Elisa (ubuntu gutsy packages) on the computer hooked on my > > > TV but there are a few limitations that make it quite unusable for me > > > (the main issues being the subtitles handling > > > > I believe we still support subtitle files (but not vob sub yet). Just > > name your sub file like the video file, but with a different extension, > > depending on the sub format (srt or txt in most cases). > > > > > and the fact that file/folders names are truncated which isn't very > > > useful when trying to watch videos of some tv show since you don't > > > always get to see the season and episode number). > > > > Well, there's no easy answer to your concerns at this point. The ideal > > solution would be to not cut labels but make them horizontally animated. > > Eg, make them move from left to right back and forth, slowly. > > Unfortunately that's not supported yet in Pigment. :( > > Not a very general solution. When you have a lot of similar things like > 4 seasons of some show, you need more data then a scrolling filename can > easily provide. > > I've been working a bit on a MythTV plugin for Elisa, and kind of run > into the same problem. I think a better solution would be to split the > screen into two parts. The top half or 2/3rds would be the way things > are now with the icons/preview, and the bottom part would be the full > file name, or if there is metadata, the metadata provided by the plugin. > stuff like: > > The Simpsons - Episode 3 > Channel: 4 > Date: 12/04/2007 > Description: > Lisa gets a .... > > See (http://www.mythtv.org/mythimages/conflictresolution.png) for a > screenshot of Myth. Think, the bottom half of that screenshot, with the > top half being elisa's file chooser. > > Kevin > > > > > > Other than that, elisa is a very promising project and one of the big > > > selling point for me, compared to mythtv and freevo, was that > > > installing the deb and running it just worked with HAL support and > > > without too much conf file tweaking. > > > > > > I'd like to check out if the current SVN version would be something I > > > could use on my TV (meaning the bugs that annoy me are fixed) or if I > > > should create new tickets or try to write some plugins myself. > > > When I run elisa.py on a "fresh" update (i.e. without any ~/.elisa > > > folder), the programs fails to load a component. I've tried each and > > > every *.conf from the sample_config folder and they all fail on some > > > exception at some point. Usually something about a frontend that can't > > > be created. > > > > > > > Can you give more details please? What component is failing to load. If > > you all dependencies to be installed, install the "elisa-extra" package. > > > > > By the way, on hal_service.py, line 62, on my version of dbus (0.82.4 > > > from Debian sid), I don't have a property "message" for DBusException, > > > I've modified that line (you don't use the value of message anyway) to > > > let elisa fail at some later point. > > > > > > > Hmm ok, can you give us the traceback you got? We'll find a proper fix > > for it, for all versions of DBus deployed around ;) > > > > > My question/suggestion is basically: does elisa run straight out of > > > svn (meaning i messed up somewhere) or is it normal that it doesn't > > > work on my machine ? > > > > > > > For now, I advise you to wait the release to use Elisa "in production". > > We are fixing some issues still, there will have some activity in SVN > > this week :) If you're using Sid, the official Elisa package will be > > updated shortly after the release. > > > > > Thank you for having read this awfully long email, > > > > > > > You're welcome, thanks for the feedback :) > > > > Philippe
