[00:20] <persia> blahblahx: Not for 8.04.  Should be doable for 8.10.
[00:32] <ogra> well, it will change your complete defaults as long as ubuntu-mobile-default-settings is installed
[00:32] <ogra> (in 8,10)
[00:35] <persia> Yeah, but it's 8.10.  Installing ubuntu-mobile in hardy is an exercise in frustration, more than anything else.
[00:42] <ogra> yeah
[13:41] <smp4488> anyone up?
[13:44] <smp4488> how would i go about embedding rythmbox into a custom interface
[13:52] <maniheer> !hi
[13:52] <maniheer> does anyone know if ubuntu mobile would work on a mio 269?
[13:53] <persia> maniheer, what's the specs?
[13:53] <maniheer> dunno
[13:53] <maniheer> got it yesterday
[13:53] <maniheer> :P
[13:54] <maniheer> and google ain't helping
[13:57] <persia> OK.  Do you know which processor it uses?  What OS is on it now?
[13:57] <maniheer> its on WinCE
[13:57] <maniheer> no idea about processer
[13:58] <maniheer> i think 300mhz
[13:58] <maniheer> and 2.5 GB
[13:58] <persia> OK.  I found http://www.mio-tech.be/en/gps-navigation-device-Mio-269-plus-specifications.htm
[13:58] <maniheer> thats all I know
[13:58] <maniheer> thats the one
[13:58] <persia> Launchpad doesn't have any ARM buildds, so Ubuntu can't support ARM, so it won't work.  You might try the rebuild from mojo.handhelds.org
[13:59] <maniheer> errrm
[13:59] <maniheer> wats ARM?
[13:59] <persia> WIth that low a resolution, I'd recommend looking for something different anyway : at QVGA, you want a very specialised interface.
[13:59] <persia> www.arm.com : it's a processor architecture.
[13:59] <maniheer> ohhh
[14:00] <maniheer> but I dont like what they've got preinstalled
[14:00] <maniheer> its ****
[14:00] <maniheer> i'd rather use google maps
[14:01] <persia> You'll probably either have to do something custom, or look for a embedded community that supports QVGA.
[14:02] <persia> Currently, Ubuntu supports down to 800x600, and there's work to get that down to 640x480, but I've not heard of anything that was known to work at 320x240, and Ubuntu Embedded has been quiet for a while.
[14:02] <maniheer> so i'm stuck
[14:04] <maniheer> time to go reinstall WinCE
[14:04] <maniheer> bye
[14:04] <maniheer> and thnx
[14:42] <smp4488> im trying to write a c program to control rythmbox
[14:42] <smp4488> do i need to use the dbus?
[15:31] <persia> smp4488, For rhythmbox customisation, you probably want a rhythmbox-specific channel.  Here we might be able to help you with a variant hildon interface if you wanted that (although I'm not sure how helpful we could be).
[15:33] <smp4488> i basically want an overlay to make a media player
[15:33] <smp4488> and then have rhythmbox running in the background
[15:36] <persia> That sounds overly complex.  I'd suggest either building a hildon interface for rhythmbox, or a dfferent gstreamer-based music player (there are a few in the repos).
[16:03] <smp4488> how would i go about building an interface?
[16:03] <persia> I'm entirely the wrong person to answer that, but glade seems popular.
[16:04] <smp4488> see thats what i was thinking and using python to code the buttons to do simple things like forward, play, and back
[16:07] <persia> Makes sense.  If you're going to use rhythmbox, I'd recommend doing it inside the rhythmbox code as an extended UI.  If you want to do it in python, I'd suggest something like decibel as a base.
[16:13] <smp4488> so what do you think
[16:14] <persia> I think that having something better than totem for playing audio would be nice.  Which way you do it is up to you.
[16:15] <smp4488> i was thinking or embedding rhythmbox
[16:15] <smp4488> i dont know if you have ever heard of roadrunner for windows
[16:16] <smp4488> it uses winamp for its functions
[16:16] <smp4488> it hides winamp but you can use most of its functions inside of the "skin"
[16:19] <persia> Right.  That doesn't sound to be like a lightweight solution.  rhythmbox is basically a library manager wrapped around gstreamer with plugin support.
[16:19] <persia> That's why I pointed you at decibel if you want to do it in python : creating a decibel-hildon package as a separately built binary in the install process should be fairly easy (take a look at update-manager vs. update-manager-hildon for an example of how to do this).
[16:20] <persia> Then you can tweak the interface there, take advantage of the smaller backend (with mostly the same technologies as rhythmbox).
[16:21] <persia> If you want to do it in rhythmbox, I'd suggest the same: building an alternate frontend within rythymbox, rather than a wrapper, but that's not python.
[16:21] <smp4488> true
[16:22] <smp4488> i was wanting library and playlist functions thats why i thought rhythmbox
[16:22] <persia> Right : I'm just suggesting that rather than trying to embed the whole app, you extend it internal to the code.
[16:23] <persia> Or if you want to use python, you select one of the music players already written in python, and extend that.
[16:23] <smp4488> makes sense
[16:23] <persia> Building a wrapper usually takes more disk space, memory, and processing power, and those are precisely the things that are often lacking in smaller devices.
[16:23] <smp4488> decibel looks good
[16:25] <smp4488> so then instead of adding on top i take the existing interface and modify it
[16:25] <persia> So just extend the interface to fit inside the hildon interface, and then tweak to meet your needs.  Should be fairly straightforward.
[16:26] <smp4488> now i just have to learn python. i know c# but thats about it
[16:26] <persia> If you're careful about how you write the code, you should be able to adjust the packaging to have decibel, decibel-common, and decibel-hildon.
[16:26] <smp4488> lol
[16:26] <persia> heh.  Well, at least you have a python project :)  If you want to learn GTK instead, you could do the same thing with rhythmbox.
[16:27] <smp4488> so now it comes time to choose a path
[16:28] <smp4488> i want to learn gtk but i dont see it as a traditional language
[16:29] <persia> It's C : probably the most traditional language for unix programming.
[16:30] <smp4488> yea but it is low level
[16:30] <persia> Mind you, the GTK libraries encourage writing C in a way that is a little different from other people.
[16:30] <persia> It's not really that low-level when you're just gluing GTK, GNOME, GIO, and gstreamer.
[16:30] <persia> C can do low-level, but it can also do high-level.
[16:32] <smp4488> i need to learn a few
[16:33] <smp4488> so gtk is just a library for c?
[16:35] <persia> Yep, as are the others I mentioned.
[16:35] <persia> All of them also have python bindings.
[16:35] <persia> You'd be using the same libraries for either language : it's just a matter of which language you want to use to program.
[16:35] <smp4488> that makes more sense
[16:35] <smp4488> time to take a dive in a direction
[16:35] <smp4488> what do you prefer?
[16:37] <persia> C, but that's because I learned C a very long time ago (well before python was ever imagined).  I'd recommend picking whichever seems more common for the sorts of applications you want to modify.
[16:39] <smp4488> im coming from c# so what do you think?
[16:40] <persia> I can't say.  I don't know C#  From the name, it might be like C, but I have heard it's fairly different.
[16:40] <persia> Perhaps you'd do best to read some C code and some Python code, and see which you find easier to understand.
[16:41] <smp4488> alright we will see what happens