Edgewall Software
Home
Trac
Trac Hacks
Genshi
Babel
Bitten
Home
Download
Documentation
Mailing Lists
License
FAQ
Search:
Login
Preferences
Help/Guide
About Trac
Wiki
Timeline
Roadmap
Browse Source
View Tickets
New Ticket
Search
Context Navigation
-1
Start Page
Index
History
Editing TracDev/Proposals/AdvancedWikiOperations
Adjust edit area height:
8
12
16
20
24
28
32
36
40
Edit side-by-side
= Discussing Advanced Wiki Operations = The Trac wiki currently lacks some advanced features you can find in more mature wikis, operations like '''rename''', '''copy''' and '''merge'''. This will summarize and expand the proposals found in #1106 and other places. == Operations === Rename See WikiRename. === Copy Mainly interesting if supporting ''batch'' copies, a.k.a. Subversion style branching. === Merge See #152. The attachment `rename` methods from WikiRename will also be relevant for this operation. == 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_%28Scouting%29 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 * I can see this useful for Trac itself, comparing 0.11 and 0.12 versions of a page. Current wiki diff link is: {{{ http://trac.edgewall.org/wiki/TracLinks?action=diff&version=76&old_version=75 }}} Possible suggestion: {{{ http://trac.edgewall.org/wiki/TracLinks?action=diff&version=76&old_page=wiki/0.11/TracLinks/&old_version=75 }}} 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 ;-) Now that we have MultipleRepositorySupport and "unlisted" repositories `(hidden = true)` for those who would prefer that ancillary repository to remain invisible, this is increasingly becoming a more realistic option. (rblank) I agree with that. Even more, I would like to be able to have the source code, wiki ''and tickets'' in a single DVCS repository, so that I can take the whole thing on the road. Something along the lines of [http://www.fossil-scm.org/ Fossil]. I guess the most difficult part is creating a GUI for merging that is simple enough. == 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).
Note:
See
WikiFormatting
and
TracWiki
for help on editing wiki content.
Change information
Your email or username:
E-mail address and name can be saved in the
Preferences
Comment about this change (optional):
Note:
See
TracWiki
for help on using the wiki.