> > I like the HAL idea alot, but i don't know if HAL reacts to eg a > > bluetooth device connecting to the PC > > There is a project underway somewhere to take care of that. "Not yet" > would be the response. >
Good, this was one of the "problem" areas I had thought of. Quick aside, anyone tried a WM5 bluetooth connection in the current framework ? How does it work. > > > Have been in talks with Ubuntu (wrt Conduit and sync that "just works" > > > - you plug it in and it says "where sync to.. k thx bye") and its > > > likely that we'll see some support into pulling the latest and > > > greatest into the next release (probably more in terms of acceptance > > > rather than actual man hours)... > > > > I wrote that initial draft, conduit seems like an excellent 'glue' to > > tie synce and eg gnokii together. > > Tis great to here acceptance (wrt conduit). Its taken a lot to get so > far, and some peoples attitudes just make you want to give in. > > > > There is no "modern" way to sync 2003 devices. You seem to have to use > > > ancient programs like a pre-opensync version of multisync. About 1 in > > > 5 #synce requests is WM2003 related... That was a guess. Enough for it > > > to bother me that we don't offer support any more :P Interesting, obviously I dont hang out on #synce, not nearly enough time, but are these generally connection or sync based problems ? Again, I would guess half the problems are due to having too many options with with up to date guidance rather than being real bugs, but I'm guessing. > > > > You want to drop WM2003? > > Hope my reply got through! No, my desire was that jagow might be able > to resurrect the RRA stuff inside sync-engine. > Go jagow ! > > > I presume vdcccm won't support WM6? It also doesn't work with > > > sync-engine. Unfortunately dropping it hurts KDE users, who often ask > > > about RAKI. I have no idea what exactly that is, but seems not to work > > > with odccm. Yet. I am strongly in favor of having just one *dccm. > > > Either RAKI support in odccm or another standalone proggy, or vdccm > > > needs to be extended for WM6 and needs to be made to work with > > > sync-engine? > > vdccm with WM6, don't know, but would guess it works fine. vdccm with sync-engine, don't know, have a pre WM5 device, go jagow ! Sorry John, no pressure :) Raki support in odccm is not going to happen, it would be messy. odccm support in Raki however, is very simple for anyone who can do dbus in C ++, if anyone can please step up, I'll tell you exactly what needs to be done. I can do dbus but not C++. This will also be the case with hal-dccm. An alternative is a fake vdccm on top of odccm/hal-dccm, I can do this when I clone myself :) > > vdccm also works with the ancient multisync for wm2003 devices > wm2003 multisync works with any *dccm. Anything that uses pure rapi calls should. > With the work that jagow and mark are doing that won't matter - we can > have a nice working and modern opensync/sync-engine/odccm. Really > don't want to have to figure out and document years old releases of > things :-) > Could be fun, people could read it to respond "you used to have to do what !!!!" :) Mark ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
