More > Media Center 16 (Development Ended)
Feedback/ideas wanted: File Properties (tags) wiki rewrite
MrC:
Hi folks,
I'm midway a good portion through the process of rewriting the File Properties (tags) wiki page. I generated a table of Media Center fields and their definitions using Matt's source code header file as a start, manually checked each one, and then created a program to output a wiki table. Thus, it is easy to change the formatting, add new entries, etc.
I'd like your feedback / input / modifications:
- how to best format/present the information
- additional information to present
- descriptions or links you'd like to see
Keep in mind there's a lot of info to show, and the page is already long. It probably isn't the place for a comprehensive list of links, but is perhaps better to provide a single meta-link to more comprehensive pages relevant to a field / tag.
My new version is located here (I created a working scratch page for now):
wiki.jriver.com/index.php/MrC-temp
The original is located here:
The original has now been replaced with the new version:
http://wiki.jriver.com/index.php/File_Properties_%28tags%29
I realize I'm opening a can of worms by asking feedback, but what is the point of a Wiki if not to benefit the most users? And I'm curious to see where it leads.
I'm thinking since folks don't really like editing the wiki (I hate it), we can try this. You post your feedback in this thread, I'll incorporate it where possible into the wiki. I give myself license to wordsmith... just because.
kensn:
Looks really nice. thanks for taking the time to do this. With the quick look I gave it I have just one critique, I think the flow would look nice if the Edit Type was not right Justified, but tabbed over... Hey you asked...
Data Type: String Edit Type: Standard
Ken
MrC:
I agree Ken. I wasn't sure how to column align/float that entry without using an interior table per cell, and padding with non-breaking spaces doesn't work with vairable-spaced fonts. So I just floated it right for the time-being. There really is no "tab" concept in HTML/CSS, but I'll see what I can workout.
Thanks.
rick.ca:
The table is a handful. What you need is a MediaWiki table filter extension. That would allow one table to answer questions like...
* What fields are provided for Audio?
* Which ones are saved in file tags?
* Which Audio fields are included in a search?
* What other list-type fields are available for Video?
* ...etc. 8)
If that's not doable, you could provide the same thing in the form of an Excel worksheet (also automatically generated?). That would get less use, but would still be handy for doing things like deciding how to use Video fields, mapping data from meta data sources, etc.
Aren't you glad you asked? ;)
MrC:
Agreed. ...or the Sortable extension, which provide sort columns via Javascript. I don't believe it is enabled/installed.
I could also create one page / media type. There would be duplicate information. Its no problem on the generation side, but updating 5 pages instead of 1 each time. Yuck.
Just before you posted, I thought it might be better to use full words for audio types, so they at least could be searched from the page. I used letter-abbreviations simply to reduce clutter, but that was before rows become taller. This wouldn't be an issue if the columns could be sortable.
I'd love to see this type of documentation automatically generated from the source code.
Navigation
[0] Message Index
[#] Next page
Go to full version