Dirk Stöcker skrev 04/01/11 19:08: > On Tue, 4 Jan 2011, Christian Boos wrote: > >> However I still think that separating the open source projects from >> the companies using private Tracs would be useful. In the first >> section "open > > Well, the "instead" only referred to the "I work at" comment. I agree > that commercial and open accessable stuff should be separated. > >> source", we're free to organize it as we want, placing the outstanding >> Tracs first (including those of contributors to the projects if they >> want, starting with edgewall.org itself). Whereas in the second >> section for companies, a neutral order sounds more appropriate (e.g. >> last additions at the end as it is now I believe - easier to maintain >> than alphabetical order). > > Well, it is harder to read for the user, so alphabetical is much better. >> From time to time someone can have a look and resort :-)
I suppose one could consider using: http://trac.edgewall.org/wiki/ProcessorBazaar#SortedTable for this ? Not sure if it works with 0.12, though. Should give the best of everything -- allow initial grouping by "theme", as well as easy access to oldest/newest and alphabetic sort for readers. There's an open ticket for adding something like this to trac: http://trac.edgewall.org/ticket/8949 (sortable tables) While I wasn't aware of the `||= header =||`-table syntax before looking at the html and wiki-source of http://trac.edgewall.org/wiki/TracUsers -- it seems it would be inconvenient to make the standard trac tables sortable -- most javascript-solutions assume a thead/tbody-style markup, rather than sorting on th-cells. It would be possible to tweak the wiki-parser to output thead/tbody-elements -- but it would require header-columns to come on the first line of at table, ie, it would break stuff like: {{{ ||= OSS Licence =||= Project =|| || GPL || Roxen WebServer || || APL v2.0 || Apache httpd || ||= Licence fee ||= Product =|| || ?$ || IIS || }}} as well as the canonical example from the WikiFormating-page: {{{ || ||= stable =||= latest =|| ||= 0.10 =|| 0.10.5 || 0.10.6dev|| ||= 0.11 =|| 0.11.6 || 0.11.7dev|| }}} (Or require some rather convoluted "magic" parsing, grouping all first-row headers in a thead-group -- not very appealing IMNHO). Semantically, having a header-group(row) makes sense for sortable tables, so wiki syntax for sortable tables should reflect this. Note that the (rather complex) table-syntax in html4 in many ways mirrors html5-like structure, with semantic grouping (thead,tbody) -- so finding a reasonable way to support this in the wiki markup would be a nice future-proofing exercise. I kind of like the simplicity of just adding a `#sorttable`-macro that mirrors the standard table syntax -- even if it feels a bit redundant. Anyway, keep up the good work maintaining the wiki! Best regards, -- .---. Eirik Schwenke <eirik.schwe...@nsd.uib.no> ( NSD ) Harald Hårfagresgate 29 Rom 150 '---' N-5007 Bergen tlf: (555) 889 13 GPG-key at pgp.mit.edu Id 0x8AA3392C
signature.asc
Description: OpenPGP digital signature
