Hi Larry,
I'm going to stand with Michaël on this one. Here is why: In SkyJUMP
(and probably JUMP) it behaves this way and it seems natural. I
suspect this capability has been lost along the way since OJ has added
more sophisticated support for window management and multiple views.
Here is how I tested so we can see if I understood exactly what
Michaël was going for:
1. I created two new projects, each with one rectangle in one layer.
In project 2 I selected the rectangle.
2. I opened an Attribute View for project 1 and project 2 for the one
layer in each.
3. With Attribute View 2 as the active window, I went to
Tools->Analysis->Buffer (Multiple Ring)
For SkyJUMP the menu was active and for OpenJUMP it was not. Make
Attribute View 1 active and SkyJUMP greys out the menu - OJ does not
change.
@Michaël: is this what you meant?
This is this "kind of" thing. I'm not sure I fully understand your
example though as I cannot see any reason to activate the menu with
Attribute View 2 and to deactivate it with Attribute View 1
in SkyJUMP.
In the ticket, I probably mixed several small consistency problems, and
to be honest, I noticed several of them on plugins I added.
But as you see, the rule to determine when a plugin must be activated is
not so obvious.
My main point is that a plugin should be deactivated when it cannot get
all the information it needs from the context.
Ex. if there are two projects opened and none of them is active (ex. the
active windows is the output window), there is
no way to know in which project you want to work (no plugin except
drivers has a combobox to choose the target
project). So most plugin should be deactivated (currently, some plugins
are still activated).
On the other hand, when there is no ambiguity and the plugin can get all
the information it needs
from the dialog box (ex. one project only, and a layer selector in the
plugin dialog box), I cannot see
any reason to grey it out.
I can see limits to this rule though : if a plugin needs selected
features, making it work when the attribute table
is active may be misleading as the plugin will work on features selected
on the view, not with features selected
on the table !
So I can admit that some plugins must be activated when one particular
window is active and not the other
and that layerview and attribute view must not always be considered as
equivalent from the plugin perspective.
Hope I could clarify (It has probably not been clear in my mind from the
beginning ;-)
Michaël
regards,
Larry
On Tue, May 14, 2013 at 3:46 PM, Michaël Michaud
<michael.mich...@free.fr <mailto:michael.mich...@free.fr>> wrote:
Hi,
> On 14.05.2013 19:54, Michaël Michaud wrote:
>> Le 14/05/2013 10:32, edgar.sol...@web.de
<mailto:edgar.sol...@web.de> a écrit :
>>> On 14.05.2013 08:43, SourceForge.net wrote:
>>>> ==> Should be activated if no layer is selected but a
Attribute table is active
>>>> Generate > Create point layer
>> I think plugins which have a layer chooser in their dialog box
should be
>> available
>> every time a the active frame is related to a task including at
least
>> one layer.
>> Selected layer, if any, should be proposed first.
>>
>> Don't you think so ?
>>
> sorry, lost me here.. can you give steps?
> why should 'Create point layer' be active when an attribute
window is active?
OK, I realize that what I feeled like something obvious is not...
I think that as a user, I have to know in which project I work (it is
not the same
to create a point in project 1 and to create it in project 2)
But I generally don't want to bother about which window is active,
if they
belong to the same project. Just want to work on my project.
The plugin may update the view, the table, both, create a report,
etc. It
is not related to a particular "view" of the project.
In "Create point layer" case, my last operation was to check or to
edit
some
coordinates in the attribute table. Now I want to create the
points. Why
should I have to explain OpenJUMP I don't want to create them in
Attribute
table but in the view. I just want to create them in my project. I
don't
want to
bother which is the active frame and click the view just to have
the menu
available.
Oh, this may not be a great example, but hope it makes my perspective
more clear.
> the plugin draws in the task frame, hence it should be active
only then.
Maybe you point a technical issue I did not see. My point is that the
user generally does
not need to bother which frame is active. In some cases, the soft may
need to know
of course.
Michaël
>
> ..eDe
>
>
------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers
complete
> security visibility with the essential security capabilities.
Easily and
> efficiently configure, manage, and operate all of your security
controls
> from a single console and one unified framework. Download a free
trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
<mailto:Jump-pilot-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers
complete
security visibility with the essential security capabilities.
Easily and
efficiently configure, manage, and operate all of your security
controls
from a single console and one unified framework. Download a free
trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
<mailto:Jump-pilot-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
