experiments/outline-editor/editor.js

@@ -362,7 +362,6 @@ var attributes = {
 // - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -      
 
 // XXX handle cursor marker...
-// XXX do button naviigation a-la tasks...
 var templates = {
 	__proto__: plugin,
 

experiments/outline-editor/index.html

@@ -164,29 +164,27 @@ var setup = function(){
         |text|text|text|
   -
 - ## ToDo:
-  - ASAP Basic standalone client (file-oriented)
-    - _The main idea is to provide a minimal usable app with syncable (externally) 
-	  data_
-    - _Use to write/maintain docs for self_
-    - Levels::
-      - PWA (shared api)
-        - ASAP Conflict resolution
-          - merge two versions
-          - identify conflicts
-        - ASAP localStorage
-        - ASAP FileSystemAPI (???)
-          - see:: 
-            - https://developer.chrome.com/docs/capabilities/web-apis/file-system-access
+  - ASAP Basic standalone client
+    - _the main idea is to provide a minimal usable app with syncable data_
+    - basic pwa (shared api)
+	  - localStorage
+	  - FileSystemAPI
         - is this usable???
           ...this boils down to if we need to ask for access every run or
-              once per install, if it's the former this API is essentially 
-              unusable... 
-        - Nextcloud / WebDAV (???)
-          - _how expensive is it to do a nextcloud plugin???_
-      - Desktop / electron app
-        - fs
-      - Mobile / cordova app (???)
+         onse per install... 
+	  - Nextcloud (???)
+	- electron app
+	  - node fs
+	- cordova app
 	  - fs
+  - Standalone client
+    - basic
+      - file-oriented
+    - mid
+      - logseq-like???
+    - advanceed (pWiki)
+      _this needs thought -- either integrate into pWiki or the other way
+      around_
   - Item templates:
     - ASAP keyboard actuation (a-la checkboxes)
     - inline DONE
@@ -873,4 +871,4 @@ var setup = function(){
 
 </body>
 </html>
-<!-- vim:set ts=2 sw=2 expandtab nowrap : -->
+<!-- vim:set ts=4 sw=4 nowrap : -->