Skip to content

Conversation

@andrewdavidsmith
Copy link

@andrewdavidsmith andrewdavidsmith commented Sep 9, 2025

Adding proposed "bigComposite" with:

  • A cgi app to accept/construct cart updates while keeping them concise.
  • JS and CSS to make the controls page.
  • A definition for the bigComposite (and MethBase2-related tracks) in simpleTracks.c
  • A function to generate the controls html in hgTrackUi.c
  • Test data/instructions can be found in the README in bigComposite dir.
$ git diff --name-status upstream/master HEAD
A       src/hg/bigCompositeUpdate/README.md
A       src/hg/bigCompositeUpdate/bigCompositeUpdate.c
A       src/hg/bigCompositeUpdate/makefile
M       src/hg/hgTrackUi/hgTrackUi.c
M       src/hg/hgTracks/simpleTracks.c
A       src/hg/htdocs/style/bigComposite.css
A       src/hg/js/bigComposite.js
M       src/hg/makefile
M       src/lib/htmshell.c

(EDIT: the README mentions a script to help make test data. I forgot to include it but I put it at https://smithlabresearch.org/data/sample_bigcomposite.py if needed.)

…d a helper parseDataTypes. Also added a condition in specificUi to catch tdb->type bigComposite and generate the UI, along with an extra condition to avoid calling hCompositeUi when the type is bigComposite
… 'bigComposite'; also types 'hmr', 'levels' and 'reads' used by MethBase2. These are checked and set 'fillInFromType'.
…d dataTables.select plugins, needed by bigComposite.js
…wo lists but probably only one was appropriate...
…e-embedded data so the JS knows the identifier on possibly-cached metadata
…e-embedded data, which comes from the track name for the bigComposite
…metadata (any url that's not CORS blocked) and encoding it in the settings for the bigComposite trackDb entry
…ute, ensuring that at least two values are present. Also made attributes in the settings from the metadata JSON file lowerCamel to match
…the color-related information is present/complete in the settings part of the metadata, and preventing things from going crazy if the max number of checkboxes is not defined by the user
…config information is all stored in the trackDb.settings longblob; color information is optional and if used needs a json file to define colors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant