Re: Plugins to Block in the Core in 0.7

It's not the devs that have to be notified. 
The end user should be notified about a plugin that is no longer compatible with the new version. 
Yes this is an open source project, I understand , 
and it's being developed by developers for developers.

But I think that the upcoming release 0.7 , finally makes it friendly enough for the rest of the human
population. We shoudl start thinking of the semi techie users.
My sugestion would be to add this functionality to the load screen plugin .. or just send a popup message that
"Plugin so and so is not supported in current version".
I think that woud be perfectly sufficient. 

----- Original Message ----
From: Dragos Dumitrescu/Drugwash <drugwash@...>
To: miranda-develop@...
Sent: Thursday, August 2, 2007 6:10:28 PM
Subject: Re: [Miranda-Develop] Plugins to Block in the Core in 0.7

Robert Rainwater wrote:

> Hi,
> 
> Thursday, August 2, 2007, 5:28:43 PM, you wrote:
> > Robert Rainwater wrote:
> 
> >> Hi,
> >> 
> >> Thursday, August 2, 2007, 2:55:58 PM, you wrote:
> >> > I just hope there will be a notification, like: "These plugins:
> >> > [list of plugins] has been blocked. They are not compatible with
> >> > this version of Miranda. Please update those plugins at
> >> > http://addons.miranda-im.org.";...
> >> 
> >> 
> >> The release notes on the site will mention the plugin
> >> incompatibilities.  I don't plan on adding a UI to the plugin
> loader >> in the core however.
> 
> 
> > How many people read the main page or whatever remotely related to
> > it?  It'll be ugly. Better try to notify the plug-in developers
> > about the changes, somehow, and allow them some time to fix
> > whatever needs fixed, while - if necessary - add a message box to
> > the core. Otherwise the forums will be flooded with "I just updated
> > to xxxx and this and that doesn't work anymore". You know people
> > don't read announcements, they just upgrade.
> 
> Actually, the plugins being blocked have compatible plugins in 0.7.
> So for instance, if a user has icolib or fontservice installed, the
> fact that it will not be loaded anymore is of no consequence.  The
> other plugins are clist and message plugins.  Since 0.7 ships with a
> compatible plugins, the users are not left with an install that
> doesn't work.  The most popular plugins, scriver and tabsrmm will
> have to be updated in order for them to load, and this will be noted
> on the download page.

That is perfectly reasonable. As long as there is a built-in or in-pack
replacement, it's the best decision to take.

But regarding mToolTip or other similar third-party plug-ins - as
suggested earlier - it's best to just warn the devs about the issue and
let them update their products.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Miranda-Develop mailing list
Miranda-Develop@...
https://lists.sourceforge.net/lists/listinfo/miranda-develop

      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user panel and lay it on us.
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/