Update of /cvsroot/freevo/freevo/src
In directory sc8-pr-cvs1:/tmp/cvs-serv23454/src

Modified Files:
        item.py directory.py 
Log Message:
Ok,  now it shows the "Coming Up" list anywhere in the TV menu. I think
it fits, though it looks fairly ugly right now. I'm going to make it more
flexible after I get some listings for 'tomorrow' since mine expire tonight.

I like this as a feature, but I'm wondering if someone has an idea on a
cleaner way to implement this. This is a little hackish, since "Coming Up"
isn't really a item "property" so it doesn't exactly fit in the object
model.

I did remove it from directory.py, so that's at least more logical.

Maybe we should have a general function in item.py to call extra
functions, or a way to embed python in the skin which isn't so nice.

Ideally, we need a different way to have "default" information in an info
area, as opposed to putting it in the item. 



Index: item.py
===================================================================
RCS file: /cvsroot/freevo/freevo/src/item.py,v
retrieving revision 1.47
retrieving revision 1.48
diff -C2 -d -r1.47 -r1.48
*** item.py     10 Jan 2004 16:49:37 -0000      1.47
--- item.py     11 Jan 2004 04:04:37 -0000      1.48
***************
*** 10,13 ****
--- 10,31 ----
  # -----------------------------------------------------------------------
  # $Log$
+ # Revision 1.48  2004/01/11 04:04:37  outlyer
+ # Ok,  now it shows the "Coming Up" list anywhere in the TV menu. I think
+ # it fits, though it looks fairly ugly right now. I'm going to make it more
+ # flexible after I get some listings for 'tomorrow' since mine expire tonight.
+ #
+ # I like this as a feature, but I'm wondering if someone has an idea on a
+ # cleaner way to implement this. This is a little hackish, since "Coming Up"
+ # isn't really a item "property" so it doesn't exactly fit in the object
+ # model.
+ #
+ # I did remove it from directory.py, so that's at least more logical.
+ #
+ # Maybe we should have a general function in item.py to call extra
+ # functions, or a way to embed python in the skin which isn't so nice.
+ #
+ # Ideally, we need a different way to have "default" information in an info
+ # area, as opposed to putting it in the item.
+ #
  # Revision 1.47  2004/01/10 16:49:37  dischi
  # add long to possible length
***************
*** 408,411 ****
--- 426,433 ----
              else:
                  return '%d:%02d' % (length / 60, length % 60)
+ 
+         if attr in ('comingup'):
+                     return util.comingup(None)
+ 
  
          if attr[:4] == 'len(' and attr[-1] == ')':

Index: directory.py
===================================================================
RCS file: /cvsroot/freevo/freevo/src/directory.py,v
retrieving revision 1.93
retrieving revision 1.94
diff -C2 -d -r1.93 -r1.94
*** directory.py        11 Jan 2004 03:22:30 -0000      1.93
--- directory.py        11 Jan 2004 04:04:37 -0000      1.94
***************
*** 10,24 ****
  # -----------------------------------------------------------------------
  # $Log$
! # Revision 1.93  2004/01/11 03:22:30  outlyer
! # First try at the "Coming Up" page. It only shows up when a directory in the
! # TV menu is selected, but I'm working on a way to have it show up for the
! # rest of the TV menu.
  #
! # TODO:
! # o Cache the coming up list for an hour at a time (misc.py)
! # o Cleanup the 'comingup()' function, it's currently just executable pseudo-code 
(misc.py)
! # o Show the Coming Up list for all items (skin)
  #
! # If you don't use 'blurr2.fxd' this will have no effect on you whatsoever.
  #
  # Revision 1.92  2004/01/10 13:19:05  dischi
--- 10,30 ----
  # -----------------------------------------------------------------------
  # $Log$
! # Revision 1.94  2004/01/11 04:04:37  outlyer
! # Ok,  now it shows the "Coming Up" list anywhere in the TV menu. I think
! # it fits, though it looks fairly ugly right now. I'm going to make it more
! # flexible after I get some listings for 'tomorrow' since mine expire tonight.
  #
! # I like this as a feature, but I'm wondering if someone has an idea on a
! # cleaner way to implement this. This is a little hackish, since "Coming Up"
! # isn't really a item "property" so it doesn't exactly fit in the object
! # model.
  #
! # I did remove it from directory.py, so that's at least more logical.
! #
! # Maybe we should have a general function in item.py to call extra
! # functions, or a way to embed python in the skin which isn't so nice.
! #
! # Ideally, we need a different way to have "default" information in an info
! # area, as opposed to putting it in the item.
  #
  # Revision 1.92  2004/01/10 13:19:05  dischi
***************
*** 299,305 ****
              return space
        
-         if attr in ('comingup'):
-             return util.comingup(None)
- 
          return Item.getattr(self, attr)
  
--- 305,308 ----




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Freevo-cvslog mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-cvslog

Reply via email to