Confg and/or scheduling subsystems (crontab, at) and the desktop
avibrazil at gmail.com
Fri Jul 23 23:50:18 EEST 2004
Linux (not only Linux) Registry is also an option for a backend.
The community has grown and there is also available Python and Ruby
bindings, QT GUI for editing, etc.
Check it out at http://registry.sf.net/
On Fri, 23 Jul 2004 14:34:08 +0200, C. Gatzemeier <c.gatzemeier at tu-bs.de> wrote:
> Am Thursday 22 July 2004 20:55 schrieb Avery Pennarun:
> > Shameless plug: you could use UniConf for this by creating a special
> > "crontab" backend, and then even access it via gconf if you wanted.
> Tried to get an idea of what it does. Looks quite cool from first impression.
> I am not sure weather UniConf assumes to be in "authoritative control" of
> config files. From the Note that it can't handle commments, it would seem it
> works in a rather intrusive way.
> You wrote you found it has similarity to ACAP. ACAP was also brought up here
> in the past thread on a unifying configuration API. Nobody seemed to know
> about UniConf though. Did you come accross Config4GNU (CFG)? There sure seems
> to be a lot of overlap here too. One interesting thing I have not found yet
> in UniConf seems to be separating syntax/semantic handling (syntax parsers/
> sematic description files (config meta data)). This allows easier
> maintainablilty by keeping the description files synced within the app's
> cvs/packages, and not requreing recompilation on each update.
> Also there is support to include meta-data that helps frontends to dynamically
> create the (G)UIs. Much like it is envisioned by the proposed scheduling
> subsystem, too.
> I'd love to hear how you think they compare.
More information about the xdg