Re: [ jEdit-devel ] plugins providing shortcuts

[Damien R. <dam...@gm...>]

Overall I like the idea, but it could become problematic if someone
installed a large number of plugins (say, while setting up a new system)
and it prompted you once for each new plugin. For automatic runs at least,
it would be better to display all available plugin defaults in a single
window.

On Thu, Apr 12, 2012 at 12:24 AM, Shlomy Reinstein <sre...@gm...>wrote:

> I haven't followed the discussion closely, but here's what I think about
> this subject:
>
> Slava made the rule (which has been followed so far) that plugins should
> not provide their own shortcuts, toolbar buttons and menu items. He had a
> reason for that. For this email, let's refer to these 3 types of properties
> (shortcuts, toolbar buttons and menu items) collectively as "plugin
> defaults".
>
> What do you say about the following:
> - A plugin will be able to define its own "desired plugin defaults". These
> will not use the same properties as the usual ones, but will have a
> slightly different prefix, e.g. "plugin.desired.".
> - jEdit will provide an action for each plugin, which will provide an easy
> way to accept the desired plugin defaults. This action will open a dialog
> listing the desired plugin defaults, and provide easy means to accept all
> of them or a subset (e.g. using checkboxes). In addition, if some plugin
> desired shortcut is already mapped to something else, it will show the
> current mapping, and allow setting another shortcut for the plugin action.
> Since this action is available for use at any time, the dialog will not
> list the desired plugin defaults which have already been accepted.
> - This special action can be configured (using the Global Options dialog)
> to run automatically whenever a plugin is installed or updated.
> - A new menu item will be added under 'plugins', something like "import
> plugin defaults..." which will show the list of plugins and allow the user
> to run the special action for a selected plugin.
>
> This feature gives plugins the ability to define defaults while not
> forcing the user to use them.
>
> * If I remember correctly, this topic of plugins providing shortcuts, menu
> items etc were discussed more than once in the mailing list. I cannot find
> it now using a simple google search, so maybe I'm wrong.
>
> Thanks,
> Shlomy
>
>
>
>
>
> On Wed, Apr 4, 2012 at 8:42 AM, Jarek Czekalski <jar...@po...>wrote:
>
>>
>> W dniu 2012-04-04 00:14, Alan Ezust pisze:
>> > plugins don't have to maintain any defaults for every keymap. Not even
>> > sure what that means.
>> You don't have to maintain defaults for every keymap. But the keymap is
>> a copied behaviour of another application. That application used a given
>> shortcut for a compile command, so for that keymap the original shortcut
>> should be provided, not the same for everyone.
>>
>> With the design I suggested it could be possible to provide a new keymap
>> through a plugin.
>> >
>> > Plugin developers can set preferred shortcuts in the plugin's own
>> > .props file which can be very easily overridden by the user in their
>> > own properties files (or user keymap as of jedit5).
>> Is it something that already works in jedit? I'm almost fine with it. I
>> was  concerned about another shortcut intercepted by Console without
>> ability to assign another meaning to it.
>>
>> (...)
>>
>> On Tue, Apr 3, 2012 at 2:20 PM, Damien Radtke <dam...@gm...>
>> wrote:
>> >>>> The problem with letting plugins create default shortcuts and menu
>> items
>> >>>> is that it can easily spiral out of control, since every plugin
>> author wants
>> >>>> theirs to be noticed. I think in general the "plugins shouldn't
>> install
>> >>>> shortcuts or menus" rule should remain the default, but not be
>> iron-clad.
>> >>>> Allowing a plugin to create default shortcuts should be the
>> exception to the
>> >>>> rule.
>> It's hard to discuss things for which no design was given, like "letting
>> plugins create menu items", "allowing a plugin to create default
>> shortcut".
>>  With the design I suggested there's no danger of spiraling out of
>> control, as the user has a choice to "skip all".
>>
>> Jarek
>>
>> (...)
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Better than sec? Nothing is better than sec when it comes to
>> monitoring Big Data applications. Try Boundary one-second
>> resolution app monitoring today. Free.
>> http://p.sf.net/sfu/Boundary-dev2dev
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>