Last update: Mon, Sep 5, 2011 at 7:18 AM.
Getting tables sorted out
undefined
  • I'm using the Bootstrap toolkit from Twitter, specifically the zebra-striped table format.
  • The tables should have a <thead> and <tbody>. In <thead> is a <tr> with <th> elements.
  • The <tbody> is just the normal table body stuff. <tr>s with <td>s within.
  • log2.view
    • Add <thead> and <tbody> elements. Eliminate the "oddrow" class on every other row. This can be done in the stylesheet (and is). If the cache is turned off don't store the text in the log item.
  • opmleditor.viewCatalog
    • In the column headers, use <th> elements instead of <td> elements. Want to get absolute consistency here. Remove <b> elements from the text in the <th> elements.
    • And when I did this, the bold border at the top of the table appeared as in the log table. So now when we get rid of it in one place presumably it will go away in the other.
    • And when we do tables anywhere, let's do it the same way. That way we can change them all by just changing builtins.webapp. Yes!
  • General note: Be sure to update opml.root when you manually update any of the tools. Very often there are changes to core code when the tools are getting updates. You don't have to worry about this with automatic nightly updates, only when you do it "by hand."