[Armory-devel] responsibilities; client plugin structure

[darrik m. <da...@my...>]

Hello list.

I have a few questions regarding the planning of this project as it stands.

First and foremost, until we have something concrete in cvs, is it
possible to post a list of who's working on what, so we aren't
overlapping and responsibilities are clear?  Or if someone started a
responsibilities thread on the forum, and everyone posted with what they
were working on, that would work too.  ;)

Another question comes from Bico's description on the forum (see the
post "Plugins Development" :
http://sourceforge.net/forum/forum.php?thread_id=1751978&forum_id=689813),
the client will have a few built-in functions (disk usage, cpu, memory,
etc) and then rely on plugins for any other functionality.  My thought
was that it makes more sense to develop the client to simply load
whatever plugins and execute them, rather than mixing built-ins and
plugins.  We could write the client as just a plugin framework, and then
write the disk usage, cpu, and memory plugins.  This seems like the
cleanest method to me, and I wasn't sure if I just misunderstood the
post and this was what Bico had in mind.  This gives the obvious
advantage of not having to have two different systems for the client.
It's only function would be to load its plugins, and the plugins could
do the rest.  This would make upgrading the "builtin" functionality of
disk usage and whatnot a lot easier.


These are my thoughts.

~Darrik