From 152fd92e0fe9d090c20ffc31de36b77e7b35ddc8 Mon Sep 17 00:00:00 2001
From: "Alex A. Naanou" <alex.nanou@gmail.com>
Date: Wed, 10 Aug 2022 18:21:00 +0300
Subject: [PATCH] notes...

Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
---
 pwiki2.js | 48 +++++++++++++++++++++++++++++-------------------
 1 file changed, 29 insertions(+), 19 deletions(-)

diff --git a/pwiki2.js b/pwiki2.js
index 8cd67a4..190a35d 100755
--- a/pwiki2.js
+++ b/pwiki2.js
@@ -2,22 +2,6 @@
 * 
 *
 * XXX BUG: .get('/*').raw hangs...
-* XXX RELATIVE relative urls are a bit odd...
-* 			Path/to/page opens Moo	-> Path/to/Page/Moo
-* 		should be (???):
-* 			Path/to/page opens Moo	-> Path/to/Moo
-* 		this boils down to how path.relative(..) works, treating the base
-* 		as a directory always (current) vs. only if '/' is at the end, on 
-* 		one hand the current approach is more uniform with less subtle ways
-* 		to make mistakes but on the other hand this may introduce a lot 
-* 		of complexity to the user writing links, e.g. how should the 
-* 		following be interpreted?
-* 			page: /SomePage
-* 				link: SomeOtherPage
-* 					-> /SomeOtherPage
-* 					-> /SomePage/SomeOtherPage (current)
-* 		the current approach does not seem to be intuitive...
-* 		can this be fixed uniformly across the whole system???
 * XXX add action to reset overloaded (bootstrap) pages...
 * 		- per page
 * 		- global
@@ -38,9 +22,17 @@
 * 		- store topology
 * 	- markdown										-- DONE??
 * 	- WikiWord										-- DONE
-* 	- dom filters									-- DONE
-* 		- wikiword									-- DONE
-* 		- path2link (wikiword?)						--
+* 	- dom filter mechanics							-- DONE
+* 	- filters / dom filters:
+* 		- wikiword (control)
+* 			this can be done in one of two ways:
+* 				- wrapping blocks in elemens
+* 					...requires negative filter calls, either on -wikiword 
+* 					or a different filter like nowikiwords...
+* 				- tags (current)
+* 		- raw / code
+* 		- nl2br
+* 		- path2link (wikiword?)			
 * 		- editor
 * 	- configuration
 * 		- defaults
@@ -122,6 +114,24 @@
 * 		- in this view a user in the system is simply a set of keys and 
 * 			a signature (a page =))
 *
+* XXX RELATIVE relative urls are a bit odd...
+* 			Path/to/page opens Moo	-> Path/to/Page/Moo
+* 		should be (???):
+* 			Path/to/page opens Moo	-> Path/to/Moo
+* 		this boils down to how path.relative(..) works, treating the base
+* 		as a directory always (current) vs. only if '/' is at the end, on 
+* 		one hand the current approach is more uniform with less subtle ways
+* 		to make mistakes but on the other hand this may introduce a lot 
+* 		of complexity to the user writing links, e.g. how should the 
+* 		following be interpreted?
+* 			page: /SomePage
+* 				link: SomeOtherPage
+* 					-> /SomeOtherPage
+* 					-> /SomePage/SomeOtherPage (current)
+* 		the current approach does not seem to be intuitive...
+* 		can this be fixed uniformly across the whole system???
+* 		XXX document this!
+*
 * XXX need to think about search -- page function argument syntax???
 *
 * XXX might need to get all the links (macro-level) from a page...