Opened 20 years ago
Last modified 6 years ago
#3098 new enhancement
Support "Descript.ion" files in Browse Source
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | next-major-releases |
| Component: | version control/browser | Version: | 0.9.5 |
| Severity: | normal | Keywords: | description |
| Cc: | trac@…, osimons, Ryan J Ollos | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
As the summary says…
Right now we hand edit a Wiki page describing each subdir and file.
The descript.ion metadata file is a quasi-standard by JP-Soft (4DOS) that Browser might be able to support showing a short description of each file.
Attachments (0)
Change History (17)
comment:1 by , 19 years ago
| Keywords: | description added |
|---|---|
| Milestone: | → 0.12 |
| Owner: | changed from to |
| Priority: | low → normal |
comment:2 by , 19 years ago
| Cc: | added |
|---|
comment:3 by , 15 years ago
| Priority: | normal → high |
|---|
Or simpler:
[browser] readme = README, descript.ion, ...
Show at the top a one-liner of the README, with a link to the full content at the bottom (i.e. GitHub's way).
follow-up: 5 comment:4 by , 13 years ago
| Cc: | added |
|---|
FYI: My th:ReposReadMePlugin implements much of what is requested here. See the plugin docs and the examples I link to from there.
comment:5 by , 13 years ago
Replying to osimons:
FYI: My th:ReposReadMePlugin implements much of what is requested here. See the plugin docs and the examples I link to from there.
tracopt.versioncontrol.readme? With the likes of GitHub, BitBucket and co supporting this out of the box, I think it's appropriate to have this feature at least in tracopt.
comment:6 by , 13 years ago
| Cc: | added |
|---|
comment:7 by , 13 years ago
All the comments so far concern a header or a footer. The descript.ion file is a line-by-line description of each individual file in a directory.
I was the OP five years ago, but cannot edit the ticket description to point to the file layout specs that I just found.
comment:8 by , 13 years ago
| Description: | modified (diff) |
|---|
comment:9 by , 13 years ago
So this really boils down to 2 separate technical needs:
- A way of rendering directory files following a certain naming scheme (like
readme*, descript.ion) much like th:ReposReadMePlugin - A content renderer for the
.ionfile type that can parse and render the file description information contained within
comment:10 by , 13 years ago
Or/and:
- A IPropertyRenderer. But then the version control backend would have to be extended to parse and attach the file description information as properties first. Maybe a new extension point
IPropertyProvideris needed? - A nice way to present this information would be to add an additional column
Descriptionto the directory listing table (dirlist_thead.html / dir_entries.html). Maybe a new extension pointIBrowserColumnProvideris needed?
comment:12 by , 11 years ago
| Cc: | added; removed |
|---|
comment:14 by , 11 years ago
| Milestone: | next-major-releases → next-dev-1.1.x |
|---|
comment:15 by , 10 years ago
| Owner: | removed |
|---|
comment:16 by , 10 years ago
| Milestone: | next-dev-1.1.x → next-dev-1.3.x |
|---|
Narrowing focus for milestone:1.2. Please move ticket to milestone:1.2 if you intend to fix it.
comment:18 by , 6 years ago
| Milestone: | next-dev-1.5.x → next-major-releases |
|---|



Even better, there could be a setting like:
which could be used to pick one entry among the folder entries which will be previewed in the browser folder list, on top or after the entries list itself.
The preview would be done the standard way, so it would be possible to use wiki formatting either by setting the
svn:mime-typeproperty on a README file (if using svn), or by using mime-type associations in mime_map (e.g.text/x-trac-wiki:trac).Using an ordered list is useful so that you can eventually add a special file (
.tracas in the above) to prevent some existingREADMEfile to be shown, when this is not desirable.