On Sep 15, 2010, at 6:13 AM, Dmitry Samersoff wrote:
Christian.
On 2010-09-15 15:26, Christian Boos wrote:
1. HTML formatter cease out<video> tag, also I think Video macro
(like Image one) should be added to main trunk
<video> is HTML 5, right?
It's not a high priority task, as far as this macro could be
developed in five minutes but definitely worth to do.
It could be smart enough to install flash/youtube/<video> depending
to content and browser version.
But I will not push here - just count it as RFE.
2. WikiFromatter doesn't respect html special chars - i.e.
become&nbsp; - is it a bug or expected behavior? (I wrote a
plugin to workaround it - but I think it should be fixed)
That's supported by the WikiGoodiesPlugin
(http://trac-hacks.org/wiki/WikiGoodiesPlugin).
Yes, actually I wrote my own simple plugin to workaround the issue,
but I still thing it should be default behavior.
3. id like one below in wiki text is a bad idea.
<h3 id="Краткаябиография">Краткая
биография</h3>
It's better to use some number e.g. md5(header value)
And what about <h3
id="Краткая_биография">Краткая
биография</h3>?
(see
http://trac.edgewall.org/wiki/TracDev/Proposals/AdvancedWikiFormatting#Headings)
id of xml tag should be reliable across different editors, VCS etc.
Think you should type something like code below couple of times
within your program:
var el =
getElementById('Shogainokarate生涯の空手-
Загородный17с21до22:30');
so IMHO it should be normalized by one of existing algorithms
(base64, md5 etc)
4. Wiki paragraph text have to have come default class i.e.<p
class="wikitext"> ....</p> otherwise it's hard to manage fonts etc
within wiki.
The "#wikipage p" selector is not enough?
It works but I guess separate class is slightly better.
Ideally if we could have:
<div id="_wiki_budo_ashihara"> (from /wiki/budo/ashihara)
<div id="wikipage">
<p class="wikipara">
....
</p>
</div>
Now I have to do some javascript tricks if I want to have different
formatting on different pages.
5. Menu system doesn't handle correctly a situation when we have /
wiki/page1 and /wiki/page2 in mainnav - it threat both as active
(see
http://trac-hacks.org/ticket/4914). I use trackmenus plugin to
customise mainnav, but it's not a tracmenus issue - I debug it
down to
trac core.
Go to:
http://devnull.samersoff.net/trac/me/wiki
And compare behavior of "blog" and "family" or "budo" entries of
mainnav
This is due to how the active navigation provider is determined by the
current controller. You need to alter the source name on the extra nav
entries, which is something that has to be done in the plugin not Trac
itself.
--Noah
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-...@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
