I just had a possibly useful idea.. The big difference between the iPod and iTunes UI is that in the iPod, the playlists and song info are displayed one at a time, while in iTunes they're all onscreen at once.
Maybe what this would lead up to is a framework for defining modules of information, and automatically displaying the one the uer is interacting with, plus however many else will fit on the screen? On Mon, May 27, 2002 at 08:57:19PM -0600, Micah Dowty wrote: > On Mon, May 27, 2002 at 02:28:16PM -0700, Joshua Haberman wrote: > > * Micah Dowty ([EMAIL PROTECTED]) wrote: > > > Hmm... and gstreamer even has python bindings! > > > > > > It would make a lot of sense to write the media player in python and > > > using gstreamer. That would make the media player require non-small > > > things like python and glib, but it's probably safe to assume that any > > > machine that you would want to play media on could handle that. > > > > This was my exact idea several months ago! When I mentioned it then on > > #picogui, everone asked "why not just write a frontend to mpg123?" :-) > > Hmm.. I probably wasn't there at the time ;) > > > > > But Python bindings for gstreamer did not exist then, and so I may be > > tempted to try this again soon. I have a good friend who is much better > > at UI design than me, so I will ask for his input on UI issues. > > > > For UI, what ballpark of screen resolutions are you targetting? What > > input devices are most relevent? I know that PicoGUI is technically > > agnostic to these things, but I think they are still important as far as > > UI design goes. > > I agree that it's good to know what device you're targetting.. Using Widget >Templates it should be possible to separate the UI layout from the app code, but it's >still important to design the UI's functionality well. > > I can see four classes of devices you might want to play media on... > 1. Cell-phones or dedicated music players, with very small displays and keypad or >scroll-wheel based user input (think iPod :) > 2. PDAs with sufficient processing power (Agenda VR3, Zaurus...) > 3. Set top boxes, with large amounts of relatively low-quality screen space, plus >limited user input (remote control) > 4. PCs or other devices with large screens and a rich set of input devices > > You could probably use the same type of UI with only WT or theme-level changes on >classes 1&2 and classes 3&4. The GUIs in use between a cell-phone and a set top box >though would probably have programmatic differences as well. This would be a lot like >the difference between iTunes and iPod. (Brandon has an iPod that I've been able to >look at, and it's UI is quite nicely done.. not to mention the sexy hardware ;) > > > > > Joshua > > > > -- > > Joshua Haberman <[EMAIL PROTECTED]> > > -- > Only you can prevent creeping featurism! > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Pgui-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/pgui-devel -- Only you can prevent creeping featurism! _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
