browse source - edit feature?

[anonymous]

It would be great if when browsing the source tree through the subversion repository, there was a way to pull up an "Edit" box to make quick edits to files and submit them to the subversion repository. This way I can give access to WIKI users to make edits to files within the subversion repository without them needing to set up full development environments.

[Emmanuel Blot]

Potential duplicates / related requests: #2956, #2755

[Christian Boos]

Potentially useful for making small edits, like fixing typos, the inlined documentation, etc.

[Christian Boos]

#5131 was closed as duplicate of this ticket.

[Christian Boos]

Milestone 2.0 deleted

[Christian Boos]

Replying to cboos:

Potentially useful for making small edits, like fixing typos, the inlined documentation, etc.

And instead of "saving" by performing a commit, we could create a diff as an attachment to an existing ticket or to a new one (if the ticket field is left blank).

The "Review changes" page should present the diff in the usual way, but also a textarea containing the diff as plain text for copy/pasting (or should have a link to the raw diff).

That would be for the "Edit" feature, a related feature could be "Review" (a simple form of #2035), where the original text would be quoted (> ...), and the saving would create a new comment for the selected ticket (or, like in the above, a new ticket if the ticket field is left empty).

Those two features would be useful not only for source files in the repository, but also for attachments. Combined with a patch renderer that is more resilient to "fragmented" patches, it would make it easier to review patches.

[Christian Boos]

Replying to cboos:

Replying to cboos:

Potentially useful for making small edits, like fixing typos, the inlined documentation, etc.

And instead of "saving" by performing a commit, we could create a diff as an attachment to an existing ticket or to a new one (if the ticket field is left blank).

The "Review changes" page should present the diff in the usual way, but also a textarea containing the diff as plain text for copy/pasting (or should have a link to the raw diff).

I just noticed that something very close has been recently(?) added to GoogleCode.

a related feature could be "Review" (a simple form of #2035), where the original text would be quoted (> ...), and the saving would create a new comment for the selected ticket (or, like in the above, a new ticket if the ticket field is left empty). … (needs a) patch renderer that is more resilient to "fragmented" patches, it would make it easier to review patches.

That would be the difficult part. We should be able to deal with this kind of input:

Index: TracOnUbuntu
===================================================================
--- Version 81
+++ Version 82
@@ -12,7 +12,7 @@
 '''Note:''' It is always best practice to use the latest [wiki:WikiStart stable version] of Trac.
 
 ||= tutorial =||=  Ubuntu Version =||= Trac Version =||= Apache =||= VCS =||= Database =||
-|| [wiki:Ubuntu-11.04-Subversion] || 10.04 || 0.12 || Mod_Python || Subversion || MySQL||
+|| [wiki:Ubuntu-11.04-Subversion Ubuntu-10.04-Subversion] || 10.04 || 0.12 || Mod_Python || Subversion || MySQL||

Really?

 || [wiki:Ubuntu-10.04-Bazaar] || 10.04 || 0.12 || Mod_WSGI || Bazaar || MySQL||
 || [https://help.ubuntu.com/community/Trac ubuntu Help] || ?|| ?|| Mod_Python || ?|| SQLite||
 || [wiki:0.11/TracOnUbuntu] || 8.04 || 0.11 || Mod_Python || Subversion || SQLite||

[Christian Boos]

See also #9248 for an use case in which it would actually be useful to modify the repository (e.g. a clone dedicated to contributions in one area, like the documentation).

We could have a generic file edit/preview/review feature, but a IBrowserWriter interface, which could implement either the creation of a patch (and optionally attaching it to a ticket or create a new ticket), or directly saving the edited content in a new changeset.