Edgewall Software

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


Ignore:
Timestamp:
Jun 24, 2010, 9:22:50 AM (10 years ago)
Author:
Christian Boos
Comment:

restructure page, add an outline

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/Proposals/AdvancedWikiOperations

    v13 v14  
    11= Discussing Advanced Wiki Operations =
    2 
     2[[PageOutline(2-3)]]
    33The Trac wiki currently lacks some advanced features you can find in more mature wikis, operations like '''rename''', '''copy''' and '''merge'''.
    44
     
    1313=== Rename
    1414
    15 See WikiRename.
     15Basic renaming was implemented for 0.12, but this feature can be enhanced further. See WikiRename.
    1616
    1717=== Copy
     
    4242Note 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).
    4343
    44 == User Interface
    45 
    46 The advanced operations should not clutter the wiki page.
    47 Instead of ''Copy'' and ''Merge'' buttons coming in addition to the ''Rename'' one, maybe a single ''Advanced...'' button would be preferable.
    48 This could go to a single page containing the different forms, one for each advanced operation. Plugins could add their own advanced operation there.
    49 
    50 {{{
    51 #!comment
    52 Some of the following two items were mentioned in TracDev/ReleaseNotes/0.13#OutstandingWiki - which linked to here - but were not listed here)
    53 }}}
    54 == Section Editing
    55 Many wiki's allow you to edit paragraphs or sections (while leaving the rest of the page un-edited. For example:
    56  * [http://en.wikipedia.org/wiki/Section_editing#Section_editing Edit Links in Wikipedia]
    57 
    58 See also #1024.
    59 
    60 == Better Hierarchy Navigation
    61  * 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.
    62    - 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).
    63    - the same could be done for siblings actually, by turning each '/' path separator into a similar link
    64 
    65 {{{
    66 #!comment
    67 Some other ideas - feel free to remove delete or vilify as necessary
    68 }}}
    69 
    70 == Compare different Wiki pages
     44=== Diff
     45Compare different Wiki pages
    7146 * I can see this useful for Trac itself, comparing 0.11 and 0.12 versions of a page.
    7247Current wiki diff link is:
     
    7954}}}
    8055
    81 This would belong under 'Advanced Operations' I guess?
    82 Possibly, yes.
    8356
    8457But 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 ;-)
     
    8861 (cboos) See also related discussion in DistributedTrac and above, in [#Merge].
    8962
    90 == Comments per paragraph
     63=== Edit
     64
     65==== Section Editing
     66Many 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.
     67
     68
     69==== Comments per paragraph
    9170 * 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/.
    9271
    93 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).
    9472
    9573
     74== User Interface
     75
     76The advanced operations should not clutter the wiki page.
     77Instead of ''Copy'' and ''Merge'' buttons coming in addition to the ''Rename'' one, maybe a single ''Advanced...'' button would be preferable.
     78This could go to a single page containing the different forms, one for each advanced operation. Plugins could add their own advanced operation there.
     79
     80=== Better Hierarchy Navigation
     81
     82In 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).
     83
     84It would be nice if this could be used to navigate to children and, perhaps, siblings:
     85   - 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).
     86   - the same could be done for siblings actually, by turning each '/' path separator into a similar link
     87
     88
     89