Jul 032015
 

NQVDRD:   “intro & overall”

  1. NQVDTX:  “The “terms of use” of {this post & its comments, including the privacy & confidentiality of it plus all knowledge obtained from it} is JotHere’s standard Terms of Use except:
    1.  NQVDUA:  none.
      TBA
  2. NQVDUJ:  “post name history in reverse start-order”
    1. NQVDUR:  now originally to next: “{CSS(Cascading Style Sheets) & related JavaScriptstumbling points, by DestinyArchitect
    2. NQVDYB:  “per post name, add post to categories”
      1.  NQVDYT:  ‘CSS LXM2QF
      2. NQVE1M:  ‘JavaScript NQVCR2
      3.  NQVDYK:  ‘DestinyArchitect creation N0L9VW
  3.  NQVN42:  overall
    1.  I use it
      1. ..
    2.  
  4. NQVE3M:  formatting & styling
    1. NQVPCB:  –while the particular solutions here are geared to the topic of this post (CSS & related JavaScript) as that is the by far most popular & generally most powerful environment today, the organization & concepts of this section are applicable to most any text formatting environment.
    2. NQVIUP:  ‘display size’: common display size
      1. NQVIWV:  vastly affects this
      2. NQVIV1:  ‘small display now’
        1. NQVJ1T:  shrunk substantially ~2014 due to the normal web browser becoming the mobile device
          1. NQVJ0J:  which is  smartphones & {tablets of size between phone and about 80% smaller than laptops}
    3. NQVE4D:  managing extra including excessive detail
      1. NQVEXJ:   to support & allow content containing extra detail
        1. NQVE7Q:  can & does dramatically help
          1. NQVE8S:  especially as far as quantity then possible:
            1. NQVEAF:  as for text, maybe up to 50x more
            2. NQVEBP:  as, for graphics heavy, maybe up to 10x more
          2. NQVQZW:  so key for efficient writing on variety of subjects each in considerable depth
            1. NQVR2X:  so 1st off for my writing
            2. NQVR5J:  as for notably best writing efficienty, except for limited types of posts, general posts seem best at 50 to 500 points, but but then it’s easy to “not be able to see the forest because of the trees”
        2. NQVFPL:  goal is to make things visiable proportunate to how much the user wants or/and needs to see them
      2. NQVP7Y:  notable examples:
        1. NQVP87:  NQVP87:  formatting for the right column text #M8K00L
        2. NQVPI9:  default formatting for HTML.
        3. NQVPJC:  others.
      3. NQVNL7:  sources of inspiration
        1.  NQVNLK:  almost entirely my own thinking
        2. NQVNLS:  likely possibly from { http://en.wikipedia.org/wiki/Outliner#Browser-based_outliners , from here}
      4. NQVFI8:  via dynamic vs static behavior
        1. NQVF77:  ‘notable pros thru cons:’
          1. NQVFES:  huge pro: dramatic ability/effect
          2. NQVFFN:  pro: entertaining
          3. NQVF7I:  con: ‘prinout support’
          4. NQVF88:  con: being traditional, especially ‘prinout support’
        2. NQVEPP:  via dynamic behaviors:
          1. NQVIJT:  depending on user/reader’s “focus” or/and selection
          2. NQVENC: ‘via dynamic minimizing’:
            1. NQVFU2:  via deemphazing vs. removing-from-display
              1. NQVFEB:  ‘notable pros thru cons:’
                1. NQVG0I:  even if content is unfeatured, still working else make-able to work:
                  1. NQVFVF:  big pro: anchors
                  2. NQVFVT:  big pro: Page Find (as Ctrl-F)
                2. NQVG0W:  con: easily more cluttered-looking
              2. NQVG2M:  via de-emphazing
                1. NQVEDI:  via dynamic shrinking/scaling-down (by notably reducing especially graphic & font size, so display area)
                  1. NQVQDG:  my (re?) invention as just before the start of this post, motivating me to make it.
                  2. NQVQH3:  presently my current hope.
                  3. NQVV50:  via font-size and img width+height %
                    1. NQVV8R:  pro: doable via CSS2 maybe 1
                    2. NQVW7Y:  reference http://stackoverflow.com/questions/787839/resize-image-proportionally-with-css
                    3. NQVW8G:  1st coding: class NQVVFJ in NQVV85
                  4. NQVV61:  via transform scale of https://developer.mozilla.org/en-US/docs/Web/CSS/transform
                    1. NQVVB0:  con: that reference says ‘experimental technology’
              3. NQVG2S:  via removing from display aka hiding
                1. NQVQNB:  collapsing (vs. expanding)
                  1. NQVECT:  via truncating partially to fully
                    1. NQVOOQ:  for natural language, called ‘Expose/ hide levels’ in Wikipedia
                    2. NQVQQB:  for computer languages, called code folding
          3. NQVLTG:  via bread-crumb generation/maintenence
            1. NQVLUL:  ‘notable pros thru cons:’
              1. NQVLVW:  PRO: seems definitely-else-nearly essential for medium to deep levels
                1. NQVLYD:  with the possible exception of having, in one’s path up from the current location, all ancestors’ previous siblings  ‘.. dynamic minimizing’-ed
              2. NQVLX6:  con: requires JavaScript
          4. NQVPR3:  ‘via hoisting’
            1. NQVQ1P:  definition
              1. NQVPUA:  zeros the overall present indent –it’s apparent core goal.
              2. NQVPRI:  defined at https://en.wikipedia.org/wiki/Outliner#Design
            2. NQVPSP:  is a rated feature at https://en.wikipedia.org/wiki/Outliner#Mobile_device_outliners
            3. NQVPZI:  ‘notable pros thru cons:’
              1. NQVQ4R:  notable pro: the effect is essential in many cases
              2. NQVQ47:  small con: may require JS
              3. NQVPZX:  notable con: appears to be better solutions in at least many cases.
        3. NQVEQA:  via static behaviors, from roughly most effective:
          1. NQVECL:  ‘via indenting’
            1. NQVNNZ:  is the most famous aspect of outlines & outliners
              1. NQVU6Z:  this now add this post to category ‘outline (list) NQVTOY’
            2. NQVJQV:  ‘notable pros thru cons:’
              1. NQVJRY:  huge pro: can be a huge help
              2. NQVJSG:  pro: familiar
              3.  NQVI1N:  ‘easily-big con’: costly, easily prohibitively, if 2 or more, from decreasing problematic:
                1. NQVJHJ:  substantial indent of each level
                  1. NQVOX9:  (so) minimizing indent
                2. NQVI85:  narrow width ‘display size’ (which is now common)
                3. NQVI7C:  ‘(via indenting) the whole text block (not just 1st line)’
                4.  NQVI7N:  more than a few nesting levels (which is common)
            3. NQVP5F:  indent amount
              1. NQVOYN:  ‘indent amount of each level’
                1. NQVP07:  substantial can cause problems
                2. NQVP4N:  minimizing
                  1. NQVP63:  to near but non 0
                    1. NQVPAP:  top example: NQVP87
                    2. NQVQBV:  my recommendation.
                  2. NQVQ6O:  to 0
                    1. NQVQ6Z:  –effectively removes all ‘via indenting’, so both the pros & cons.
              2. NQVPKF:  ‘indent amount of the particular points being looked at’
                1. NQVPLA:  is generally the ‘indent amount of each level’ times the current level depth.
                2. NQVPML:  minimizing
                  1. NQVPMW:  is not necessary wherever  ‘easily-big con’ is kept in check
                    1. NQVPUW:  to 0
                      1. NQVPQC:  can be done ‘via hoisting’
            4. NQVOVF:  handling many levels of indent
              1. NQVOW9:  via minimal
            5. NQVI0A:  ‘(via indenting) the whole text block (not just 1st line)’
            6. NQVKVO:   1st line vs. all lines indented for ‘.. item/section symbol’
              1. NQVL6B:  this is the extra indent of the content to accomodate the ‘.. item/section symbol’ prefixing it.
              2. NQVLAN:   ‘notable pros thru cons:’
                1. NQVLE9:  Huge pro: generally drastically reduces the total indent.
                2. NQVLAZ:  Notable pro: can accomodate arbitrary sized symbols, notably large count #s, and w/o having inconsistent indents for the remaining lines.
                3. NQVLD4:  con: not default & uncommon
                4. NQVMAI: con: adjacent sibling items won’t always have exactly the same, but still near, indent of their start text when the starter symbol varies in width, including most notably when going from item ‘9.’ to ‘10.’
                  1. NQVMFZ:  but other than small asthetic unplesantness for short text points, this seems not a problem as now the indent is starting at the ‘.. item/section symbol’‘s indent, not the text immediately following it.
              3. NQVKZH:  ‘1st line indent for item symbol’:
                1. NQVLLT:  Notable example: NQVP87
              4. NQVLNS:  ‘all line indent for item symbol’:
          2. NQVFB5:  via generation/maintenenace of an additional {table of contents}
            1. NQVIQ7:  ‘notable pros thru cons:’
              1. NQVIOD:  big pro: can be a big help
              2. NQVFBZ:  small con: requires JavaScript.
              3. NQVIEC:  big con: seems like better can be done ‘via dynamic minimizing’
          3. NQVEFJ:  via bolding key items
          4. NQVET7:  ‘via item/section symbol’
            1. NQVL1L:  have numbering indicating the item position within its list.
            2. NQVJTX:  via having the numbering indicate nesting level level
              1. NQVJX2:  via prefix # vs. numbering alphabet
                1. NQVJXX:  ‘notable pros thru cons:’
                  1. NQVKAO:  huge pro: one needs to know & think a lot less to figure out the level & item sequence
                    1. NQVJZW:  as immediately
                      1. NQVKDD:  names the level (by giving it a number)
                      2. NQVKDL:  tells how deep the level is (by the number)
                      3. NQVKE7:  allows the sequence # to the most familiar alphabet: notably decimal numerals, which everybody well knows the sequence and even how to subtract them.
                    2. NQVKKC:  in contrast, the other method requires quite a bit of knowledge & familiarity
                      1. NQVKL9:  to count in the various alphabets (to know sibling position), and roman numbers & greek letters is tricky.
                      2. NQVKM8:  to be able to identify which alphabet, to know the grouping.
                      3. NQVKMN:  to know which alphabet is  assigned to which depth level (to fast tell the level depth without haveing to infer & count it)
                        1. NQVK8Q:  and (worse) there are few standards there, none well known, with perhaps the most common known by some is the symbols go from capitlized at the upper levels and not at the lower levels, (as A to a and I to i) but even that standard is incomplete.
                  2. NQVJZ5:  pro: readily supports many more levels
                  3. NQVK0E:  con: very unfamiliar
                    1. NQVK37:  indeed I’ve never seen it elsewhere.
                  4. NQVKRD:  con: requires ~3 symbols instead of 1 to ~3 (as ‘3.2′ instead of ‘ii’)
                    1. NQVKUM:  typically not a problem, especially if ‘symbol ident for 1st line only’
                2. NQVJV0:  via telling the level depth followed by the sibling # within that level, both in familiar decimal numbers
                  1. NQVK3W:  my invention 2012~
                3. NQVJUD:  via a different numbering alphabet on each level
          5. NQVEF6:  via enlarging key items, typically headings
            1. NQVJN9:  con: doesn’t seem to well support many levels.
            2. NQVITS:  notable con: somewhat to very bad for small ‘display size’
    4. NQVT3P:  coding practices
      1. N4YJUY:  Seems likely: a CSS selector should ideally NOT refer to an ID (instead say refer to a class and/or tag) because IDs fail when multiple copies are included on the same web page, such as results when we want to display several pages (say in a reduced form or via many widgets) on a single page.
      2. NQVT6X:  handling medium to large amounts of CSS
        1. NQVT7I:  tools
          1. NQVT7Y:  highly recommend Brackets ‘Custom region code folding’ as detailed at point NQU7MR so far in sheet MEY2HI
      3. NQVT4Z:  compatbility
        1. NQVT5A:  http://caniuse.com has best docs I know
  5. NQVOFG:  much more TBA
  6. NQVN9C:  “motivation”
    1. NQVN3O:  1st to help define stylesheet_N4=N4PLGG.css (used to define this site), and can readily be used for many more purposes.
  7.  “success of this”
  8. “author(s) background (on the topic)”

  9. NQVOFR:   “post edits overall history table, by increasing start-time”
    “entry ID” “action” “why” “word cnt”  “ver #” “s#” “date (typ fr earliest ID)”
     
    1. NQVDOP:  ‘{post.status.snapshot: date ’20150702Thu0955pst‘; after ID’ minutes 0~‘; revision ’1‘; words ’208~‘; version ’0‘; as ’stuff to record & ideally share starting with text-collapse-by-shrink‘, do ’“now {via “Copy to a new draft”, so of {then latest post template used by author of similar type, so /4706#NPB9K9}, so of then its latest saved version, so with last entry “/4706#NQRJ4R: ..”} created {this here post, so” http://1.JotHere.com/4795#NQVDRD “} then cut {all its content not to be reused here, so the content just applying to the template, so all the posts’ fully stated points including their KCGUIDs}.”‘}’.
    2. NQVDQL:  adding initial content; fairly complete 1st pass
    3. NQWK19:  ‘{post.status.snapshot: date ’20150703Fri0100pst‘; after ID’ minutes 1~‘; revision ’1‘; words ’1665‘; version ’0.7‘; as ’>500 words added so periodic save‘, do ’Publish‘}’.