Kobby GSoC: Connections and Browsing support
Its been a couple weeks since I last blogged about Kobby, and much has happened since then. In my last post I was having issues implementing a Qt socket event plugin for libinfinity, but thanks to some advice from Armin Burgmeier I was able to get this working very quickly. Since then, I have created and then added some features to the Connection Manager for Kobby to make it a little more user friendly (see below)
After getting this worked out I started on the next big step, browsing support in libinfinitymm, which not only includes traversing the directory tree of the Infinote server, but also creating and removing nodes. While looking through the infinote repository I noticed an awesome test application which creates a sort of interactive shell with the server using the client library, so I decided a great way to go about testing my C++ bindings for the Client Browser portion of libinfinity would be to replicate this test, which I just completed this afternoon. Hopefully, I will be able to implement a GUI for this by monday (meaning more screenshots) now that all the backend issues seem to be out of the way.
Comments
I’m really looking forward to kobby - I only now Gobby, and that’s more a proof-of-concept than a real editor solution.
As soon as you need testers, just tell me, I could test while being at work.
But did I get i right that Kobby would be compatibl to Gobby, usind the same type of server?
Has the text editing itself worked for a while I suppose?
Libinfinity provides a set of callbacks to connect the editing component (an insert/remove text function, among a couple others), so connecting it to the editor is pretty trivial. I haven’t been able to test it graphically until documents can be added/removed but it seems to function under the hood.
Also, in response to liquidat, Kobby not only uses the some protocol as Gobby (infinote), but also the same library (libinfinity), so there *shouldnt* be any compatibility issues.
Write a Comment