On Monday 07 September 2009, Jon A. Cruz wrote: > On Sep 7, 2009, at 10:11 AM, Marco Martin wrote: > > At the moment, (should make it more clear in the spec) is ARGB and > > is not > > designed to be network transparent, so the endian should be the same > > of the > > machine for both the client and the server > > I'd say this point was a HUGE red flag. > > For commercial app development (and here at home too) I've had to > support remote X11 between different architectures. Especially since > Mac's are officially UNIX(tm) one does not even have to install Linux > on a mac to take advantage of this (although I often do). right now when the dbus spec is not supported (i.e. local instances of NotificationItemWatcher and NotificationHost aren't on the bus) it falls back to the xembed based systray, and is what happens also when using remote displays, given that on the remote machine doesn't run a full blown workspace.
now i'm not sure about the current status of the tcp transport of dbus, but once it works i don't see particular problems, big endian machines would have to invert the bytes of the image by hand, that is something that somebody will inevitably have to do in a mixed environment. i think it's possible to avoid an extra field for that anyways -- Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
