You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO, the c-ide document would be easier to read were it divided somehow by the helm vs. gtag options chosen by the user.
I made a first shot at a solution, by lining up parallel sections side-by-side using simple raw html table tags, which did read well, but presented poorly because the table was forced to width greater than 100% of my screen, and passed the two-tone background of the page.
Now that I know more about how the html is generated, maybe the solution already exists as an ox- option / function / script?
A second idea would be to have color-coded vertical margin stripes for the option being discussed, with the stripes occupying different column positions, for the silent mono-chrome minority among us. I guess that would be a css class definition.
The text was updated successfully, but these errors were encountered:
IMO, the c-ide document would be easier to read were it divided somehow by the helm vs. gtag options chosen by the user.
I made a first shot at a solution, by lining up parallel sections side-by-side using simple raw html table tags, which did read well, but presented poorly because the table was forced to width greater than 100% of my screen, and passed the two-tone background of the page.
Now that I know more about how the html is generated, maybe the solution already exists as an ox- option / function / script?
A second idea would be to have color-coded vertical margin stripes for the option being discussed, with the stripes occupying different column positions, for the silent mono-chrome minority among us. I guess that would be a css class definition.
The text was updated successfully, but these errors were encountered: