On Mon, Feb 16, 2004 at 04:15:50AM -0300, Gustavo Sverzut Barbieri wrote:
> - Ligatures: please do some kind of ligatures (could be hand-made, I
> can do it if you send me the SVG). "Th" (top) "at"(bottom) "tr"
> (bottom) "tf" (middle)
The logo was done in Photoshop, so I would need to convert it
--- Rob Shortt <[EMAIL PROTECTED]> escreveu:
>
> I was just thinking we could replace the 'program display' popup
> (when
> you press record or select a show fron the scheduled recordings) with
> a
> menu / skin area something like:
>
> +-+
> |+
--- Rob Shortt <[EMAIL PROTECTED]> escreveu: > Rob Shortt wrote:
> > I have to quickly go for a bit but when I return I will followup
> with my
> > ideas for an edit favorites page based on this.
>
> Ok, I was pondering something like:
>
> +-+
> |+---
--- Dirk Meyer <[EMAIL PROTECTED]> escreveu:
> Rob Shortt wrote:
> > Hi,
> >
> > Exprerimenting with pyui and directfb has had me thinking a lot
> about
> > our UI lately. I have been investigating the use of pyui for our
> > popup style dialog boxes because what we use now is slow and
> doesn't
I was just thinking we could replace the 'program display' popup (when
you press record or select a show fron the scheduled recordings) with a
menu / skin area something like:
+-+
|+---+|
||Info area ||
||
Rob Shortt wrote:
I have to quickly go for a bit but when I return I will followup with my
ideas for an edit favorites page based on this.
Ok, I was pondering something like:
+-+
|+---+|
||Info area ||
||
jlaska wrote:
I have to agree with you here, the popup style has it's place for short
informative type messages. But for elaborate screens such as manual
recording, recording, favorites, recording_todo_list...I think the user
experience would be better served with custom SkinArea screens.
When it
Aubin Paul wrote:
My only thought on this matter is that full screen, simple widgets are
better. Even if it takes an extra step. The tree widget you described
below works well on a desktop and a mouse, but is difficult to
navigate with the four arrows, which should be the goal, in terms of
making t
Dirk Meyer wrote:
After you mentioned in at irc, I also thought about it. I vote against
pyui, it's just another dep and as you said, we only need some view
elements like popup boxes.
I vote for doing it the Freevo wait and doing it with the skins and no
complex boxes. I also played with making t
Torben Janssen wrote:
> Hi,
> I just tried a 'freevo cache' and this happens...
>
> Traceback (most recent call last):
>File "/root/freevo_cvs/freevo/src/helpers/cache.py", line 488, in ?
> cache_directories(rebuild)
>File "/root/freevo_cvs/freevo/src/helpers/cache.py", line 203, in
>
Update of /cvsroot/freevo/freevo/src/util
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27520
Modified Files:
mediainfo.py
Log Message:
fix crash
Index: mediainfo.py
===
RCS file: /cvsroot/freevo/freevo/src/util/medi
Rob Shortt wrote:
> Hi,
>
> Exprerimenting with pyui and directfb has had me thinking a lot about
> our UI lately. I have been investigating the use of pyui for our
> popup style dialog boxes because what we use now is slow and doesn't
> impliment the level of features pyui does (layour managers,
I have to agree with you here, the popup style has it's place for short
informative type messages. But for elaborate screens such as manual
recording, recording, favorites, recording_todo_list...I think the user
experience would be better served with custom SkinArea screens.
When it comes to UI d
I have to agree with you here, the popup style has it's place for short
informative type messages. But for elaborate screens such as manual
recording, recording, favorites, recording_todo_list...I think the user
experience would be better served with custom SkinArea screens.
When it comes to UI d
My only thought on this matter is that full screen, simple widgets are
better. Even if it takes an extra step. The tree widget you described
below works well on a desktop and a mouse, but is difficult to
navigate with the four arrows, which should be the goal, in terms of
making things simple.
TV
I have to agree with you here, the popup style has it's place for short
informative type messages. But for elaborate screens such as manual
recording, recording, favorites, recording_todo_list...I think the user
experience would be better served with custom SkinArea screens.
When it comes to UI d
Hi,
Exprerimenting with pyui and directfb has had me thinking a lot about
our UI lately. I have been investigating the use of pyui for our popup
style dialog boxes because what we use now is slow and doesn't impliment
the level of features pyui does (layour managers, containers, etc). Our
po
Hi,
I just tried a 'freevo cache' and this happens...
Traceback (most recent call last):
File "/root/freevo_cvs/freevo/src/helpers/cache.py", line 488, in ?
cache_directories(rebuild)
File "/root/freevo_cvs/freevo/src/helpers/cache.py", line 203, in
cache_directories
util.mediainfo.cac
Thanks... comitted. Seems to work nicely.
On Mon, Feb 16, 2004 at 09:27:09AM -0500, James A. Laska wrote:
> This is a small patch to mimic the tivo-style guide selection. Here's
> how it works:
>
> If you select a program that is >7min in the future...instead of taking
> you to the channel (whic
Update of /cvsroot/freevo/freevo/src/tv
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30143
Modified Files:
tvguide.py
Log Message:
Patch from James A. Laska to make the TV Guide behave intuitively when
clicking on a future program. As you would expect, it now pops up the record
d
Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26525
Modified Files:
directory.py
Log Message:
use ucmp to compare
Index: directory.py
===
RCS file: /cvsroot/freevo/freevo/src/dire
Update of /cvsroot/freevo/freevo/src/util
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26250
Modified Files:
misc.py
Log Message:
helper function for cmp
Index: misc.py
===
RCS file: /cvsroot/freevo/freevo/src/util/
Florian Demmer wrote:
btw clock: a small feature wishplease : make the strftime format
string configurable in local_config.py, so i dont have to remodify the
code next time updating freevo
ok i am stupid: for the record: one just needs to set the format as an
argument when loading the plugin
James A. Laska wrote:
This is a small patch to mimic the tivo-style guide selection.
good idea... i got people afraid of technology and vcr programming in
the family and this makes it more intuitive to use...
I've been testing this and it works well. We could customize the number
of minutes
Update of /cvsroot/freevo/freevo
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19143
Modified Files:
freevo_config.py
Log Message:
Index: freevo_config.py
===
RCS file: /cvsroot/freevo/freevo/freevo_config.py,v
retr
This is a small patch to mimic the tivo-style guide selection. Here's
how it works:
If you select a program that is >7min in the future...instead of taking
you to the channel (which doesn't seem very intuitive since that program
hasn't yet started), it pops up the prgm record dialog. This is how
Update of /cvsroot/freevo/freevo/share/skins/main
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7583
Modified Files:
blurr2.fxd
Log Message:
Clean up the language.
Index: blurr2.fxd
===
RCS file: /cvsroot/freevo/fre
Update of /cvsroot/freevo/freevo/share/skins/main
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7364
Modified Files:
blurr2.fxd
Log Message:
Ran the XML file through xml indent (http://www.cs.helsinki.fi/u/penberg/xmlindent/)
to clean up the indentation.
Index: blurr2.fxd
==
Hi,
I'm running local games (frozen-bubble) and can control it with keyboard -
but would like to control it through lirc too. I'm getting above messages so
it seems like I should only add some proper key mapping to eventhandler for
context games. But how to do this for instance for arrow keys and
29 matches
Mail list logo
