Great job everybody on the 3.0.0 milestone and thanks to everyone involved!
I have the following feedback:
The Pade Meetings plugin inclusion in its current form needs to be completely rethought. In its current form this plugin adds 700+MB to a Windows user’s profile which is completely unacceptable for an organization that utilizes roaming profiles. The fat either needs to be substantially trimmed or the plugin moved somehow to the C:\Program Files directory so you’re not dragging 700MB for a plugin that may or may not be used across your network when you login or out.
You can’t currently remove or get rid of the Pade plugin. At all. If you delete the files manually Spark just re-downloads them upon next login. If you deactivate it via the plugin manager, and restart, it ignores your choice and upon next Spark startup, Pade is back re-activated. I’m sure this must be a bug.
The installer needs to offer a choice and ask the user if they want to use this or perhaps the Client Control plugin could be utilized for that (not sure at what point Pade is getting downloaded/installed vs. Client Control settings read by Spark). As it is, I can’t find any option anywhere in Spark that controls this behavior of automatically force downloading Pade and dependency libraries, even looking at the properties files. I guess I could try blocking the download at the firewall edge but I am unsure if that will hang Spark while it tries (in vain) to download the libraries.
I am a fan of Pade Meetings but the current implementation in 3.0.0 Beta is…not well thought out for an organization.