Changes between Version 13 and Version 14 of TracDev/Proposals/AdvancedWikiOperations

Timestamp:

Jun 24, 2010, 9:22:50 AM (14 years ago)

Author:

Christian Boos

Comment:

restructure page, add an outline

TracDev/Proposals/AdvancedWikiOperations

@@ -1 +1 @@
 = Discussing Advanced Wiki Operations =
-
+[[PageOutline(2-3)]]
 The Trac wiki currently lacks some advanced features you can find in more mature wikis, operations like '''rename''', '''copy''' and '''merge'''.
 
@@ -13 +13 @@
 === Rename
 
-See WikiRename.
+Basic renaming was implemented for 0.12, but this feature can be enhanced further. See WikiRename. 
 
 === Copy
@@ -42 +42 @@
 Note that this advanced conflict resolution method would also benefit to ''other'' kind of resources, in particular #7145 (not to mention the possibility to merge tickets, in case of duplicates for example - #3006).
 
-== User Interface
-
-The advanced operations should not clutter the wiki page. 
-Instead of ''Copy'' and ''Merge'' buttons coming in addition to the ''Rename'' one, maybe a single ''Advanced...'' button would be preferable. 
-This could go to a single page containing the different forms, one for each advanced operation. Plugins could add their own advanced operation there.
-
-{{{
-#!comment
-Some of the following two items were mentioned in TracDev/ReleaseNotes/0.13#OutstandingWiki - which linked to here - but were not listed here)
-}}}
-== Section Editing
-Many wiki's allow you to edit paragraphs or sections (while leaving the rest of the page un-edited. For example:
- * [http://en.wikipedia.org/wiki/Section_editing#Section_editing Edit Links in Wikipedia]
-
-See also #1024.
-
-== Better Hierarchy Navigation
- * In 0.12 we introduced the wiki page name ''path'' trail, visible in the top left corner of the page, which makes it easy to quickly navigate to any ancestor (#8857). But it would be nice if this could be used to navigate to children and, perhaps, siblings.
-   - if there are children, the path trail would end with a `...` link, leading to a page list (URL could be `/wikilist/<wikipath>`). If Javascript is enabled, the link could be disabled and replaced by an action that would query that same list with an XHR and display a selection list (or a more elaborate form of menu; but a simple <select> would probably do).
-   - the same could be done for siblings actually, by turning each '/' path separator into a similar link
-
-{{{
-#!comment
-Some other ideas - feel free to remove delete or vilify as necessary
-}}}
-
-== Compare different Wiki pages
+=== Diff
+Compare different Wiki pages
  * I can see this useful for Trac itself, comparing 0.11 and 0.12 versions of a page. 
 Current wiki diff link is:
@@ -79 +54 @@
 }}}
 
-This would belong under 'Advanced Operations' I guess?
-Possibly, yes.
 
 But along with the TracDev/Branches/WikiBlame idea (and even the copy operation), I can't help but note that this would come for free if we had #1132 support ;-)
@@ -88 +61 @@
  (cboos) See also related discussion in DistributedTrac and above, in [#Merge].
 
-== Comments per paragraph
+=== Edit
+
+==== Section Editing
+Many wiki's allow you to edit paragraphs or sections (while leaving the rest of the page un-edited, like [http://en.wikipedia.org/wiki/Section_editing#Section_editing Edit Links in Wikipedia], for example. See also #1024.
+
+
+==== Comments per paragraph
  * Maybe this does not belong in Trac and should be plugin instead - but the neatest way of collecting user feedback I have ever seen was the Django book http://www.djangobook.com/about/comments/.
 
-Nice idea. I can try to make [#SectionEditing] a `tracopt.*` optional component, which should then make it easier to implement such a thing as a plugin (or another `tracopt.*` component eventually).
 
 
+== User Interface
+
+The advanced operations should not clutter the wiki page. 
+Instead of ''Copy'' and ''Merge'' buttons coming in addition to the ''Rename'' one, maybe a single ''Advanced...'' button would be preferable. 
+This could go to a single page containing the different forms, one for each advanced operation. Plugins could add their own advanced operation there.
+
+=== Better Hierarchy Navigation
+
+In 0.12 we introduced the wiki page name ''path'' trail, visible in the top left corner of the page, which makes it easy to quickly navigate to any ancestor (#8857). 
+
+It would be nice if this could be used to navigate to children and, perhaps, siblings:
+   - if there are children, the path trail would end with a `...` link, leading to a page list (URL could be `/wikilist/<wikipath>`). If Javascript is enabled, the link could be disabled and replaced by an action that would query that same list with an XHR and display a selection list (or a more elaborate form of menu; but a simple <select> would probably do).
+   - the same could be done for siblings actually, by turning each '/' path separator into a similar link
+
+
+