Changes between Version 122 and Version 123 of ReviewHeuristicLab3.3.0Application


Ignore:
Timestamp:
04/08/10 21:42:25 (11 years ago)
Author:
swagner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReviewHeuristicLab3.3.0Application

    v122 v123  
    178178
    179179=== Priority: HIGH ===
    180  * searching for "prog" in the operator pane and using backspace twice => program hangs
    181   * abeham: see also ticket #904
     180 * Searching for "prog" in the operator pane and using backspace twice => application hangs.
     181   * abeham: See also ticket #904.
    182182 * Empty TSP problem always throws an exception
    183  * If later a problem is loaded, the algorithm still throws an exception (maybe automatically reset algorithm?)
    184  * A Help menu should be available, maybe also an about dialog
     183 * If later a problem is loaded, the algorithm still throws an exception (maybe automatically reset algorithm?).
     184 * A Help menu should be available, maybe also an about dialog.
    185185
    186186=== Priority: MEDIUM ===
     
    188188   * Maybe the operators pane should be hidden by default, or only shown once an algorihtm graph is loaded or the click action could give an explanation why nothing happens and that you should drag them over into an operator graph. 
    189189   * Another idea, double clicking an operator could add it to the currently visible operator graph. (Probably not so easy to implement)
    190  * Some algorithm parameters cannot be set until problem is selected: display reason why parameters cannot be changed yet
    191    * maybe make the Problem tab the default one for Algorithms
    192  * Problem parameters that cannot be changed by the user could be hidden
    193    * i.e. Maximation is always the first parameter but can rarely be changed
     190 * Some algorithm parameters cannot be set until problem is selected: display reason why parameters cannot be changed yet or maybe make the Problem tab the default one for Algorithms.
     191 * Problem parameters that cannot be changed by the user could be hidden.
     192   * i.e. Maximation is always the first parameter but can rarely be changed.
     193   * swagner: After a discussion with maffenze, it was decided not to hide parameters. The parameters collection of a problem should show all parameters of a problem so that a user sees and understands how the underlying problem object looks like. This should help users when they start to implement own problems.
    194194 * The [+] Button in the !ValueParameterView is slightly misleading once a value has been added, then it should mean change the value.
    195  * The [+] Button in the !ValueParameterView should also be disabled if the type of the parameter cannot be changed
    196  * New Item Dialog: Algorithm and Problem items should be listed before the advanced items in "Algorithm Design"
    197  * Parameters of sub-operators that are not changeable by the user should be hidden (e.g. lookup parameter)
     195 * The [+] Button in the !ValueParameterView should also be disabled if the type of the parameter cannot be changed.
     196   * swagner: Even if the type of a value parameter cannot be changed, it might be necessary to be able to exchange the whole value object. Therefore the [+] button should be enabled in every case.
     197 * New Item Dialog: Algorithm and Problem items should be listed before the advanced items in "Algorithm Design".
     198   * swagner: After a discussion with maffenze it was decided to keep alphabetical sorting of creatable groups in the new item dialog. Alphabetical sorting is used in many places throughout the whole application and it might be irritating for a user if we change this in the new item dialog. Furthermore, it depends on a user which creatable groups are considered to be more important.
     199 * Parameters of sub-operators that are not changeable by the user should be hidden (e.g. lookup parameter).
    198200 * Graph View
    199201   * Icon for expanding/collapsing details is rather confusing (undo/redo), should be +/- imho
     
    207209   * swagner: Showing results by default is critical, as the continuous redraw of a result's value (e.g. a quality chart) might consume a lot of runtime. Therefore the user should have to select a result manually, if he wants to look at a result.
    208210 * Hierarchical grouping of operators by namespace in operator tab (instead of just by plugin) or maybe just remove the intial "HeuristicLab" as this is common for all of them and makes it harder to scan for the right plugin/namespace.
    209    * swagner: After a discussion with maffenze, it was decided not to change the way how operators are grouped and displayed in the operators sidebar. Reasons are that grouping hierarchically by namespaces might lead to deep trees that have to be opened to get an operator and that the initial "HeuristicLab" in each plugin name might not be common for all plugins if an external user develops an own plugin.
    210 
    211 ----
    212 
     211   * swagner: After a discussion with maffenze it was decided not to change the way how operators are grouped and displayed in the operators sidebar. Reasons are that grouping hierarchically by namespaces might lead to deep trees that have to be opened to get an operator and that the initial "HeuristicLab" in each plugin name might not be common for all plugins if an external user develops an own plugin.
     212
     213----
     214