Opened 20 years ago
Last modified 10 years ago
#1245 new enhancement
Highlight changes of a wiki page since last visit
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | lowest | Milestone: | next-major-releases |
Component: | wiki system | Version: | 0.8 |
Severity: | normal | Keywords: | |
Cc: | kilian.cavalotti@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
- It would be very handy to be able to choose the versions we want to see the diff between. A la moinmoinwiki, see here for an example.
- It would be nice to display the changes of a page since last visit
- It would be nice to have a diff mode where only changes are displayed (not the whole page source), with perhaps a preview of the rendered page below the diff.
Just ideas. :)
Attachments (0)
Change History (9)
comment:1 by , 20 years ago
comment:2 by , 19 years ago
Component: | general → wiki |
---|---|
Priority: | normal → low |
Summary: | Diff display enhancement → Highlight changes of a wiki page since last visit |
- has been implemented in [1973].
- would be nice indeed
- is how wiki diffs work in trunk (0.9-pre)
Adjusting summary to reflect that only 2. is still open.
comment:4 by , 18 years ago
Milestone: | → 2.0 |
---|
(Feature request for point 2. accepted, but no idea when it could be done…)
comment:5 by , 15 years ago
Side Note: Tracking last visit status of an authenticated user or an anonymous user on a per resource basis will boost storage requirements for high traffic sites a lot.
Apart from that, a cookie must be implemented stating when the (anonymous) user last visited the site, if not already done. Based on that cookie, one could track the visits to each page and keep a timestamp with each visit, which will be updated as soon as the user once again visits the page.
I'd like to propose an extra table for tracking individual page/resource visits on a per realm basis, so that we could also implement such a "difference" view for for example the ticket system, the roadmap, the timeline itself and so on.
Implementation should go into the main request handler, as this would be a feature common to all subsystems.
In the configuration I would like to have an option for either enabling or disabling individual realms from being tracked, or even individual resources (considering high volume access to individual resources) or collections thereof being matched by for example a regular expression or wildcard.
E.g.
[tracking] realm.wiki=enable realm.ticket=enable realm.timeline=disable realm.attachment=enable ... resource.disable=/wiki/highvolumetraffic/*
or something like that
comment:7 by , 14 years ago
Milestone: | triaging → next-major-0.1X |
---|---|
Priority: | low → lowest |
comment:8 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
The hardest part would be of course to render the differences in the rendered wiki content, in a way that makes sense.
comment:9 by , 10 years ago
Owner: | removed |
---|---|
Status: | assigned → new |
I can agree for the 'mark changes since last update'. I use the CSS Timeline of Trac to keep trac and sometimes pages are changed and I cant see too good, what is changed. I would go for a in text marking of changes since last visit. Or something like a vertical line in front of the text if that is possible in CSS (left-border solid 1 px).