yeah i've always wanted to give mpd a shot but it seems like a lot of work just to play music, and i don't really see the benefit. i talk to the guy who develops gmpc on #ubuntuforums every now and then.

now that i've looked at the example config file, i've become a bit less keen on it.. maybe another day when i have lots of time to waste.

exactly...

damn, i wanna do some work on that applet i linked to, and reading up on gnome programming stuff i brain melting. perhaps i am trying to gain more info than i really need?

have you looked at the applet's source code yet? i assume that would give you a better idea of what to research.

oh yeah of course, but i've never used gtk or any of that stuff, i have no idea what the gnome standards are, i have no idea how to get the modified source back to the author, etc...

anyways, the only actually coding i need to do right now is figure out how to detect a mouse-over instead of a mouse-click

at least you're starting small!

any suggestions? :-/

i can't find a reference for it anywhere and i have no idea if it's a gtk+ thing or a gnome libs thing or what.

so i'm downloadin' today's build of the feisty herd 2 (live) cd :D

i kinda got the itch to see how things are shaping up; i'm sure i'll be posting my thoughts later in the day (got about ~1.5 hours of download time left, then the fun will begin).

i would assume it's a gtk thing, 'cause you'd just being using an event handler to catch a mouse-over event. at least, that's what i assume. have you checked through the tutorial? http://www.gtk.org/tutorial/

gg

so far i have basically just started at developer.gnome.org, and then followed links from there for anything relevant.
'
thanks

have you ever tried to setup obpager?? it looks like a nice addition to my openbox environment, but i'm having strange problems when i try to build it. kinda frustrating.. i think i'll go back to it later.

yeah nothing but problems when i tried recently.

openbox kinda sucks in Ubuntu right now (although you are in arch, but might encounter the same issues).

pypanel doesn't work, and some other things weren't packaged correctly

pypanel isn't tough to fix in ubuntu.

aside from that, and that little problem with the names of libobparser and libobrender which cause obconf to screw up, openbox has always worked just fine for me in ubuntu. both problems are relatively easy to solve (though that's not an excuse for them.. 'cause both should just work in the first place)

i don't think i like arch as much anymore. it's a nice system, but some of the things that i've had to manually configure that it should be able to figure out for me.. it's getting on my nerves. my burner doesn't work properly.. not sure how i'll get that fixed. and i don't really like pacman all that much; aptitude and portage are both considerably better.

yeah the thing with pypanel and obconf is that they just should work. and when you are planning on writing a script that installs those, it's kind of a pain in the ass to have to fix someone else's mistake.

as for arch, i agree. i don't mind so much having to configure gnome or whatever to my liking, but i just don't understand why i actually have to do so much. i know they keep a KISS philosophy, but still... if i install a daemon, such as GDM, why wouldn't i want it in the daemons list in rc.conf? there are little things here and there too that should be more automated. plus, arch doesn't really follow a standard linux setup anyways, so it's not really an all purpose learning tool.

the keep-it-simple approach is a nice idea, but i don't think it would fly with most people. i think i'll just stick with ubuntu.. if i do a base install with the server disc, and then build it up just like i did with arch, i assume that the difference in performance will be negligible.

i think i am getting the hang of GTK programming. haven't really gotten my hands too dirty with it quite yet, and every example is in C and not Python (which is fine, i know C better than Python, but i plan on using Python). signals and events are slowly making a little more sense to me.

once you get used to it, coding functions to handle events is no big deal. i find actually designing a gui and getting it to look decent much more frustrating :(

do you mean like coming up with a beautiful interface concept in your head, or taking a beautiful concept and actually getting it to work out in gtk?

i think i am moving along quite nicely. i was able to add the "quit" button at the one part with no problem, and now i realize that i didn't have to declare GtkWidged *quitbutton, because the *button that was already declared can be used to make any new button!

i was talking about actually coding it, though coming up with a good ui (by drawing mockups and so on) can be equally difficult.