Super +1, good idea, Martin. Cheers, Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Friday, May 3, 2013 10:11 AM To: Apache SIS <[email protected]> Subject: Re: AbstractMetadata.toString() representation >Le 03/05/13 19:03, Martin Desruisseaux a écrit : >> Note that this is just for developer convenience. If such output is >> desired for end-user, then the steps are to get a TreeTable >> representation of the metadata, configure a TreeTableFormat and use it >> like below: >> >> AbstractMetadata myMetadata = ...; // Any of the ~80 available >> subclasses. >> TreeTable treeTableViewOfMyMetadata = metadata.asTreeTable(); >> TreeTableFormat format = new TreeTableFormat(myLocale, myTimezone); >> String s = format.format(treeTableViewOfMyMetadata); > >Just for the record, the code behind the above "metadata.asTreeTable()" >method call is a complete rewrite compared to what we had in Geotk, >which is why the port of other Geotk code has been delayed. The main >difference is that the SIS TreeTable view is read/write (i.e. invoking >Node.setValue(...) automatically invokes the appropriate setter methods >on the metadata object), while the Geotk one was read only. The intend >for this development is to make metadata TreeTable usable in GUI >metadata editors. > > Martin >
