From: Mitch S. <mit...@be...> - 2010-08-06 18:05:59
|
On 08/06/2010 09:05 AM, Paul Stodghill wrote: > For starters, I see that "subfeatures":true needs to be added to > trackInfo.js, but what else? "subfeatures": true can go in the config file, yes, but it doesn't end up in trackInfo.js, which is something else. > (I tried following the configuration provided for the Drosophila, but > the syntax used for that example and for the for the config file > reference documentation appear to be out of sync with the current > implementation.) I'm not sure what specifically you're referring to here, but I'm guessing that there may be some confusion related to the roles that the different JS(ON) files play in JBrowse. For biodb-to-json.pl, it goes: JSON config file--->biodb-to-json.pl--->(one entry in data/trackInfo.js, data/tracks/<refseq>/<tracklabel>/trackData.json, optionally data/tracks/<refseq>/<tracklabel>/subfeatures-*.json) for flatfile-to-json.pl, it goes: command line parameters--->flatfile-to-json.pl--->(one entry in data/trackInfo.js, data/tracks/<refseq>/<tracklabel>/trackData.json, optionally data/tracks/<refseq>/<tracklabel>/subfeatures-*.json) So the config file looks different from (and serves a different role from) data/trackInfo.js. The config file tells biodb-to-json.pl how to generate the JSON for each track; trackInfo.js tells the client-side javascript what tracks are available. Regards, Mitch |