From e5cbea854c87a32516458c511d9db337b4d66e29 Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Sun, 21 Aug 2022 13:10:36 +0300 Subject: [PATCH] notes... Signed-off-by: Alex A. Naanou --- pwiki2.js | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/pwiki2.js b/pwiki2.js index 08bead4..73298ab 100755 --- a/pwiki2.js +++ b/pwiki2.js @@ -1,6 +1,43 @@ /********************************************************************** * * +* XXX track requested paths in render state.paths... +* ...this would be useful for dependency tracking and cache +* management/invalidation... +* ...would also be useful to have a parse mode that would only +* track paths -- is this practical??? +* XXX need a uniform way to track state in pwiki for things like paging +* and the like with simple user/macro access... +* ...the simplest that comes to mind is to store in in path +* somehow: +* - ?=&... +* traditional "query string"... +* - /:/:/.../ +* stack-style arguments... +* + simple to implement +* - goes thrugh page search??? +* - ::=:... +* - ... +* the general idea is to be: +* - flexible enough to allow the basics done +* - restrictive enough to prevent missuse +* ...the rest of the state can simply be stored in the root pwiki +* object in one of the following ways: +* - directly (attrs/dict) +* - a special page +* - virtual (path-specific) +* e.g. +* /some/path/@state/page -> 4 +* ...might be fun to implement a basic json editor +* and viewer with this api... +* ...controlled via js +* ...or special actions: +* /some/path/@state/page/next (increment) +* /some/path/@state/page/prev (decrement) +* /some/path/@state/page=10 (assign) +* ... +* - session +* - stored (config) * XXX GENERATOR make pattern path parsing a generator... * ...experiment with a controllable iterator/range thing... * This would require: