Metaprogramming

[raineorshine]

• Use Export as JSON (simple) to parse. See Export JSON #289.

This is an initial formalization of metaprogramming in em. That is, programming from within em itself self-reflectively operating on the content of em. With metaprogramming, features of em can be implemented in em: Settings is just another context with thoughts like “Theme” it “Font Size” that can be edited directly. Recently Edited Thoughts is just another context. It’s similar to how Search already works, except we are adding templates, type validation, and command triggers so that users can create their own dynamic and interactive contexts. This moves closer to the vision of em’s contextual data model as a universal sensemaking structure.

Requirements

• Namespacing
  • Functions start with =
  • Manually exclude descendants of functions from context views and search
  • Otherwise allow signifier conflicts and do not enforce strict namespace (eventually may want the ability to seerch or view in contexts)
• Syntax Sugar
  • “:” and “()” == nesting

Functions

• Hidden
  • Hides context and all descendants from:
    • search
    • context views
• Immutable (?)
  • Do not allow subthought to be modified
• Readonly
  • Names
    • Fixed
    • Permanent
  • Do not allow context to be deleted or the signifier edited
• Type
  • Options
    • Boolean
    • Link
    • Options
    • String (default)
  • Validation
    • “Warning: Invalid value. Expected X or Y”