2011-07-10, 09:18 AM
Ommina Wrote:it's an idea that I like in principalI agree.
Ommina Wrote:First, I'm in agreement with mvallevand's opinion of putting executable code outside in the Documents / Users tree. It feels icky. It's just not a home for DLLs.But not on this point. I understand your reluctance over it, but one of goals with Vista/Win7 (and partly UAC) was to make things a bit more like Unix and allow non-administrative users to be able to install programs that don't require admin rights. Therefore the only place these programs can go is outside of Program Files, because the user would need admin rights to put them there. Part of the historical problem with doing this is because programs insisted on writing to what should have been protected areas. Executable code is just executable code; it doesn't matter where it goes, what matters is who gets to run it.
Ommina Wrote:...each of them require some level of config work after installation. As such, any sort of "install with the click of a remote" advantage is (for me) immediately lost anyway. And with that advantage lost, why bother going to the effort in the first place?Again, I agree. But even being able to browse/download/install from within the Settings dialog would be better than the current situation.
Personally - and so far - all of my plugins (both released and in progress) can exist happily in their own plugin and skin subdirectories. One or two of them rely on 3rd party DLLs that can be safely bundled in the plugin directory with them. I always try to ensure that any config settings for them have usable defaults so they can be run with no configuration too. So in my case, a plugin manager that could do nothing more than automatically download and extract the files would be enough.
I know others have more complicated requirements though, but surely nothing we couldn't solve together as a community. If any of us could find the time
Iain