Tag Archives: architecture

Back to Work: libsoylent Foundation

Moving to the new flat took longer than expected. But I think the extra time was worth it. The whole flat and my room look pretty nice and comfortable now. Most things are organized, only for the party on friday there is some planing left to do ;) . Internet is still an issue after two weeks of having (almost) no internet-access. Currently we are using the neighbours WLAN until our ISP is done with installing the new connection.

The Southside festival was great too. Radiohead and Sigur Ros, yeah! Tegan and Sara were also amazing. Looking back I would say it was one of the best music festivals I’ve been to so far.

Nevertheless, being away for two weeks kept me slightly behind my schedule. Version 0.1 is ready but not released, because of organizational reasons. In the meantime I’m already working on v0.2.

Last week I finished the foundation of libsoylent. That basically means I thought in greater detail of the architecture (see below), designed the needed GObject classes and made stubs for most functions and methods. From now on there should be a release every week, and a solid foundation will help a lot.

libsoylent overview

The libsoylent architecture as shown in the diagram: SlBook is the addressbook where people (SlPerson) and groups (SlGroup) are stored. People and Groups are entities (i.e. objects with attributes that can be modified etc.). SlEntities are backed by SlEntityHandlers. For SlPerson there will be an EDS-handler and for SlGroup a file-handler. More handlers can easily be added (if needed).

The storage of attributes (SlAttribute) is managed by attribute-handlers (SlAttributeHandler). They are responsible to convert runtime-values to values that can be stored by the entity-handlers (e.g. a SlAddress C-struct to a VCard-string for EDS).

If you have any thoughts on the architecture I’d be glad to hear them. This week I will have more time and work on people, group and addressbook management. And of course on the first release :) .