Archive Trac docs layout integration notes

Docs Layout Integration Notes

Legacy Trac archive page imported from docs_layout_integration_notes. Source: https://genapp.rocks/wiki/wiki/docs_layout_integration_notes. Review age, links, and examples before treating as current.

new layout integration notes

• role is extension

  • primary interest is .input & .output for loops on fields:id

• need to maintain backward capability

• place for buttons

  • default location

• as-is

  • builds table for input & output

• new way ...

  • types build data structures
  • layout.js / ga.layout.show()
  • reads data structures
  • inserts buttons
  • related evals

• testing:

  • layout data from module.html run thru command line node to produce html

• starting with

  • energy.json
  • types:
    • label.input
    • float.input
    • text.output
    • button.input

• genapp/tmp/layout/layouttest.js

  • extracts ga.layout marked lines from genapp generated html for module, outputs html

nb

• $.show() seems broken under bootstrap, check for this!

done

• [done] add layout call to display
• [done] get buttons functional
• q: how do we add fields in ga_layout.pm and push to insertions?
• a: layout.js
• [done] remove

  ---

  , other cleanup (move to input area - genapp/etc/perl/ga_layout.pm)
  • [done] input.footer
  • {{{__moduleid___progress}}}
  • [done] output.header
  • {{{__moduleid___output_msgs}}}
  • {{{__moduleid___output_airavata}}}
  • {{{__moduleid___output_textarea}}}
• [done] data.js hmod_out
• add bootstrap classes
• [done] "genapp" theme
• [done] with material-design-theme
• [done] separate package.json's in case of conflicting dependencies
  • [done] color issues
• [done] bootswatch
  • [done] possibly reconstruct directives:bootstrap
• [done] add __! logic
• get redisplay of fields working properly
  • e.g. msgs, textarea
  • value.js
    • docs_value_js
  • reevaluate code for this and write up save, restore field info
  • note we had output as a separate form before...

todo 2019/08/13

• add more field types
  • perhaps prioritize modals
  • then plotting
  • it might effect layout
• test limits (e.g. type integer, min/max etc)
• warning message clears
• test calc
• test airavata message output
• redo repeaters
• test reattach
• add

  ---

  back ?

  • filter out "out" from submit

  • take button colors and more text colors from themes

  • add bootstrap icon with theme info?

  • add remainder of field inputs/outputs

  • user theme choice

  • reset css https://coderwall.com/p/n6k6bq/reset-css-to-browser-defaults

  • panel "boxes" (e.g. output)

  • panel "scrolling regions" (e.g. input vs output)

  • bootstrap sideways sliders (e.g. multiple plots or detailed input ...)

  • repeaters in sliding window?

old todo 2019/07/15

• working in sga:~/tutorial2
  • add back default

    ---

  • fix textarea, msgs, airavata layout positions
  • not getting dgr, dgc, lgr, lgc for these added fields
  • resurrect layout tester
  • layout generator ?
  • more textarea fixes:
  • $.show didn't work with bootstrap :(
    • converted to js document...removeAttribute(hidden)(style)
    • textarea width
    • textarea (and progress etc) panel when not just a root panel
    • in ga_layout.pm when setting up panels
    • cases:
      1. only root panel, no b_submit ... current default is ok?
      2. only root panel, b_submit specified ?
      • place controls(outputs) after b_submit, b_reset
      1. multiple panels no b_submit ?
      2. new "controls" panel?
      3. multiple panels b_submit specified
      • if controls panel exists, append to that
      • o.w. add below b_submit, b_reset

older todo

• add buttons

1. buttons at bottom
2. buttons in before 1st output - going to need to do this in ga_layout.pm - cssgrid finds the 1st unassigned cell for entries without explicit grid coordinates
3. buttons explicitly defined in module

• maybe special "button" type only takes one cell (w/o label)

• button row by default? (auto, auto)

• possibly, default panels root, top(input), buttons, bottom(output) ?

• add

  ---

  spanning row

issues

• not satisfied with button placement
  • possibly special row layout for buttons?
  • button panel without grid?
• one form
• cursor increment issue
• repeaters & absolute layout
  • perhaps add spacing since empties are not displayed
  • e.g. +100 for a big gap