[
https://issues.apache.org/jira/browse/IVYDE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621305#action_12621305
]
jaguild edited comment on IVYDE-104 at 8/10/08 1:34 PM:
---------------------------------------------------------------
Sorry for the confusion. I mixed multiple points together hastily.
Editing and applying workspace-level options works just fine as you expect,
including the "Order alphabetically the classpath entries" feature. However:
# The feature is one of many (and last) on a busy property screen which caused
me to miss it in the first place. It should be made more prominent.
# I don't like the UI (a check box for that), because it doesn't give any
indication what order the libraries will be display in when it is NOT
checked...which was one reason for my opening this issue in the first place --
the displayed libraries didn't appear to be in any order to me. Instead, I
propose this option be exposed as a drop box or radio group with two items
"resolution", "alphabetical" to make it clear. If other orderings/groupings
make sense (e.g. grouped by organization) then those should be listed there as
well.
In 2.00alpha1, enabling project-specific Ivy-configuration is broken for me.
When I enable the project-specific configuration the whole plugin blows up and
I lose my classpath container entirely. But that is beside the point...even if
it was working properly, my other point is that the project-specific Ivy
configuration page/screen does not ALSO have a way to specify an
project-specific ordering for display of libraries which is separate from the
workspace configuration. Perhaps this is not so important though.
bq. Then about that shortcut in a context menu I am afraid that will not be
possible in the general case. In the case the project is not configured
"locally", and is relying on the global configuration, having a entry to
configure the order locally has no sense.
After thinking a bit about this, I see what you mean about the inconsistent
semantics. I was attempting address my #1 above, thinking that adding an item
to the context menu would make the option more prominent.
Though my suggestions may not be optimal, I think my points #1 and #2 above are
legitimate usability problems which should be addressed. Thanks for your
patience.
was (Author: jaguild):
Sorry for the confusion. I mixed multiple points together hastily.
Editing and applying workspace-level options works just fine as you expect,
including the "Order alphabetically the classpath entries" feature. However:
# The feature is one of many (and last) on a busy property screen which caused
me to miss it in the first place. It should be made more prominent.
# I don't like the UI (a check box for that), because it doesn't give any
indication what order the libraries will be display in when it is NOT
checked...which was one reason for my opening this issue in the first place --
the displayed libraries didn't appear to be in any order to me. Instead, I
propose this option be exposed as a drop box or radio group with two items
"resolution", "alphabetical" to make it clear. If other orderings/groupings
make sense (e.g. grouped by organization) then those should be listed there as
well.
In 2.00alpha1, enabling project-specific Ivy-configuration is broken for me.
When I enable the project-specific configuration the whole plugin blows up and
I lose my classpath container entirely. But that is beside the point...even if
it was working properly, my other point is that the project-specific Ivy
configuration page/screen does not ALSO have a way to specify an
project-specific ordering for display of libraries which is separate from the
workspace configuration. Perhaps this is not so important though.
bq. Then about that shortcut in a context menu I am afraid that will not be
possible in the general case. In the case the project is not configured
"locally", and is relying on the global configuration, having a entry to
configure the order locally has no sense.
After thinking a bit about this, I see what you mean about the inconsistent
semantics. I was attempting address my #1 above, thinking that adding an item
to the context menu would make the option more prominent. I think both of my po
> Display all resolved libraries in order
> ---------------------------------------
>
> Key: IVYDE-104
> URL: https://issues.apache.org/jira/browse/IVYDE-104
> Project: IvyDE
> Issue Type: Improvement
> Components: classpath container
> Affects Versions: 2.0.0.alpha1
> Environment: Eclipse 3.3.2
> Reporter: Jason A. Guild
> Priority: Minor
>
> The display listing of libraries resolved in Eclipse package explorer should
> be in some kind of predictable order. It can be frustrating when you are
> looking through a long list of libraries and can't see the one you are
> looking for fast.
> Right now, libraries are listed in what appears to be random order and should
> either be in order of resolution or (preferrably) sorted order by library
> name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
