From: Marcel H. <ma...@ho...> - 2006-10-20 14:26:04
|
Hi Alex, > > The bluetooth API documentation for darwin can be found here: > > http://developer.apple.com/documentation/DeviceDrivers/Reference/IOBluetooth/index.html > > > > Darwin's OBEX is at the same place... > > Well, there is simply no demand, since Darwin already provides OBEX > API :) I think that rather than making openobex work perfect on all > architectures we should concentrate our efforts on high-level user > applications. As you probably know Gnome's OBEX support is almost > non-existent, and there is no support for USB OBEX in KDE either. Work > on syncml is ongoing in opensync but is far from being complete. the GNOME integration should be based on the OpenOBEX GLib bindings that are already included in an experimental state. Regards Marcel |
From: Alex K. <ak...@se...> - 2006-10-20 14:41:16
|
2006/10/20, Marcel Holtmann <ma...@ho...>: > the GNOME integration should be based on the OpenOBEX GLib bindings that > are already included in an experimental state. A Gnome-vfs module based on the bindings is probably the best way for Bluetooth (more information at http://blogs.gnome.org/view/jamesh/2006/10/05/0 ), but for USB I plan to use Fuse/ObexFS/ObexFTP - should solve the problem anywhere, not just in GNOME. -- Alexander |
From: Hendrik S. <sat...@gm...> - 2006-10-20 14:53:38
|
Am Freitag 20 Oktober 2006 15:45 schrieb Alex Kanavin: > 2006/10/20, Hendrik Sattler <sat...@gm...>: > > The bluetooth API documentation for darwin can be found here: > > http://developer.apple.com/documentation/DeviceDrivers/Reference/IOBlueto > >oth/index.html > > > > Darwin's OBEX is at the same place... > > Well, there is simply no demand, since Darwin already provides OBEX > API :) I think that rather than making openobex work perfect on all > architectures we should concentrate our efforts on high-level user > applications I do but I rather have a common framework and not reinvent the whole wheel for every desktop out there because after you go Gnome and KDE, you still have Xfce users in the cold. I am not a GUI programmer (I can do that but I do not really like it). > As you probably know Gnome's OBEX support is almost > non-existent, and there is no support for USB OBEX in KDE either.yncM As it is called kdebluetooth, they stay away from all other technics :-( And its not really maintained, either. Upstream's gone for a looooong lunch, it seems. It needs a bit of rewrite, maybe QT4 bindings would help. With bluez3, there is also _no_ passkey agent for KDE, so kdebluetooth is not self-contained anymore. There are more problems than a neat desktop integration. > Work on syncml is ongoing in opensync but is far from being complete. SyncML is not really related to OBEX, is it? HS |
From: Manuel N. <nar...@gm...> - 2006-10-20 14:58:32
|
> I do but I rather have a common framework and not reinvent the whole wheel for > every desktop out there because after you go Gnome and KDE, you still have > Xfce users in the cold. > I am not a GUI programmer (I can do that but I do not really like it). > What about using Java with SWT or QTJambi, the first is a way to program GTK apps with Java and the second uses QT libs. Let me know what you think about this. |
From: Alex K. <ak...@se...> - 2006-10-20 15:32:33
|
2006/10/20, Hendrik Sattler <sat...@gm...>: > I do but I rather have a common framework and not reinvent the whole wheel for > every desktop out there because after you go Gnome and KDE, you still have > Xfce users in the cold. > I am not a GUI programmer (I can do that but I do not really like it). Like I said, I'll see what I can do with obexfs in Fedora. My approach is to have USB Obex work the same way USB flash drives and digital cameras work - you plug your gadget in, you get a nice icon on the desktop, regardless of which desktop you use. > > Work on syncml is ongoing in opensync but is far from being complete. > > SyncML is not really related to OBEX, is it? It is directly related :) SyncML is an application protocol and it can use either HTTP or OBEX as session protocols. HTTP is typically used over TCP links and OBEX over Bluetooth or USB links (e.g. Nokia phones). See: http://libsyncml.opensync.org/wiki/obex-guide -- Alexander |
From: Hendrik S. <sat...@gm...> - 2006-10-20 14:56:09
|
Am Freitag 20 Oktober 2006 16:20 schrieb Marcel Holtmann: > > > The bluetooth API documentation for darwin can be found here: > > > http://developer.apple.com/documentation/DeviceDrivers/Reference/IOBlue > > >tooth/index.html > > > > > > Darwin's OBEX is at the same place... > > > > Well, there is simply no demand, since Darwin already provides OBEX > > API :) I think that rather than making openobex work perfect on all > > architectures we should concentrate our efforts on high-level user > > applications. As you probably know Gnome's OBEX support is almost > > non-existent, and there is no support for USB OBEX in KDE either. Work > > on syncml is ongoing in opensync but is far from being complete. > > the GNOME integration should be based on the OpenOBEX GLib bindings that > are already included in an experimental state. Is the API/ABI already stable on this one? Are you planning other bindings? Maybe QT4? HS |
From: Marcel H. <ma...@ho...> - 2006-10-20 15:07:46
|
Hi Hendrik, > > the GNOME integration should be based on the OpenOBEX GLib bindings that > > are already included in an experimental state. > > Is the API/ABI already stable on this one? Are you planning other bindings? > Maybe QT4? the API is not stable and will be earliest with the 1.5 release. Other bindings are find with me, but I am not gonna write them. And non C based bindings should maybe not be included. The should be a separate source package. Regards Marcel |