Mobile: Network Mapper gains touch authoring (#1468) Ed asked for the palette drag after LAYER 31 shipped read-only, so the module page grows a section for it and the scope statement at the top is corrected rather than rewritten - the original reasoning is what shaped what got built. - Mobile-Friendly-Network-Mapper: 'Ed asked for the drag anyway' - all three gestures, why the second and third are not extras, why it does not use the HTML5 drag §22 pointed at, the 320ms long press, the iOS callout guard, and how it was verified on a throwaway diagram. - Mobile-Friendly + Techniques: status row, LAYER 31 row and the seventeen-modules line brought in line. - Techniques §22: a declined-for-no-undo scope is rarely answered by shipping it as it was - build the undo alongside it; and a hand-rolled touch drag CAN be driven headlessly where a native one cannot.
Mobile-Friendly: Network Mapper (LAYER 31), the 17th module New page for the round, plus: - Mobile-Friendly: status rows for Network Mapper and Process Mapper (the latter had shipped without one), the 'canvas stays desktop-first' line corrected to split reading from authoring, seventeen-modules count, and the LAYER/page-count reference. - Techniques: LAYER 31 reference row; §22 gains 'this section answers a narrower question than it looks' (a drag that fires is not a feature that works - ask what the user does if they get it wrong); §23 gains 'flex-grow is inert when the row is already full'; two quick lessons - a dvh split only works when the two halves are the whole viewport, and making a control bigger also makes it easier to hit by accident.