Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-03-15T20:51:05ZEcoinformatics Redmine
Redmine Bug #4883 (New): Need more command line options for kar fileshttps://projects.ecoinformatics.org/ecoinfo/issues/48832010-03-15T20:51:05ZChad Berkleyberkley@nceas.ucsb.edu
<p>right now, we can execute a single workflow contained in a kar file with the -runwf command line switch. It would be nice to have more options for working with kar files on the command line. The minimal options I would like to see are:</p>
<p>1) allow the user to specify which workflow within a kar file to execute (if there is >1). <br />2) allow the user to specify the output location. Either a server or local directory.<br />3) allow the use of a remote kar file with an https url (i.e. for a kar file stored in a repository).</p>
<p>Please add more requirements as you see fit. We will add this to the queue of post-2.0 enhancements.</p> Bug #4785 (New): move cache object from 1.0 to 2.0https://projects.ecoinformatics.org/ecoinfo/issues/47852010-02-10T23:13:31ZChad Berkleyberkley@nceas.ucsb.edu
<p>Cache kar objects from 1.0 that contain customized actors (i.e. not those shipped with 1.0) need to be migrated to the 2.0 installation. Any kars that include jars must be made into modules (see bug 4702).</p> Bug #4735 (New): Allow params to be passed to ConfigurationManager from the command linehttps://projects.ecoinformatics.org/ecoinfo/issues/47352010-02-04T20:48:06ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need a mechanism for passing params to CM from the command line. This is a post 2.0 feature.</p> Bug #4667 (In Progress): New documentation on modules and extension points for moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/46672010-01-13T22:49:25ZChad Berkleyberkley@nceas.ucsb.edu
<p>Should include information on the config system, karentryhandlers, viewpanes,<br />adding icons to the config, etc. See the Initialize methods of wrm and provenance for more info.</p> Bug #4341 (New): rearrange the actors module into smaller moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/43412009-08-26T22:54:57ZChad Berkleyberkley@nceas.ucsb.edu
<p>I'll create a list of proposed modules for the actors currently all lumped together in the actors module. The new module names should have a naming convention of "actors-xxx" so that they all sort together and so that it's evident that the module is primarily an actor module. Once I'm done with this list, I'll post it to the wiki and we can have an email discussion about how others think the actors should be re-modularized.</p> Bug #4339 (New): build system needs to provide more information on moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/43392009-08-26T20:52:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>The build system has a 'describe' task that will svn cat the description.txt file of any module. This is a good start, but only the ppod module has a description.txt file. Furthermore, the description.txt file is located in the root of the module instead of in the module-info directory where such metadata should probably reside.</p>
<p>To close this bug:<br />-The description.txt file needs to be redesigned to include the following fields (whoever works on this should evaluate and probably use the kepler documentation format for this):<br /> 1) Title<br /> 2) Description<br /> 3) Author*<br /> 4) Related Modules*<br />-The description.txt file should be located in module-info<br />-All modules should have a valid description file and all core modules must have a description.txt file<br />-Modify the list-modules task to print the description, name, etc of every module in the system.</p> Bug #4328 (New): change-to command checks out across brancheshttps://projects.ecoinformatics.org/ecoinfo/issues/43282009-08-21T18:54:18ZChad Berkleyberkley@nceas.ucsb.edu
<p>If kepler is currently in a branch, the change-to command should not update from the trunk. Once a branch is selected with the -Dbranch=xxx param, the build system should keep the current workspace in the branch until the user updated to another branch or the trunk. The build system should also print a banner alerting the user that he/she is working in a branch to avoid confusion.</p>
<p>this bug arose when we added several modules to the trunk. Matt was working in a branch (unknowingly) and when he ran 'ant change-to -Dsuite=kepler' it updated the kepler/module-info/modules.txt file from the trunk, but did not update the rest of the modules to the trunk so the build failed. The build-area was also running from the branch so the excludes file was not updated and would not allow him to build ptolemy.</p> Bug #4323 (In Progress): Add the "send to back" menu to keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/43232009-08-18T19:49:26ZChad Berkleyberkley@nceas.ucsb.edu
<p>Ptolemy has an appearance/send to back menu that is not in kepler. We should add this and similar menus to the kepler gui.</p> Bug #4306 (In Progress): add command line params to the configurationhttps://projects.ecoinformatics.org/ecoinfo/issues/43062009-08-12T21:19:45ZChad Berkleyberkley@nceas.ucsb.edu
<p>There's been a request to have an actor know what the command line params were when Kepler was started. It should be pretty easy to add these as parameters of the configuration upon startup. An actor could then just get the configuration and look up the params.</p> Bug #4260 (New): Add a test suite for the build systemhttps://projects.ecoinformatics.org/ecoinfo/issues/42602009-07-22T18:25:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need to create a testing harness for the build system to ensure that all functionality remains working as new features are added. This should be run with the nightly build.</p> Bug #4168 (New): User documentation creates bloat in workflowshttps://projects.ecoinformatics.org/ecoinfo/issues/41682009-06-18T16:49:11ZChad Berkleyberkley@nceas.ucsb.edu
<p>Currently, the user documentation is copied into every actor instance as the actor is drug to the canvas. The problem that this is addressing is that people need to be able to customize the documentation for actors that they have customized on the canvas. The problem with this approach is that it creates unnecessary duplicate documentation in every actor instance. One solution would be to diff the documentation against the original and just store what is different in the actor instance.</p> Bug #4162 (New): using the alt key makes menus appear in strange places on OSXhttps://projects.ecoinformatics.org/ecoinfo/issues/41622009-06-15T22:53:41ZChad Berkleyberkley@nceas.ucsb.edu
<p>if you do alt-F or alt-E on the mac, the menu shows up on the application window instead of coming down from the menu bar. Not sure if these alt key combos are even supposed to work on the mac. Might just disable it.</p> Bug #4112 (New): make kepler use OSX dialog boxeshttps://projects.ecoinformatics.org/ecoinfo/issues/41122009-05-27T23:13:59ZChad Berkleyberkley@nceas.ucsb.edu
<p>Add configuration to the mac extensions to make kepler use the OSX file open/save dialog boxes instead of the default java ones.</p> Bug #2140 (New): need dataset extraction WF for documentation/example purposeshttps://projects.ecoinformatics.org/ecoinfo/issues/21402005-07-05T21:20:47ZChad Berkleyberkley@nceas.ucsb.edu
<p>We need a simple dataset extraction workflow for documentation/example purposes.<br /> This goes along with the helloworld and R workflows. This was decided at the<br />june 05 kepler meeting.</p> Bug #1884 (In Progress): Enable drag and drop of ports and relationshttps://projects.ecoinformatics.org/ecoinfo/issues/18842005-01-20T17:59:21ZChad Berkleyberkley@nceas.ucsb.edu
<p>you should be able to drag and drop the ports and relations instead of clicking<br />on the toolbar button and having the port appear somewhere. this functionality<br />should be similar to dragging an actor.</p>