[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC libquran: Architecture
- To: "Development Discussions" <developer at arabeyes dot org>
- Subject: RFC libquran: Architecture
- From: "Mohammad DAMT" <mdamt at gnome dot org>
- Date: Thu, 26 Jul 2007 18:03:23 +0300
The libquran architecture is meant to be simple and clear.
*Audio Plugin System*
The libquran only provides abstract APIs for handling the audio. The
plugin management is needed to handle multiple formats of audio
encoding. The audio data files are actualy read by audio plugins.
The advantage of having a plugin based system over a statically
compiled system is that if a vendor wants to provide an audio package
which can't be handled by the standard libquran, the vendor can just
provide the audio package and the plugin. If the library is statically
compiled, the vendor have to also provide their version of libquran
which is discouraged.
*Dependencies*
The libquran only depends on libc and sqlite. During building it
requires autotools, libtool and pkgconfig.
*License*
The libquran will be released with GNU LGPL version 2.1 only.
Interested vendors can supply the plugins with whatever license they
want.
The original text of Quran is released with a license which permits
everybody to copy and distribute, but not free to modify. All errors
found shall be reported to the Arabeyes.org bug reporting tool.