Hi Steve,
You actually read the TODO!? :shock: :lol:
I confirm I stopped developing adesklets, since it now does
pretty much what I wanted it to do in the first place. This
said, I am still actively maintaining it (adesklets 0.4.9
should be out in about a week by the way) solving remaining
portability issues and similar. The package is slowing
getting more recognition (for instance, it has just been
included in FreeBSD's port collection), and you can be
ensured it will not disappear any time soon. Of course, I
also still process desklets submission as they are sent to
me.
I haven't received a single new desklet in more than a month
now, and I suspect the main reason being that I informed all
current or potential desklet writers that I was developing
the "successor" to adesklets (not a fork nor a rewrite, but a
different package with similar objectives)... But I do not
think it is the right time to discuss it in the open yet: I
will contact you privately in case you are interested by
development issues...
(like why the config file is in the script itself)
Well, it is not. Default configuration is defined in the
script itself, but individual per-instance configurations
parameters are kept in an external, dynamically created file,
usually called
config.txt
and stored in the base directory of the desklet.