Re: [Freevo-users] Wonderful work everyone! (And first impressions of the latest SVN)
On Thu, 2011-01-20 at 11:12 -0800, James Trietsch wrote: > On 1/20/2011 08:46, Adam Charrett wrote: > > I've used cancel to allow me to restart the freevo interface by adding a > > while loop in the shell script that start freevo, means I can easily > > restart the interface without waiting for the whole system to reboot. > > Can you raise a feature request for this on the tracker. > Hey, now that's a neat idea I never thought about. Granted, usually when > I need to restart the interface, I'm either already hacking on it (so > I'm logged in) or it's crashed/wedged so bad I can't get back to the > main menu through the interface. > > I'm just thinking out loud here, but wouldn't it be interesting to have > a hidden 'restart interface' button, like the 'hibernate' option in > Windows XP? XP normally shows 'Standby', 'Shutdown' and 'Restart'. But > if you hold down shift, 'Standby' turns into 'Hibernate'. What if > pressing Display while at the shutdown menu, 'Reboot' turned into > 'Restart Interface'? Again, just thinking out loud here. ^_^ > > > > Try out the proper skin 'blurr' rather than my amateur "he's what you can > > do with this" base skin :-) > > > Oh ho! 'Here's a quarter, go get yourself a real interface skin?' ^_^ > > I'm using Blurr, as selected through the interface. I checked and short > of some local modifications I'm playing with, all the files in > share/freevo/skins are up to date with SVN. Of course as I admitted in > the last e-mail, things in my local copy got a bit wonky for a while. > I'll back up my changes to the skin fxds and revert them and see if it > changes anything. In the meantime, is there somewhere else I need to go > to get this proper 'Blurr' skin? Or is it affected by something outside > of share/freevo/skins? The dialog skins use completely different skin files than the main skin and at the moment the GUI can't select which dialog skin to use. To change the dialog skin you need to set a config variable ie DIALOG_SKIN_XML_FILE='blurr' Cheers Adam -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Wonderful work everyone! (And first impressions of the latest SVN)
On 1/20/2011 08:46, Adam Charrett wrote: > I've used cancel to allow me to restart the freevo interface by adding a > while loop in the shell script that start freevo, means I can easily > restart the interface without waiting for the whole system to reboot. > Can you raise a feature request for this on the tracker. Hey, now that's a neat idea I never thought about. Granted, usually when I need to restart the interface, I'm either already hacking on it (so I'm logged in) or it's crashed/wedged so bad I can't get back to the main menu through the interface. I'm just thinking out loud here, but wouldn't it be interesting to have a hidden 'restart interface' button, like the 'hibernate' option in Windows XP? XP normally shows 'Standby', 'Shutdown' and 'Restart'. But if you hold down shift, 'Standby' turns into 'Hibernate'. What if pressing Display while at the shutdown menu, 'Reboot' turned into 'Restart Interface'? Again, just thinking out loud here. ^_^ > > Try out the proper skin 'blurr' rather than my amateur "he's what you can > do with this" base skin :-) > Oh ho! 'Here's a quarter, go get yourself a real interface skin?' ^_^ I'm using Blurr, as selected through the interface. I checked and short of some local modifications I'm playing with, all the files in share/freevo/skins are up to date with SVN. Of course as I admitted in the last e-mail, things in my local copy got a bit wonky for a while. I'll back up my changes to the skin fxds and revert them and see if it changes anything. In the meantime, is there somewhere else I need to go to get this proper 'Blurr' skin? Or is it affected by something outside of share/freevo/skins? Thanks for your help. Always appreciate it. James __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Wonderful work everyone! (And first impressions of the latest SVN)
On Wed, 19 Jan 2011, James Trietsch wrote:
> So for reasons I won't get into (complicated story, and probably
> embarrassing too), despite SVN updates my files were being held back
> because the old copies were considered my working copies and the current
> revisions were being overwritten... I finally sat down today and
> untangled the mess (thank you, revert command!) and fired it back up.
> Some little growing pains (see below) but I got it going and all I can
> say is:
>
> Holy Smokes! It's looking sharp! Great job and many kudos to both the
> developers and everyone out there running Freevo and testing it and
> making suggestions. Maybe it's just because it's been so long since I've
> seen an actual update, but this leap was huge.
>
> Quick things that come to mind:
>
> Biggest problem I had was the system exiting two seconds into playing
> any audio, no traceback or anything. If I started audio and immediately
> kicked it into the idlebar (pressing 'display'), it would play fine.
> When I tried to 'Show Player', it finally coughed up a traceback:
>
> Traceback (most recent call last):
> File "/usr/local/lib/python2.6/site-packages/freevo/main.py", line
> 296, in eventhandler
> consumed = app.eventhandler(event)
> File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
> 858, in eventhandler
> self._handle_play_item(menu, event)
> File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
> 663, in _handle_play_item
> action(arg=arg, menuw=self)
> File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
> 106, in select
> self.function(arg=self.arg, menuw=menuw)
> File
> "/usr/local/lib/python2.6/site-packages/freevo/audio/plugins/detach.py",
> line 157, in show
> self._attach(menuw)
> File
> "/usr/local/lib/python2.6/site-packages/freevo/audio/plugins/detach.py",
> line 142, in _attach
> gui.show()
> File "/usr/local/lib/python2.6/site-packages/freevo/audio/player.py",
> line 151, in show
> self.refresh()
> File "/usr/local/lib/python2.6/site-packages/freevo/audio/player.py",
> line 183, in refresh
> skin.draw('player', self.item, transition=transition)
> UnboundLocalError: local variable 'transition' referenced before assignment
>
> It would appear the definition of 'transition' is held inside an if
> statement, although the skin.draw statement is not. When the if
> statement is bypassed, 'transition' is never set. I fixed it by adding
> 'transition=None' before the if statement, but this may need to be
> better fixed.
That is useful to know I was just about to start investigating that :-)
> LOVE the new text entry screen, and I love the triple-tap shortcuts. I
> just was a little thrown when it came time to enter the line after
> triple-tapping it in. I pressed 'Enter', but since the selector was on
> the 'A', it added an A to the entry box. Perhaps if the triple-tap is
> used, the selector jumps to 'Search', so all you have to do is press
> 'Enter' to go?
I Like this idea I see what I can do
> I also love the new shutdown screen with the colorful icons. The option
> to reboot is very welcome! However, I think it needs a more obvious
> 'Cancel'. I pressed 'Exit' thinking it meant exit the dialog box...
> oops! I know now I can use escape to get out of it, but that's not
> immediately apparent. Perhaps under the three buttons have a long bar
> for 'Cancel'?
Hmm, I've always wondered about my decision not to add a cancel button,
> And speaking of 'Exit', is there an option to get rid of that button for
> those of us with stand-alone dedicated Freevos? On my box, pressing
> 'Exit' will drop you to a terminal window (on the TV) full of leftover
> log information and the only way to restart it is to power cycle or ssh
> in and restart the front-end service. For me, better to just have 'Power
> Off' and 'Reboot'.
I've used cancel to allow me to restart the freevo interface by adding a
while loop in the shell script that start freevo, means I can easily
restart the interface without waiting for the whole system to reboot.
Can you raise a feature request for this on the tracker.
> Tried out the Category Search... I really like it, but I think it needs
> some kind of indicator when there's more than one episode for a listed
> show. Obviously you should select a category to find shows, but I
> couldn't figure out why some shows immediately displayed information and
> some didn't... until I selected one that didn't have any info and found
> the whole submenu of episodes. Again, something that isn't immediately
> obvious. I'm not sure how to do it yet (perhaps something like the icons
> in the Recordings Manager, or display episode names in the info area,
> also like RM?) but it's something to consider.
Again another good idea ...
> Finally, and this is purely aesthetics... the new dialog boxes look a
> little strange. I think it's because they have lightweight borders (one
> pixel?) and light font weights, when the
[Freevo-users] Wonderful work everyone! (And first impressions of the latest SVN)
So for reasons I won't get into (complicated story, and probably
embarrassing too), despite SVN updates my files were being held back
because the old copies were considered my working copies and the current
revisions were being overwritten... I finally sat down today and
untangled the mess (thank you, revert command!) and fired it back up.
Some little growing pains (see below) but I got it going and all I can
say is:
Holy Smokes! It's looking sharp! Great job and many kudos to both the
developers and everyone out there running Freevo and testing it and
making suggestions. Maybe it's just because it's been so long since I've
seen an actual update, but this leap was huge.
Quick things that come to mind:
Biggest problem I had was the system exiting two seconds into playing
any audio, no traceback or anything. If I started audio and immediately
kicked it into the idlebar (pressing 'display'), it would play fine.
When I tried to 'Show Player', it finally coughed up a traceback:
Traceback (most recent call last):
File "/usr/local/lib/python2.6/site-packages/freevo/main.py", line
296, in eventhandler
consumed = app.eventhandler(event)
File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
858, in eventhandler
self._handle_play_item(menu, event)
File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
663, in _handle_play_item
action(arg=arg, menuw=self)
File "/usr/local/lib/python2.6/site-packages/freevo/menu.py", line
106, in select
self.function(arg=self.arg, menuw=menuw)
File
"/usr/local/lib/python2.6/site-packages/freevo/audio/plugins/detach.py",
line 157, in show
self._attach(menuw)
File
"/usr/local/lib/python2.6/site-packages/freevo/audio/plugins/detach.py",
line 142, in _attach
gui.show()
File "/usr/local/lib/python2.6/site-packages/freevo/audio/player.py",
line 151, in show
self.refresh()
File "/usr/local/lib/python2.6/site-packages/freevo/audio/player.py",
line 183, in refresh
skin.draw('player', self.item, transition=transition)
UnboundLocalError: local variable 'transition' referenced before assignment
It would appear the definition of 'transition' is held inside an if
statement, although the skin.draw statement is not. When the if
statement is bypassed, 'transition' is never set. I fixed it by adding
'transition=None' before the if statement, but this may need to be
better fixed.
LOVE the new text entry screen, and I love the triple-tap shortcuts. I
just was a little thrown when it came time to enter the line after
triple-tapping it in. I pressed 'Enter', but since the selector was on
the 'A', it added an A to the entry box. Perhaps if the triple-tap is
used, the selector jumps to 'Search', so all you have to do is press
'Enter' to go?
I also love the new shutdown screen with the colorful icons. The option
to reboot is very welcome! However, I think it needs a more obvious
'Cancel'. I pressed 'Exit' thinking it meant exit the dialog box...
oops! I know now I can use escape to get out of it, but that's not
immediately apparent. Perhaps under the three buttons have a long bar
for 'Cancel'?
And speaking of 'Exit', is there an option to get rid of that button for
those of us with stand-alone dedicated Freevos? On my box, pressing
'Exit' will drop you to a terminal window (on the TV) full of leftover
log information and the only way to restart it is to power cycle or ssh
in and restart the front-end service. For me, better to just have 'Power
Off' and 'Reboot'.
Tried out the Category Search... I really like it, but I think it needs
some kind of indicator when there's more than one episode for a listed
show. Obviously you should select a category to find shows, but I
couldn't figure out why some shows immediately displayed information and
some didn't... until I selected one that didn't have any info and found
the whole submenu of episodes. Again, something that isn't immediately
obvious. I'm not sure how to do it yet (perhaps something like the icons
in the Recordings Manager, or display episode names in the info area,
also like RM?) but it's something to consider.
Finally, and this is purely aesthetics... the new dialog boxes look a
little strange. I think it's because they have lightweight borders (one
pixel?) and light font weights, when the rest of my interface (Blurr)
has heavy borders and bolder fonts. It just doesn't look like it fits. I
also liked the old progress bar (white bar inside blue box) rather than
the new red bar, but I _do_ like it showing numerical progress (like
5/10) when available. The bouncing red bar for the indefinite wait bugs
me... I'd rather see a throbber of some sort that stays put and animates.
Which reminds me, I see the clock icon for the lower right corner is now
animated. That was a great surprise.
Okay, I think I've said enough (for now). And I'll probably have changed
my mind on some of these things an hour from now.
