Quantcast

Removing Nyquist plug-ins

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Removing Nyquist plug-ins

Stevethefiddle
Sorry if this has already been covered, but I've not had time to
closely follow all of the recent discussion about plug-in management.

I'm using Audacity 2.1.3 alpha (head) on Debian.

Scenario:
* I have a Nyquist plug-in installed, and I decide that I don't want
it now or ever.
* The plug-in .NY file is located in ~/.audacity-files/plug-ins/<filename>.ny
* The plug-in has been enabled in the Plug-in  Manager

I delete the NY file and restart Audacity.
The plug-in is (correctly) removed from the Audacity menu.

Open the Plug-in manager and look in the "Disabled" tab.
The plug-in (which no longer exists on the system) is listed as
"Disabled" and it appears that it can be enabled, though of course it
can't because it no longer exists.

At least the plug-in is removed from the Audacity menu, but the
Plug-in Manager should not list plug-ins as "disabled" when they don't
exist.

Steve

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

James Crook
> At least the plug-in is removed from the Audacity menu, but the
> Plug-in Manager should not list plug-ins as "disabled" when they don't
> exist.
Agreed.  But the previous unacceptable (to me) bug was that it was
listed in the menu and the list of plug-ins.

I am not considering this a blocker, nor that clicktrack.ny persists if
you don't delete it or pluginregistry.cfg.  Both ARE bugs though.

--James.


On 2/9/2017 2:19 PM, Steve the Fiddle wrote:

> Sorry if this has already been covered, but I've not had time to
> closely follow all of the recent discussion about plug-in management.
>
> I'm using Audacity 2.1.3 alpha (head) on Debian.
>
> Scenario:
> * I have a Nyquist plug-in installed, and I decide that I don't want
> it now or ever.
> * The plug-in .NY file is located in ~/.audacity-files/plug-ins/<filename>.ny
> * The plug-in has been enabled in the Plug-in  Manager
>
> I delete the NY file and restart Audacity.
> The plug-in is (correctly) removed from the Audacity menu.
>
> Open the Plug-in manager and look in the "Disabled" tab.
> The plug-in (which no longer exists on the system) is listed as
> "Disabled" and it appears that it can be enabled, though of course it
> can't because it no longer exists.
>
> At least the plug-in is removed from the Audacity menu, but the
> Plug-in Manager should not list plug-ins as "disabled" when they don't
> exist.
>
> Steve
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

Gale
Administrator
On 9 February 2017 at 14:30, James Crook <[hidden email]> wrote:
>> At least the plug-in is removed from the Audacity menu, but the
>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>> exist.
> Agreed.  But the previous unacceptable (to me) bug was that it was
> listed in the menu and the list of plug-ins.

I don't understand what you mean by "list of plug-ins", if not
Plug-in Manager, James.

> I am not considering this a blocker, nor that clicktrack.ny persists if
> you don't delete it or pluginregistry.cfg.  Both ARE bugs though.

The first one is
http://bugzilla.audacityteam.org/show_bug.cgi?id=1018 .

It's P4 but I think it is not now rated high enough.

It is a summary bug with issues bulleted in Steps to Reproduce.

If we wanted to increase bug count/churn we could pull out bullet
points as separate bugs. The highest rated separate bug determines
the rating of the summary bug.

I'll put the second (clicktrack.ny ) on Bugzilla if it is not already there.
Yes I can live with it in 2.1.3.


Gale






> On 2/9/2017 2:19 PM, Steve the Fiddle wrote:
>> Sorry if this has already been covered, but I've not had time to
>> closely follow all of the recent discussion about plug-in management.
>>
>> I'm using Audacity 2.1.3 alpha (head) on Debian.
>>
>> Scenario:
>> * I have a Nyquist plug-in installed, and I decide that I don't want
>> it now or ever.
>> * The plug-in .NY file is located in ~/.audacity-files/plug-ins/<filename>.ny
>> * The plug-in has been enabled in the Plug-in  Manager
>>
>> I delete the NY file and restart Audacity.
>> The plug-in is (correctly) removed from the Audacity menu.
>>
>> Open the Plug-in manager and look in the "Disabled" tab.
>> The plug-in (which no longer exists on the system) is listed as
>> "Disabled" and it appears that it can be enabled, though of course it
>> can't because it no longer exists.
>>
>> At least the plug-in is removed from the Audacity menu, but the
>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>> exist.
>>
>> Steve
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

James Crook
On 2/9/2017 7:02 PM, Gale Andrews wrote:
> On 9 February 2017 at 14:30, James Crook <[hidden email]> wrote:
>>> At least the plug-in is removed from the Audacity menu, but the
>>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>>> exist.
>> Agreed.  But the previous unacceptable (to me) bug was that it was
>> listed in the menu and the list of plug-ins.
> I don't understand what you mean by "list of plug-ins", if not
> Plug-in Manager, James.
I mean the list of plug-ins shown in the Plug-in manager.

>
>> I am not considering this a blocker, nor that clicktrack.ny persists if
>> you don't delete it or pluginregistry.cfg.  Both ARE bugs though.
> The first one is
>   .
>
> It's P4 but I think it is not now rated high enough.
>
> It is a summary bug with issues bulleted in Steps to Reproduce.
>
> If we wanted to increase bug count/churn we could pull out bullet
> points as separate bugs. The highest rated separate bug determines
> the rating of the summary bug.
If you want to increase bug count/churn, then go ahead.
I suppose if someone decides to address a part of 1018 but not the whole
thing, it could make sense for them to 'pull out' a bug at that point
anyway.
1018 is an enhancement bug, so there will likely be discussion about
what we want behaviour of plug-in-manager to be.


> I'll put the second (clicktrack.ny ) on Bugzilla if it is not already there.
> Yes I can live with it in 2.1.3.
Good.

--James.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

Stevethefiddle
I think it would be worth pulling out those parts that are "bugs"
rather than "enh" into separate issues. Fixing a "bug" is likely to be
less contentious (require less discussion), and possibly more serious
than an enh, and it would be good if we could clear the worst parts
sooner rather than later. I'm thinking particularly of the Plug-in
Manager listing non-existent plug-ins.

Steve

On 9 February 2017 at 19:20, James Crook <[hidden email]> wrote:

> On 2/9/2017 7:02 PM, Gale Andrews wrote:
>> On 9 February 2017 at 14:30, James Crook <[hidden email]> wrote:
>>>> At least the plug-in is removed from the Audacity menu, but the
>>>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>>>> exist.
>>> Agreed.  But the previous unacceptable (to me) bug was that it was
>>> listed in the menu and the list of plug-ins.
>> I don't understand what you mean by "list of plug-ins", if not
>> Plug-in Manager, James.
> I mean the list of plug-ins shown in the Plug-in manager.
>
>>
>>> I am not considering this a blocker, nor that clicktrack.ny persists if
>>> you don't delete it or pluginregistry.cfg.  Both ARE bugs though.
>> The first one is
>>   .
>>
>> It's P4 but I think it is not now rated high enough.
>>
>> It is a summary bug with issues bulleted in Steps to Reproduce.
>>
>> If we wanted to increase bug count/churn we could pull out bullet
>> points as separate bugs. The highest rated separate bug determines
>> the rating of the summary bug.
> If you want to increase bug count/churn, then go ahead.
> I suppose if someone decides to address a part of 1018 but not the whole
> thing, it could make sense for them to 'pull out' a bug at that point
> anyway.
> 1018 is an enhancement bug, so there will likely be discussion about
> what we want behaviour of plug-in-manager to be.
>
>
>> I'll put the second (clicktrack.ny ) on Bugzilla if it is not already there.
>> Yes I can live with it in 2.1.3.
> Good.
>
> --James.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

Gale
Administrator
On 9 February 2017 at 20:13, Steve the Fiddle <[hidden email]> wrote:
> I think it would be worth pulling out those parts that are "bugs"
> rather than "enh" into separate issues. Fixing a "bug" is likely to be
> less contentious (require less discussion), and possibly more serious
> than an enh, and it would be good if we could clear the worst parts
> sooner rather than later. I'm thinking particularly of the Plug-in
> Manager listing non-existent plug-ins.

Even the bugs might be contentious. I think we might list a
missing plugin in Plug-In Manager as long we say it's missing,
and as long as we have a way to deregister any plugin in Plug-in
Manager.

I know some think I want too much information and control and I
know the Manager dialogue must remain usable.

I think our decision also depends on how we fix the remaining
non-existent plugin ghosts for all types except nyquist.



Gale


> On 9 February 2017 at 19:20, James Crook <[hidden email]> wrote:
>> On 2/9/2017 7:02 PM, Gale Andrews wrote:
>>> On 9 February 2017 at 14:30, James Crook <[hidden email]> wrote:
>>>>> At least the plug-in is removed from the Audacity menu, but the
>>>>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>>>>> exist.
>>>> Agreed.  But the previous unacceptable (to me) bug was that it was
>>>> listed in the menu and the list of plug-ins.
>>> I don't understand what you mean by "list of plug-ins", if not
>>> Plug-in Manager, James.
>> I mean the list of plug-ins shown in the Plug-in manager.
>>
>>>
>>>> I am not considering this a blocker, nor that clicktrack.ny persists if
>>>> you don't delete it or pluginregistry.cfg.  Both ARE bugs though.
>>> The first one is
>>>   .
>>>
>>> It's P4 but I think it is not now rated high enough.
>>>
>>> It is a summary bug with issues bulleted in Steps to Reproduce.
>>>
>>> If we wanted to increase bug count/churn we could pull out bullet
>>> points as separate bugs. The highest rated separate bug determines
>>> the rating of the summary bug.
>> If you want to increase bug count/churn, then go ahead.
>> I suppose if someone decides to address a part of 1018 but not the whole
>> thing, it could make sense for them to 'pull out' a bug at that point
>> anyway.
>> 1018 is an enhancement bug, so there will likely be discussion about
>> what we want behaviour of plug-in-manager to be.
>>
>>
>>> I'll put the second (clicktrack.ny ) on Bugzilla if it is not already there.
>>> Yes I can live with it in 2.1.3.
>> Good.
>>
>> --James.
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Audacity-quality mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/audacity-quality

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Removing Nyquist plug-ins

Stevethefiddle
On 9 February 2017 at 21:44, Gale Andrews <[hidden email]> wrote:

> On 9 February 2017 at 20:13, Steve the Fiddle <[hidden email]> wrote:
>> I think it would be worth pulling out those parts that are "bugs"
>> rather than "enh" into separate issues. Fixing a "bug" is likely to be
>> less contentious (require less discussion), and possibly more serious
>> than an enh, and it would be good if we could clear the worst parts
>> sooner rather than later. I'm thinking particularly of the Plug-in
>> Manager listing non-existent plug-ins.
>
> Even the bugs might be contentious. I think we might list a
> missing plugin in Plug-In Manager as long we say it's missing,
> and as long as we have a way to deregister any plugin in Plug-in
> Manager.
>
> I know some think I want too much information and control and I
> know the Manager dialogue must remain usable.

Yes, that's exactly my point. There are many ways that we can have an
enhanced fixed, but there is a fundamental "bug" which is that the
Plug-in Manager should not list plug-ins as "Disabled" when they don't
exist. That fundamental bug is not in dispute.

We have a policy of "doer decides", and whoever fixes the bug is the "doer".
If there are "residuals" or further "enhancements" that need to be
addressed, then they can either be rolled back into the 1018
"summary", or moved into a new (lesser) enh issue.

"Summary" bugs may be useful for tracking issues, but they are very
unattractive for developers that are looking for something to fix.

Steve

>
> I think our decision also depends on how we fix the remaining
> non-existent plugin ghosts for all types except nyquist.
>
>
>
> Gale
>
>
>> On 9 February 2017 at 19:20, James Crook <[hidden email]> wrote:
>>> On 2/9/2017 7:02 PM, Gale Andrews wrote:
>>>> On 9 February 2017 at 14:30, James Crook <[hidden email]> wrote:
>>>>>> At least the plug-in is removed from the Audacity menu, but the
>>>>>> Plug-in Manager should not list plug-ins as "disabled" when they don't
>>>>>> exist.
>>>>> Agreed.  But the previous unacceptable (to me) bug was that it was
>>>>> listed in the menu and the list of plug-ins.
>>>> I don't understand what you mean by "list of plug-ins", if not
>>>> Plug-in Manager, James.
>>> I mean the list of plug-ins shown in the Plug-in manager.
>>>
>>>>
>>>>> I am not considering this a blocker, nor that clicktrack.ny persists if
>>>>> you don't delete it or pluginregistry.cfg.  Both ARE bugs though.
>>>> The first one is
>>>>   .
>>>>
>>>> It's P4 but I think it is not now rated high enough.
>>>>
>>>> It is a summary bug with issues bulleted in Steps to Reproduce.
>>>>
>>>> If we wanted to increase bug count/churn we could pull out bullet
>>>> points as separate bugs. The highest rated separate bug determines
>>>> the rating of the summary bug.
>>> If you want to increase bug count/churn, then go ahead.
>>> I suppose if someone decides to address a part of 1018 but not the whole
>>> thing, it could make sense for them to 'pull out' a bug at that point
>>> anyway.
>>> 1018 is an enhancement bug, so there will likely be discussion about
>>> what we want behaviour of plug-in-manager to be.
>>>
>>>
>>>> I'll put the second (clicktrack.ny ) on Bugzilla if it is not already there.
>>>> Yes I can live with it in 2.1.3.
>>> Good.
>>>
>>> --James.
>>>
>>>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Audacity-quality mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-quality
Loading...