 |
The birds lake is a framework for the creation of
distributed wordprocessors
| LsmLib | |
LsmLib is a C library that provides
transparency of files and
directories over the networks.
If the files are local, a lsmtree stores only
the meta informations of the files, if not
the files are serialized.
|
|
| LibIGen | |
LibIGen is a C libraries that enables to
handle easily and over the network with
GUIs. It creates a GUI using different
platform (GTK/GNOME, QT/KDE, Win32) enabling
to be fully integrated with the client
(There are no look and feels mismatch between
the client and the dialogs created by LibIGen,
(but for yet only the GTK backend has been
created)
|
|
| Lioubliou | |
The facade to the filters server. Offers a CORBA interface.
Connecting using a login and password. Delegates the real filter
work to the Lioubovnik. But the Lioubovnik has not to work with
the complexity of CORBA. Lioubliou may also provide standart implementation
for the Lioubovnik function in order to avoid code replication.
| LioubovnikGuile | |
Guile is the GNU official extension langage. We have some prototypes for
such a lioubovnik.
| Ports | |
The ports is the hierarchy of filters / interfaces /
addon libraries / scheme files to include / ressources
(pixmaps, etc...).
It is dependant of the wordprocessor. We have some prototypes
for ports with a Guile Lioubovnik.
| PortsIntrospector | |
The ports are hard to maintain. We need a program that checks
dependancies between include files / interfaces / ... and
generates comprehensive documentations. We have a prototype
of such program written in Python.
|
|
|
|
|
|
| LioubovnikPython | |
Guile (Scheme) is too hard for too much people
|
|
| LioubovnikSimple | |
Creating an efficient Lioubovnik is not easy.
But for testing Lioubliou we need a Lioubovnik that
is simple enough for being trustful. LioubovnikSimple
exists only for proving the viability of Lioubliou and to
get the maximum of points for my TER.
|
|
|
|
| Jentchina | |
The client facade. Jentchina is responsible of contacting the filters server,
asking him the list of filters, showing this list to the user with a GUI.
This GUI must be multi platform (GTK / QT / Win32), so we need to design
it in consequence. When a user clicks on a filter, Jentchina is asking
the server for more informations about it. When the user is confirming his choice
of filter, Jentchina is opening a filter session, it pushes the document and ask
the server what interfaces he needs for such a document and with such filter.
Jentchina is asking the server the interface that he had not cached before
(Jentchina maintains one cache per user). Jentchina is showing the interfaces to the
user. The user fills them and confirms or cancels. Jentchina sends the filled
interfaces. The server is doing its job. Jentchina asks the exported document.
| Patches | |
The aim of the patches is to propose the birds lake to existing
wordprocessors
|
|
| <Simple Client> | |
Like LioubovnikSimple, we need to prove that the client side works.
|
|
| <Full Featured Client> | |
To reveal the powerfullness of the birds lake, we need a client especially
designed for it.
|
|
|
|
|
