Jalama: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-06-24T02:11:40ZEcoinformatics Redmine
Redmine Bug #5056 (Resolved): test bug 2https://projects.ecoinformatics.org/ecoinfo/issues/50562010-06-24T02:11:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Another test.</p> Bug #5055 (Resolved): test bug 1https://projects.ecoinformatics.org/ecoinfo/issues/50552010-06-24T02:10:53ZMatt Jonesjones@nceas.ucsb.edu
<p>This is a test.</p> Bug #2447 (New): Jalama web-app XUL doesn't work in Firefox 1.5+https://projects.ecoinformatics.org/ecoinfo/issues/24472006-05-26T22:50:36ZMatthew Brookebrooke@nceas.ucsb.edu
<p>In the Jalama web-app ("Whippet"), the automatic XUL generation works fine, but the resulting XUL UI's don't display properly in Firefox 1.5+ (but are fine in Firefox 1.0x)</p>
<p>What has changed with XUL rendering in FF between 1.0.7 and 1.5?</p>
<p>This seems to be a problem with the "container" type XBL components - see the "record_per_screen" binding in the XBL file:</p>
<p>jalama/chrome/content/jalama_library/widgets/datatable_bindings.xml</p>
<p>or maybe the "complex_element", "invisible_container" and "bordered_vbox" bindings in the file:</p>
<p>jalama/chrome/content/jalama_library/widgets/complex_element.xml</p> Bug #2127 (Resolved): Fix required/not required and bold labels (minoccurs/maxoccurs issue)https://projects.ecoinformatics.org/ecoinfo/issues/21272005-06-16T19:24:30ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Fix required/not required and bold labels in XBL widgets. Thsi is a side-effect<br />of schema generation vs non-generated schema, and minoccurs/maxoccurs stuff.<br />widgets currently look to see if minOccurs>0, and if so, then field is<br />"required". We need another way of determining required-ness</p> Bug #2126 (Resolved): Show/hide examples for input fieldshttps://projects.ecoinformatics.org/ecoinfo/issues/21262005-06-15T16:57:27ZMatthew Brookebrooke@nceas.ucsb.edu
<p>this bug replaces bug <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: XBL Datatable Widget - show/hide relevant metadata for input fields (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/1626">#1626</a><br />---------------------------</p>
<p>Have implemented a framework for adding a description label above each input<br />field and an example widget below each input field.</p>
<p>Description labels are being populated OK from metadata; however, I'm not sure<br />where to pull the examples from, within the EML...</p> Bug #2090 (Resolved): problem with registering UIhttps://projects.ecoinformatics.org/ecoinfo/issues/20902005-05-25T18:38:48ZMatthew Brookebrooke@nceas.ucsb.edu
<p>using dataset:<br />seabloom.5.2<br />Sedgwick BYDV Prevalence</p>
<p>1) generate a data form</p>
<p>2) choose table "bydv-data-out.csv" for generation</p>
<p>3) see exception:<br />note "ID = data_form_seabloom.5.2_table_No_such_entity!.ser" <br />am i replacing dashes <strong>before</strong> asking datapackage for the entity? (hence<br />"No_such_entity!"??)</p>
<hr />
<p>Exception in thread "Thread-7" java.lang.IllegalArgumentException: Non-valid ID<br />received:<br /> ID = data_form_seabloom.5.2_table_No_such_entity!.ser<br /> (contains illegal characters)<br /> xulFile = <?xml version="1.0"?><br />[...]<br /></window><br /> docType_schemaLocation = eml://ecoinformatics.org/eml-2.0.0<br /> xpath = /<br /> mode = editor<br /> at<br />edu.ucsb.nceas.jalama.JalamaFormLib.throwIllegalArgumentException(JalamaFormLib.java:421)<br /> at edu.ucsb.nceas.jalama.JalamaFormLib.installForm(JalamaFormLib.java:301)<br /> at<br />edu.ucsb.nceas.jalama.entrypoint.morpho.OpenUIGenCommand$UIGenThread.run(OpenUIGenCommand.java:394)</p> Bug #2087 (Resolved): XUL Error when runnign UI for a second time on clienthttps://projects.ecoinformatics.org/ecoinfo/issues/20872005-05-24T15:23:02ZMatthew Brookebrooke@nceas.ucsb.edu
<p>start jalama on client, choose a UI and hit start. Collect data and hiot finish.<br />close this window. go back to homepage and select same UI again, and hit start.<br />window pops up showing a xul error</p> Bug #1932 (Resolved): PISCO APP: show species names in 2d popup instead of codeshttps://projects.ecoinformatics.org/ecoinfo/issues/19322005-02-01T23:49:51ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Switch species codes & species names in drools, so species names are shown in 2d<br />popup instead of codes</p> Bug #1929 (Resolved): Morpho Plugin for Field Data-Collection Adminhttps://projects.ecoinformatics.org/ecoinfo/issues/19292005-02-01T21:52:59ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Morpho Plugin for Field Data-Collection Admin has 2 main modes of operation:</p>
<p>*<strong>**</strong><br />1) Form generation:</p>
<p>a) basic requirement:</p>
<p>Add a 'Generate form' menu option, so user can browse EML data sets (local or<br />metacat) in morpho; which passes the current doc to the UI Generation code, and<br />the resulting XUL is saved somewhere (in profile?) for later download to a tablet</p>
<p>User can also go thru' DP wizard and create a new dataset to use as the basis of<br />UI generation - after creating document, proceed as above</p>
<p>b) future development:</p>
<p>If chosen Dataset has multiple tables, let user define which of these are used<br />as the basis of UI generation. Potentially the first step towards Mark's<br />requested "templating" featyre, whereby an existing dataset is used as a<br />starting point for a new dataset</p>
<p>*<strong>**</strong><br />2) dataset merging and Upload</p>
<p>a) basic requirement:</p>
<p>incoming datasets would all be put inside a subfolder that resides in the same<br />root directory, within the user's morpho profile - eg</p>
<pre><code>~/.morpho/[...]/jalama_incoming/Intertidal_12Jan05/<br /> ~/.morpho/[...]/jalama_incoming/Intertidal_28Jan05/<br /> ~/.morpho/[...]/jalama_incoming/Intertidal_31Jan05/</code></pre>
<p>Plugin would allow user to pick one of these directories, and all that dir's<br />contents would be sent to the fragment aggregator for merging</p>
<p>Resulting merged dataset would then be copied to user's main morpho profile<br />directory, so it can be browsed and manipulated in morpho, and can be uploaded<br />to metacat if required</p>
<p>b) future development:</p>
<p>Allow more sophisticated browsing (and poss Morpho search function?) to choose<br />datasets for merge - browser would show metadata in listings, like morpho search<br />results currently do (title, keywords, owner etc). User can select multiple<br />datasets and then hit merge button</p> Bug #1928 (Resolved): Build deployment server using http over tcp/iphttps://projects.ecoinformatics.org/ecoinfo/issues/19282005-02-01T21:32:23ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Build deployment server that can be contacted from tablet PCs (using http over<br />tcp/ip) in order for them to get 2 things:</p>
<p>1) (more often) zip file containing generated form(s) and associated EML files</p>
<p>2) (less often) updated Jalama software, in the form of a WAR file for<br />deployment in Tomcat</p>
<p>NOTES:</p>
<p>a) When step (1) is carried out, we should be able to check if the user has the<br />latest version of the Jalama WAR, and if not, download and install it<br />automatically (maybe ask admin first)</p>
<p>b) because jalama's httprenderer directory in the tomcat servlet context may be<br />deleted and replaced by a new WAR at some point, we should ensure that we don't<br />lose any critical files during this process - either:<br />i) by backing them up and re-writing them to the new context (harder), or <br />ii) by just storing them elsewhere to begin with (easier, and we already use<br />~/.jalama for forms, so why not for data etc?)</p> Bug #1689 (Resolved): deploy the nightly build on fedora and mac osxhttps://projects.ecoinformatics.org/ecoinfo/issues/16892004-09-15T18:10:29ZJohn Harrisharris@nceas.ucsb.edu
<p>Currently, the nightly build runs on the win32/RH7.2 platform and we need to<br />have it running on the macosx and a newer version of linux. In doing this, make<br />sure to update the notes on building jalama.</p> Bug #1683 (Resolved): servlet cache is missing in the warfilehttps://projects.ecoinformatics.org/ecoinfo/issues/16832004-09-14T19:53:37ZJohn Harrisharris@nceas.ucsb.edu
<p>I just compiled jalama on linux, with no problems, and then installed the<br />httprenderer (the Whippet application) war file in my tomcat servlet container<br />(4.1.27) and it failed to find the 'cache'. So, I made a directory in the<br />httprenderer dir called cache and everything worked fine. This looks like a<br />pretty esay fix, and without the fix the sw is unusable.</p> Bug #1631 (Resolved): Purchase and port to small devicehttps://projects.ecoinformatics.org/ecoinfo/issues/16312004-07-07T23:11:45ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need to purchase small device (mini-tablet PC?) and get jalama runnign on it -<br />poss whippet with localhost tomcat, and/or wireless link to tomcat on a "base<br />station laptop", or using webclient renderer</p>
<p>Need to ensure we have the right XBL widgets to render on smaller screen size,<br />and need to consider optimizing XBL for different user input methods (beyond<br />mouse & keyboard, which we currently use)</p> Bug #1629 (Resolved): get custom CSS support workinghttps://projects.ecoinformatics.org/ecoinfo/issues/16292004-07-07T23:02:31ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Need to be able to specify external CSS file(s) in generated UIs, and pull<br />existing CSS styles out of XBL Bindings.</p>
<p>Note that it might be feasible and preferable to avoid the use of rdf files for<br />referencing the CSS, since the whippet webapp (and probably the webclient app)<br />currently have an xml directive:</p>
<p><?xml-stylesheet href="chrome://global/skin/" type="text/css"?></p>
<p>Maybe we could do another of these but with the href="our css href" - which<br />woudl be customized as a chrome:// url for webclient renderer, or <a class="external" href="http:// url">http:// url</a><br />for the httprenderer. This differentiation is already in place in the renderers<br />- they "know" what their base url is, and set it automatically in the XULFile<br />objects</p>
<p>which pulls in the mozilla default stylesheet.</p>
<p>The stylesheet in th eXUL file can be set thru a method in the XULFile.java class</p> Bug #1628 (Resolved): Drools Rules - more sophisticated rules for data editorhttps://projects.ecoinformatics.org/ecoinfo/issues/16282004-07-07T22:52:26ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Make rules more sophisticated in order to populate the UI labels etc in a more<br />user-friendly.manner.</p>
<p>1) Look for an attribute/attributeLabel (not a required element), and use it if<br />it exists, otherwise, use attributeName (required)</p>
<p>2) Look at the eml-constraint for each attribute, and if it's "not nnull", then<br />make the input widget require a value (minoccurs=1) - if it's not required, make<br />minoccurs=0</p>
<p>3) Need to look carefully at EML and decide what other info can be used -<br />documentation etc?</p>