On Friday 21 December 2007 17:55:37 Mark Ellis wrote: > > Yes, they all operate through a rapi connection which can do either > dccm. > > > Raki does not work with odccm, but currently I am working on a program > > that will do most of the functions that raki did, except for one thing: > > the syncing, since that was done in rra. It is already in trunk, under > > synce-kdm (SynCE KDE Device Manager) and is written in Python with the > > PyQT bindings. > > I guessed that was what you were up to, though I hadn't got around to > looking at it properly, excellent, good luck ! Mine was only a stopgap > measure, personally I'm not actually bothered since I'm a gnomer, but it > seemed a shame to cut raki loose entirely.
I am really trying to get this working, since I use KDE. Fortunately I do a lot of things console based, but still it is nice to have some things done in the GUI also :) And since everybody else was using gnome, I decided to work on a successor of raki :) > > > The current program is wm5+ only, since I make use of provisioning for > > example to uninstall programs, while in pre wm5 devices you need to make > > use of the program unload.exe. The version of the device could be > > determined run time and appropriate actions could be taken for that part. > > > > A very initial version is already available and the screenshots can be > > found on my homepage ( http://www.guidodiepen.nl/ ). > > > > > odccm uses dbus, vdccm uses a control socket in ~/.synce called csock. > > > Personally I think dbus is the way to go (and later hal). The crunch is > > > then that raki in synce-kde doesn't work. > > > > The only thing that my synce-kdm does not provide, in contrast to raki is > > the syncing. IIRC jagow was busy with trying to get support for legacy > > device syncing in the sync-engine also (correct me if am wrong). That way > > the syncing part could be completely decoupled from raki and we can work > > on a version based on dbus and qt4 (i.e. work further on SynCE-KDM :) ) > > > > > > One part of synce-kde does work btw, which is the rapip kio slave: it is > > very useful for copying files back-and-forth. > > I would suggest at some point then that we decouple rapip and raki. This is definitely what I would like to suggest. Because rapip really works regardless of RAKI and imho it is a very very useful program. Since more and more people will get wm5+ devices, I think it would be nice for them to have the abilitiy to install this separately. > > > > I did try and jam dbus into raki, but I don't know much C++, I'm not a > > > kde/qt developer, synce-kde uses the previous release of qt (I think) > > > and, while dbus support for that version exists, it appears to be > > > completely undocumented. Sigh. > > > > I am working with PyQT4, which is quite clear I have to say (considering > > the fact that I started this week with python and GUI programming :) ) > > I started to fiddle with dbus in raki using qt4 before I realised it was > qt3, very silly of me. I have to say even the qt4 C++ documentation was > poor, just badly written, so I hope the python stuff is more > straightforward. I have to say that the qt4 documentation is quite nice, the examples for pyqt4 are not that ample, but qt4 c++ examples can be transformed quite easly into python code (at least the majority of the cases for me so far). Furthermore, got myself a nice book about python and qt4 :) > > > > Plan 2, a fake vdccm that translates from odccm to raki (or anything > > > else dependent on vdccm style) and vice-versa. > > > > > > I've checked it into trunk as o-vdccm, it'll build a single binary > > > called vdccm. Seems to work ok, even passwords work. > > > > I have not implemented the password thingy, though I can copy the > > relevant part out of the synce-gnome/test.py program for that. So it > > should not be very difficult to implement that in my current program. > > The password part is quite easy, just remember to back up your test > device, in case you lock yourself out ! Yes I did do this once...... Hmm... I will put this as a small todo then for later, first I want to work on potentially less harmfull stuff :) Before I work on the password thing I want to work on the possibility of installing cab files through synce-kdm. For this I have to implement some functions in pyrapi though and I want to add the possibility of copying the cab files through rapi first to a possible different location ( useful for large programs, like spoken dictionaries). I will need the CeGetDiskFreeSpaceEx function to be implemented in rapi. I already gave it a try to implement it, but I am not sure if it is working, since the last-error is equal to 1, which is not a good thing I think. More investigation into this is needed. One of the people on IRC already offered to help me out by providing me some traces of an installer program under windows that uses rapi. As soon as I have those logs I will work on implementing that functionality. If people have suggestions for features, please let me know :) Guido Diepen Guido Diepen -- Aviation is proof that given the will, we have the capacity to achieve the impossible. --Eddie Rickenbacker ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
