Ferreteria/v0.6/clade/IO/O/Data

From Woozle Writes Code
< Ferreteria‎ | v0.6‎ | clade‎ | IO‎ | O
Jump to navigation Jump to search
namespace: IO\O\Data
Subpages

About

  • Purpose: abstract classes for specifying layout - no rendering code
    • Podlings in [WF]IO/O/Render/*/ do the rendering. Styles do most of the rendering now, but there's a lot of structural interplay with these clades.

Terminology

  • "tree" (lowercase) contains folders organized around node-hierarchy (not layout)
    • "branch" is for objects that have a parent-node (i.e. are not the root)
    • "root" is for objects that have no parent-node
  • "Indent" is for objects that have indentation in their layout
  • "grid" is for objects that are arranged in a grid, and clades for managing that layout

History

  • 2024-10-20 Eliminated the "Screen" layer ([WF]IO/O/Screen/Layout -> [WF]IO/O/Layout) because it became redundant -- these clades could also be used for rendering to print, via another type in the [WF]IO/O/Render folder.
    • [THINKING] The folder and class-structure layout for this got ugly pretty quickly, because there are multiple dimensions that we're trying to keep track of:
      • tree structure
      • class/code structure
      • other commonalities/relationships in certain sub-families (indentation, table structure)
  • 2024-10-21 [THINKING] I may have just completely reversed some of what I did yesterday... It makes no sense to today!me to have `/root/` and `/branch/` folders that are separate from the `/Element/` Root and Branch namepace-hierarchy when the classes in the former folders are in fact podlings of the latter.
  • 2024-10-22 xTODO We should probably have single-line classes (which would support indentation) and block-level classes (which wouldn't).
    • A table would be a block; a table-row might be a single-line, unless the cells are multi-row...
  • 2026-01-28 I'm reworking these and the Style classes to make more sense. A lot of what this page describes has been moved into Element.

Pages