Re: [ jEdit-devel ] action namespaces

[Dale A. <da...@gr...>]

One reason to override is that the user would not have to bind the
shortcuts/toolbar buttons to those actions. The binding would be
automatic. In the case of Navigator, which has been used as an example
a few times in this thread, the override is an option in Navigator, so
the user has to explicitly choose to override the action. There are
other apps based on jEdit that do extensive customizations and having
the ability to override core actions is essential to those apps.

Dale


On Mon, Nov 28, 2011 at 3:09 PM, Shlomy Reinstein <sre...@gm...> wrote:
> Why override? They can provide their own actions and then you can bind the
> shortcuts / toolbar buttons to their own actions.
> Shlomy
>
> On Mon, Nov 28, 2011 at 11:49 PM, Alan Ezust <ala...@gm...> wrote:
>>
>> I disagree. I think plugins should be able to override core actions. And
>> many plugins already do.
>> But this is something I introduced to core, so I suppose I am responsible
>> for this mess.
>> I don't know where matthieu said that plugins should not override actions
>> though.
>>
>>
>> On Mon, Nov 28, 2011 at 1:10 PM, Shlomy Reinstein <sre...@gm...>
>> wrote:
>>>
>>> I think Matthieu was right; plugins should not override core actions.
>>> They can offer their own alternatives but should not override them.
>>> Shlomy
>>>
>>>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>