flynx/pWiki
1
1
Fork 0
mirror of https://github.com/flynx/pWiki.git synced 2025-12-27 05:01:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

notes...

Browse Source 
Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
This commit is contained in:
Alex A. Naanou 2022-08-10 18:21:00 +03:00
parent b810c625c9
commit 152fd92e0f
1 changed files with 29 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
pwiki2.js
View File

@ -2,22 +2,6 @@
* *
* *
* XXX BUG: .get('/*').raw hangs... * 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... * XXX add action to reset overloaded (bootstrap) pages...
* - per page * - per page
* - global * - global
@ -38,9 +22,17 @@
* - store topology * - store topology
* - markdown -- DONE?? * - markdown -- DONE??
* - WikiWord -- DONE * - WikiWord -- DONE
* - dom filters -- DONE * - dom filter mechanics -- DONE
* - wikiword -- DONE * - filters / dom filters:
* - path2link (wikiword?) -- * - 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 * - editor
* - configuration * - configuration
* - defaults * - defaults
@ -122,6 +114,24 @@
* - in this view a user in the system is simply a set of keys and * - in this view a user in the system is simply a set of keys and
* a signature (a page =)) * 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 need to think about search -- page function argument syntax???
* *
* XXX might need to get all the links (macro-level) from a page... * XXX might need to get all the links (macro-level) from a page...