Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-10-01T23:44:42ZEcoinformatics Redmine
Redmine Bug #617 (Resolved): After updating a data file, entity, attribute and physical document version ...https://projects.ecoinformatics.org/ecoinfo/issues/6172002-10-01T23:44:42ZJing Taotao@nceas.ucsb.edu
<p>When I created new data package, local and metacat has same version(1)in each <br />file.</p>
<p>Howerver, if data file was changed in data table and update button was <br />clicked. It was found dataset, datafile, entity, attribute, physical were <br />updated to version 2 in local. But in metacat, only dataset and datafile <br />updated to version 2, the others still keep version 1. Actually, only data <br />file was updated and entity, attribute file would still keep in version 1.</p> Bug #613 (Resolved): verify/fix synchronize/export/delete for data package windowhttps://projects.ecoinformatics.org/ecoinfo/issues/6132002-09-30T20:50:58ZMatt Jonesjones@nceas.ucsb.edu
<p>When Morpho is displaying a package, several of the menus that work for the<br />result set window should also work for the package. These include the<br />synchronize, delete, and export menus. Need to verify that each of these menus<br />is active when a data package window is open, and to make sure they work<br />properly. Fix them if they don't.</p> Bug #610 (Resolved): verify/fix problem with importing comma and tab delimited datahttps://projects.ecoinformatics.org/ecoinfo/issues/6102002-09-30T20:41:50ZMatt Jonesjones@nceas.ucsb.edu
<p>Jing reported a problem importing tab delimited data in Morpho. We used to have<br />a problem importing comma delimited data, although that is apparently fixed. <br />Nedd to verify that importing all delimited data works, and if not, fix it. <br />While at it, please also verify that importing fixed format data works reliably<br />as well.</p> Bug #604 (Resolved): Right-click in DataView Clears Selectionhttps://projects.ecoinformatics.org/ecoinfo/issues/6042002-09-28T16:36:57ZMatthew Brookebrooke@nceas.ucsb.edu
<p>If a user selects a set of cell sin the dataview table, then right-clicks on the<br />selection to get a popup menu (e.g. if they are planning to "copy" the<br />selection) the selection is cleared, and only the cell immediately beneath the<br />mouse cursor is selected.</p>
<p>I think mouse listener just needs to be changed so it doesn't start a selection<br />when right button clicked - only when left button clicked</p> Bug #603 (Resolved): XSLT works only under JRE1.4https://projects.ecoinformatics.org/ecoinfo/issues/6032002-09-28T03:00:09ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Full XSLT styling in the MetaViewer panes (which pulls XSLT from a jar file)<br />works only if running under JDK1.4. In jdk1.3, exception is:</p>
<ul>
<li>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * <br />; Line#: 88; Column#: 54 (doesn't say what file this is in!!)</li>
</ul>
<p>javax.xml.transform.TransformerException: A location step was expected following<br />the '/' or '//' token.</p>
<ul>
<li>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</li>
</ul>
<p>If the config file settings are changed so that every eml module maps to the<br />default XSL stylesheet instead of its own custom stylesheet, then it works under<br />JDK1.3 too, without the errors. However, but the triples are not shown by the<br />defautl CSS - so there's no way to navigate around - and the metadata's far from<br />readable :-(</p>
<p><strong>Note</strong> that, when the default XSL is being used, this had an <xsl:import... ><br />statement in it, which loads OK; it also uses the default CSS stylesheet, which<br />also loads OK (provided there are no Font-face definitions in the CSS -<br />otherwise this crasp out on Linux) - it therefore looks liek the path stuff is<br />all OK (with regard to pulling things out of JAR files). Note also that JDK1.4<br />ships with the JAXP packages - and these are almost certainly being put in the<br />classpath in ahead of XALAN?</p>
<p>Maybe the parser that comes with JAXP (crimson??) is less picky about syntax, so<br />it doesn't throw the error mentioned above, whereas XALAN picks it up? Maybe it<br />would be worth changing the XSLT files one by one until the line number in the<br />error changes, to track down the problem? Note that these XSLT files are from<br />eml module, and work OK in production metacat (but what version of Xalan is that?)</p> Bug #569 (Resolved): enabling/diabling menus and toolbars in MorphoFramehttps://projects.ecoinformatics.org/ecoinfo/issues/5692002-08-22T18:11:39ZMatt Jonesjones@nceas.ucsb.edu
<p>In the current architecture, each MorphoFrame's menus and toolbars are created<br />by the UIController. However, the context of each window whould determine which<br />of those menus and toolbars are enabled. When a window is switched to the<br />foreground, its context would be used to set the enabled state for its menus and<br />toolbars.</p>
<p>Here are the types of Actions we need to support:<br />1) Those that are always enabled regardless of context<br />2) Those that are enabled depending on the current window context<br />3) Those that are enabled depending on application state outside of the current<br />window</p>
<p>Are there other possible cases?</p>
<p>We also may find that groups of actions are always enabled/disabled as a set,<br />and so we may want to make it easy to do that. For example, When a column is<br />selected in a data table, several menu items should be enabled in the Data menu,<br />including "Insert column before", Insert column after, Edit column metadata,<br />sort by column, etc.</p> Bug #555 (Resolved): extend windowing framework to allow multiple windows with menushttps://projects.ecoinformatics.org/ecoinfo/issues/5552002-07-19T18:22:48ZMatt Jonesjones@nceas.ucsb.edu
<p>The existing ClientFramework is designed to havea single application window for<br />morpho that contains the menu and toolbars. In the redesign of the UI to make<br />it more data centric, we have decided we need for each package and resultset to<br />be opened in its own window and to include a common set of menu bars and<br />toolbars and status bars.</p>
<p>This bug is to redesign the ClientFramework architecture so that it allows for<br />plugins to create new windows with a specific content pane registered, and the<br />framework would return the window that was created, as well as notify existing<br />windows to update their window menus with the presence of the new window.</p>
<p>This new "createWindow" function would be called by the data package and query<br />subsytems to create their windows, and possibly by the editor subsystem to<br />create its windows as well.</p>
<p>The redesign will likely involve creating a new "Morpho" class that represents<br />the application as a whole and includes utility and main methods and application<br />state fields, and a reworked ClientFramework that implements the visual Frame<br />components separately.</p> Bug #546 (Resolved): data editing enhancementshttps://projects.ecoinformatics.org/ecoinfo/issues/5462002-07-08T17:25:33ZMatt Jonesjones@nceas.ucsb.edu
<p>Need several new features for editing data:</p>
<p>1) When an existing data file is updated, be able to save it using an ID in the<br />same family but a different revision # (right now morpho creates a completely<br />new ID rather than simply rev'ing the old one)</p>
<p>2)Need to be able to add new records to an existing file</p>
<p>3) Need to be able to provide a metadata description of a data file and add all<br />of the records for the data file from scratch.</p> Bug #533 (Resolved): new File|Open to accomodate new UI designhttps://projects.ecoinformatics.org/ecoinfo/issues/5332002-06-13T16:39:22ZMatt Jonesjones@nceas.ucsb.edu
<p>The "File|Open..." menu will now display a list of data packages that are owned<br />by the user in a dialog box. This replaces the current "ownerQuery" panel that<br />is displayed in the main morpho content pane. The dialog will have a radio<br />button that lets the user switch between displaying all owned packages, just<br />those that are local, or just those on metacat. Be sure to consider how this<br />list can be configured to use hierarchical folders as described in bug 306. <br />When selected, the package will be opened in a window as described in bug 532.</p>
<p>The search window will produce result lists that are structured in the same way<br />as the open dialog (again, see bug 306). When one does a search, double<br />clicking on a search result (a package) should open it in the same way that the<br />File|Open dialog works.</p> Bug #532 (Resolved): data-oriented UI displayhttps://projects.ecoinformatics.org/ecoinfo/issues/5322002-06-13T16:35:03ZMatt Jonesjones@nceas.ucsb.edu
<p>The current morpho UI displays a result set from a default query as its<br />principal interface. We decided to change this to instead display a<br />"data-oriented" view of a single package. In this new UI, each package is<br />represented as a document in a single window. Multiple windows can exist at<br />once so that more than one package can be displayed (need to decide if these<br />should be internal to a single frame or whether each should be its own JFrame,<br />in which case the menus etc need to be reproduced as well). Tabs at the bottom<br />of the window allow one to switch among spreadsheet views of the different<br />entities. Non-tabular entities could be displayed as browse images. An<br />additional tab lets one see a view of the package metadata. Each column in the<br />tables can be clicked somehow to see that attributes metadata. The entity<br />metadata might be displayed at the top of the view. I will also file a bug for<br />rearranging the File|Open dialog.</p> Bug #499 (Resolved): Swing changes outside the event threadhttps://projects.ecoinformatics.org/ecoinfo/issues/4992002-05-08T16:40:42ZDan Higginshiggins@nceas.ucsb.edu
<p>When the SwingWorker class was added to Morpho to create new threads for<br />time-consuming tasks, some modifications to Swing components were apparently<br />moved outside the event thread. This is not allowed since Swing components are<br />not multithreaded. Problems have not been noted during normal operation of<br />Morpho but may cause subtle problems in the future. (Bug noted during attempts<br />to convert Morpho to run with Java Web Start).</p>
<p>In particular, there are a number of modifications made to the treenode<br />structure in the XML editor outside the event thread. This would not appear to<br />be a problem until a new DefaultTreeModel is created and a method like 'reload'<br />is called. According to the documentation, this method triggers the Model to<br />notify all listeners that the model has changed.</p> Bug #446 (Resolved): itislib taxonomic synonym lookup failshttps://projects.ecoinformatics.org/ecoinfo/issues/4462002-03-21T17:49:59ZMatt Jonesjones@nceas.ucsb.edu
<p>The itislib library no longer successfully returns synonyms from the ITIS*CA web<br />interface. Need to determine what changed and update itislib accordingly.</p> Bug #396 (Resolved): login dialog requires tab before text entryhttps://projects.ecoinformatics.org/ecoinfo/issues/3962002-01-11T19:43:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>The password field of the login dialog should have default focus so the user<br />does not have to hit the tab key to start entering their password.</p> Bug #391 (Resolved): column definition is not retained through wizard navigationhttps://projects.ecoinformatics.org/ecoinfo/issues/3912002-01-11T18:51:51ZChad Berkleyberkley@nceas.ucsb.edu
<p>If you get to the text import wizard screen where you enter column definition,<br />then enter a definition, then click the 'back' button twice (back to the first<br />screen), then go back to the definition screen, the definition you entered is lost.</p> Bug #356 (Resolved): resolve icon usability issueshttps://projects.ecoinformatics.org/ecoinfo/issues/3562001-12-01T00:49:39ZMatt Jonesjones@nceas.ucsb.edu
<p>Current icons in Morpho are not completely telegraphic. Need to resolve<br />usability and understandability of icons with input from various users,<br />including REOT.</p>