Re: Re: xmms-devel Digest, Vol 4, Issue 5

On Sun, 2004-02-08 at 19:03, Matthew Rubenstein wrote:
> 	To be clear, by "real developers" I mean members of the XMMS team, with
> commit privs. Plenty of "real developers", hacking code, fixing bugs,
> and adding features, have posted to this list, but I've not seen
> response from the XMMS team to encourage submission. Or is there some
> feedback loop I'm missing?


I fear development of xmms has pretty much stopped or has become very
inaccessible (which basically means that is has stopped or reduced to
bugfixing). You might want to take a look at beepmp which appears to be
a Gtk2.0 port of xmms (but far from finished imho).

Also, I tried fixing that dnd stuff (look at my mails of this weekend)
but the way xmms has been coded is so awkward and wierd .. that it is
damn hard to get something done :-(.

For example.. It's very hard to get dnd-events in only the listbox with
the songs, in stead of the whole window. Adding dnd supports breaks
almost everything that has anything to do with clicking a mouse button,
holding it and dragging while holing the mousebutton, in that window.

I just cannot understand what is wrong with using your Window Manager
for that, why does xmms reimplemented even the most basic functionality
of a Windowed GUI? No wonder iconfying xmms, while the playlist is
visible, is broken on GNOME 2.0 desktops.

While looking at beepmp's code, it looks like they are doing pretty much
the same and are even reusing the code of xmms for the GUI part. 

IMHO building a new GUI from scratch is a way better way to go. It
cannot be that hard to make a skinnable GUI using standard toolkits like
Gtk+ 2.0 :-\. Xmms is Gtk+ the way you should NOT code Gtk+ stuff,
breaking everything. It does not even make sense to me why they did not
use plain xlib ... or maybe even rewrite xlib too and talk the the
xserver using your own sockets, just for playing mp3s, bleh.

It even has a function to check whether or not a position is inside such
a custom Widget: 

int inside_widget(gint x, gint y, void *p)

Thats like: We have X to do that for us, no?

I mean, is this how you code a on-button-clicked?

void on-entire-window-clicked (..., event...)
{
    if (inside_widget (event->x, event->y, mybutton))
    {
	on-mybutton-clicked ();
    }
}

void on-mybutton-clicked () {
}


Of course ... I did not look at the code long enough to make a good
conclusion about it. But it's not easy to understand any of it, thats
for sure.



> On Sun, 2004-02-08 at 13:00, [email protected] wrote:
> > Send xmms-devel mailing list submissions to
> > 	[email protected]
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	http://lists.xmms.org/mailman/listinfo/xmms-devel
> > or, via email, send a message with subject or body 'help' to
> > 	[email protected]
> > 
> > You can reach the person managing the list at
> > 	[email protected]
> > 
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of xmms-devel digest..."
> > 
> > 
> > Today's Topics:
> > 
> >    1. 	/dev/null? (was: Re: xmms-devel Digest, Vol 4, Issue 4)
> >       (Matthew Rubenstein)
> > 
> > 

-- 
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
work: Philip dot VanHoof at cronos dot be
http://www.freax.be, http://www.freax.eu.org