SrEd2
iType = Action. ; one of these (named for the next Time period) could be a useful addition to many Contexts. ; SrEd0 SrEd1 SrEd2 SrEd365

The secondary Summary text could be a Node of a specific iType.


EdD3: ( string5 string.5 ).test

  • Should this idea be moved to a different Parent?
  • ...

 

SrEd2:

  • z14 is an example of a search target string.
    • debateGraph requires these strings to be complete (within whiteSpace, as opposed to being subStrings like most other programs).

SrEd1:

  • the History capability provides an adequate Activity log.

SrEd0:

  • (meaningful variable) Names are increasingly important as systems grow.
    • SrEd documentation that needs to be submitted may be more effective in gDocs simply because of the imposed restrictions.
  • ...
    • Findings ( TU realizations & investigations ) ;
    • Conclusions ( What was done ) ;
    • Achievements ( Actionable Recommendations reducing Uncertainty ; Confirmations )
  • confirmed that Search is effective (even in Summary fields)
  • this allows NamesH consistency in another toolContext
    • toolContext gains importance.
  • it may be worth documenting the impacts of caseSensitive searches
  • test the leftAngleBracket hack to determine its reliability

  • Build various demonstrations that incorporate this tool to compare and contrast its relative value.
  • strive to structure effective Page Views that may help in any Review process.
  • Should this page be renamed or should it be linked into a timeLine?
  • ...

^

Immediately related elementsHow this works
dotCommands »dotCommands
TweTt = .we = -w18 = ? »TweTt = .we = -w18 = ?
TweTn »TweTn
汇 = (work)Flow »汇 = (work)Flow
Productivity »Productivity
SrEd2
+Komentarai (0)
+Citavimą (0)
+About