Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-10-16T19:17:34ZEcoinformatics Redmine
Redmine Bug #4477 (Resolved): Grey out "undraggables"https://projects.ecoinformatics.org/ecoinfo/issues/44772009-10-16T19:17:34Zben leinfelderleinfelder@nceas.ucsb.edu
<p>In the Components tree we now have non-workflow items (items contained in KARs). These should be marked as different so that it's clear that we are mixing metaphors.</p> Bug #4475 (Resolved): Order context menu items consistentlyhttps://projects.ecoinformatics.org/ecoinfo/issues/44752009-10-16T19:15:36Zben leinfelderleinfelder@nceas.ucsb.edu
<p>There is a mix of options, sure, but options that appear across different context menus (ie "Open") should appear in similar locations on the list.</p> Bug #4474 (Resolved): Report viewer - enable scroll wheelshttps://projects.ecoinformatics.org/ecoinfo/issues/44742009-10-16T19:08:06Zben leinfelderleinfelder@nceas.ucsb.edu
<p>The viewer does not respond to scroll wheel actions currently. It should!</p> Bug #4472 (Resolved): Report Viewer - use different ViewPane classhttps://projects.ecoinformatics.org/ecoinfo/issues/44722009-10-16T19:05:38Zben leinfelderleinfelder@nceas.ucsb.edu
<p>We have too many unused "areas" of the view where it looks like there should be some other window hidden. we just need to use a different ViewPane implementation with fewer divisions</p> Bug #4471 (Resolved): Report Viewer - remove TOChttps://projects.ecoinformatics.org/ecoinfo/issues/44712009-10-16T19:02:20Zben leinfelderleinfelder@nceas.ucsb.edu
<p>the "Report Contents" tab is mostly useless - remove it from this view</p> Bug #4470 (Resolved): Report Viewer - labels should be vertically centeredhttps://projects.ecoinformatics.org/ecoinfo/issues/44702009-10-16T19:00:16Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Instead of appearing at the top of the item that they are labeling, L and R labels should be in the vertical center of the item.</p> Bug #4466 (Resolved): Report Designer - report layout not shown when opening KARshttps://projects.ecoinformatics.org/ecoinfo/issues/44662009-10-16T18:29:32Zben leinfelderleinfelder@nceas.ucsb.edu
<p>If I save a workflow+report layout as a KAR and then attempt to reopen the KAR after restarting Kepler, the report layout does not show up.</p>
<p>I've tracked this down to the fact that the workflow is "opened" before the report layout and the tab panes initialize at this point (before the report layout is "opened") so we end up with a default blank report layout.<br />I believe we just need to swap out the default blank report layout when we get around to "opening" the report layout that is in the KAR file we just opened.</p> Bug #4465 (Resolved): Report Designer - "drag to here" paper should disappearhttps://projects.ecoinformatics.org/ecoinfo/issues/44652009-10-16T18:24:59Zben leinfelderleinfelder@nceas.ucsb.edu
<p>After we have one or more items on the report we should hide the helpful "drag here" paper. If all items are deleted from the report, it should show up again.</p> Bug #4464 (Resolved): Report Designer - selection pointer behaviorhttps://projects.ecoinformatics.org/ecoinfo/issues/44642009-10-16T18:23:34Zben leinfelderleinfelder@nceas.ucsb.edu
<p>-do not use cross hair pointer anywhere<br />-arrow turns to finger on hover over any item (anywhere on item except text areas)<br />-clicking anywhere (except text field) will select that report item<br />-click+drag will use existing arrow/arrow+ for "moving" report items</p> Bug #4401 (Resolved): Synchronize properties with selected report itemhttps://projects.ecoinformatics.org/ecoinfo/issues/44012009-09-21T18:21:06Zdebi staggsstaggs@nceas.ucsb.edu
<p>Make the properties window show the properties for the report item that is selected.</p> Bug #4397 (Resolved): Panel should get selected whenever it has the focushttps://projects.ecoinformatics.org/ecoinfo/issues/43972009-09-21T18:06:25Zdebi staggsstaggs@nceas.ucsb.edu
<p>Highlight the panel whenever it has the focus.</p> Bug #4390 (Resolved): Semantic Type tag deletion does not remove component from Ontology in the c...https://projects.ecoinformatics.org/ecoinfo/issues/43902009-09-16T06:41:04ZAaron Aaronaschultz@nceas.ucsb.edu
<p>When I open a workflow that has a semantic type in the WRP suite I see the semantic type at the top of the window with a little x next to it. I press the x to delete the tag, in my case "Data Input". But the component still appears under Data Input in the Components ontology of the component library.</p> Bug #4170 (Resolved): Ensure reporting/provenance do not rely on any GUI classeshttps://projects.ecoinformatics.org/ecoinfo/issues/41702009-06-18T17:28:11Zben leinfelderleinfelder@nceas.ucsb.edu
<p>I'm not entirely sure how much of the "GUI" code is ever called when we execute a workflow fromthe command line. But we need to do our best to do perform crucial initializations as part of our GUI classes (i.e. in TabPane implementations and the like).<br />I do believe the Initializer classes are called even when running without the GUI. But let's make sure.</p> Bug #3608 (Resolved): Create initial class diagrams for the reporting feature.https://projects.ecoinformatics.org/ecoinfo/issues/36082008-11-07T20:11:36Zdebi staggsstaggs@nceas.ucsb.edu
<p>Create class diagrams for the reporting feature.</p> Bug #3148 (Resolved): Add authentication error reportinghttps://projects.ecoinformatics.org/ecoinfo/issues/31482008-02-14T19:06:12Zben leinfelderleinfelder@nceas.ucsb.edu
<p>When using the AuthenticationManager with the ecogrid services there is currently no feedback given to the user when errors occur (bad password, wrong username, service unavailable...etc).<br />Should use the MessageHandler's alert mechanism so that it can function without a GUI.</p>
<p>Note that when using the AuthenticatedQueryService, there is no requirement that the authentication credential be <em>valid</em>. Therefore an error that occurs during authentication should not prevent the authenticated query from continuing (equivalent to performing a public query).</p>
<p>Also: we may want to consider adjusting the login prompt behavior so that the prompt will reappear after an unsuccessful login attempt. Only after successfully authenticating (or canceling the action) would the prompt not reappear. Currently you are only given one chance to login - there is no re-prompting.</p>