summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-09-22 17:46:50 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-09-22 17:46:50 +0000
commitae3c65f93458be6136a82b4ad04b967c00c44b63 (patch)
treeb10afbe13fd1cda7c8490c61c4532adbdf3c7fb6 /doc
parentd0b1b244281102a07f675880c401ca831ff113d4 (diff)
responsen
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn10
-rw-r--r--doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn25
2 files changed, 31 insertions, 4 deletions
diff --git a/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn b/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn
index 0083e84e5..c241e1673 100644
--- a/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn
+++ b/doc/todo/Location_of_pages_starting_with___36__tagbase_should_be_in__by_default.mdwn
@@ -1,3 +1,9 @@
-If I click on a tag that does not yet have a name, but `$tagbase` is set, it would be nice if the location suggested is `$tagbase/<tagname>`, not a subpage: `<current>/$tagbase/<tagname>`.
+If I click on a tag that does not yet have a name, but `$tagbase` is set,
+it would be nice if the location suggested is `$tagbase/<tagname>`, not a
+subpage: `<current>/$tagbase/<tagname>`.
-[[tag wishlist]] \ No newline at end of file
+> This only seems doable if the tag link you click on is in the "Tags:"
+> footer, or is added with a taglink directive. Think that's good enough?
+> --[[Joey]]
+
+[[tag wishlist]]
diff --git a/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn b/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn
index 3873a96b2..998d7f0c2 100644
--- a/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn
+++ b/doc/todo/Suggested_location_should_be_subpage_if_siblings_exist.mdwn
@@ -1,3 +1,24 @@
-Given a page `/foo` and a subpage `/foo/bar`, if I add a link to `baz` to `/foo` and click on the link to create the page, the suggested location should be `/foo/baz` instead of `/baz`. The rationale is that presence of a sibling folder, or sibling pages (with `usefolders=0`) is a strong hint that we're at the root of a (sub-)hierarchy.
+Given a page `/foo` and a subpage `/foo/bar`, if I add a link to `baz` to
+`/foo` and click on the link to create the page, the suggested location
+should be `/foo/baz` instead of `/baz`. The rationale is that presence of a
+sibling folder, or sibling pages (with `usefolders=0`) is a strong hint
+that we're at the root of a (sub-)hierarchy.
-[[tag wishlist]] \ No newline at end of file
+> I think there's something to be said for consistency, even if it doesn't
+> make the best guess every time. It makes it more easy to learn when
+> you do need to change the location, and learn when default works.
+>
+> In your example, to get the foo/bar page created, you'd need to remember
+> to change the default when creating that subpage. But only for the first
+> subpage, after that it would get the default right. But who can remember if
+> a particular page has a subpage already? You end up having to check every
+> time anyway. Plus, you'd have to check every time you wanted to create "bar"
+> from "foo" that it didn't guess you meant "foo/bar".
+>
+> With the current simple default, you at least
+> know you don't need to check in that fairly common case, which seems like
+> a win over your suggestion.
+>
+> IMHO, what you really want is [[Moving_pages]]. :-) --[[Joey]]
+
+[[tag wishlist]]