#foswiki 2016-01-09,Sat

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
gac410uebera|| okay, fix for Foswiki 2.0/2.1 is posted to Item5969. Requires Regexp::IPv6 [00:50]
FoswikiBothttp://foswiki.org/Tasks/Item5969 [ Item5969: Support IPv6 addresses in URL ] [00:50]
***jomo has left [01:03]
........ (idle for 39mn)
uebera||gac410: \o/
...and gn8 ;)
[01:42]
gac410gn8
And still pondering. Fix is pretty ugly.
I'm afraid it might match "other stuff" completely unrelated to ipv6
[01:44]
jomogac410: how to link easily such url? https://metacpan.org/requires/distribution/Moo?sort=[[2,1]]&size=500 ofc the [[https://metacpan.org/requires/distribution/Moo?sort=[[2,1]]&size=500][look this]] will be broken... [01:46]
uebera||Will have a look at the repository; originally, I thought to "whitelist" a set of known protocols so that <protocol>://[<ipv6>] is identified/replaced by a placeholder, then http://en.wikipedia.org/wiki/Special:Search?go=Go&search=][ is processed, then the placeholders get filled in again (very dirty, but a quick fix).
argh, I /did/ enter \[\[\]\[\]\] just now.
[01:46]
gac410That's what I basically did. I used Regexp::IPv6 to find any v6 address on the page, placeholder it, then do the links, then restore them [01:47]
uebera||Ah, great minds think alike. :o) [01:48]
gac410But it's a huge regex from yet another cpan module, and I have no idea what other ugliness it might match.
jomo, you'd need to encode the [ and ] I think. ugh.
[01:49]
uebera||IMHO the current handling of hyperlinks should not be affected by 'stray' square brackets in the first place. Maybe an analysis of that is a better, more stable alternative, though it requires more work. [01:52]
gac410You'd need to rewrite the regex parser for squabs into some sort of scan / state machine I suspect. [01:52]
uebera||Yes. [01:53]
jomoyeah - encode - that's what i did - only was curious about an easier solution... :) [01:53]
................ (idle for 1h16mn)
gac410jomo, good point on the %{<verbatim>... comments, though they are currently useless due to the SkinTemplateViewTemplate. [03:09]
***fsfs has quit IRC (*.net *.split)
jast has quit IRC (*.net *.split)
[03:11]
sendak.freenode.net sets mode: +v WikiRingBot [03:21]
.............................. (idle for 2h28mn)
gac410 has left [05:49]
........................... (idle for 2h13mn)
ChanServ sets mode: +o CDot [08:02]
........................ (idle for 1h57mn)
GithubBot[distro] cdot pushed 1 new commit to Item13909: http://git.io/vu7Jy
distro/Item13909 9dd90e8 Crawford Currie: Item13909: reverted changes to FW-version-sensitive templates
[09:59]
***GithubBot has left [09:59]
FoswikiBothttp://foswiki.org/Tasks/Item13909 [ Item13909: Support expansion of standard macros during topic creation from template. ] [09:59]
............................................. (idle for 3h42mn)
***ChanServ sets mode: +o Lynnwood [13:41]
.......... (idle for 47mn)
ChanServ sets mode: +o gac410 [14:28]
.... (idle for 17mn)
GithubBot[distro] Jlevens pushed 1 new commit to master: http://git.io/vu5UJ
distro/master 2495127 JulianLevens: Item13594: Documentation for AddConcatOptionToAttrs
[14:45]
***GithubBot has left [14:45]
FoswikiBothttp://foswiki.org/Tasks/Item13594 [ Item13594: Implement Feature AddConcatOptionToAttrs ] [14:45]
GithubBot[distro] Jlevens pushed 1 new commit to master: http://git.io/vu5To
distro/master 55fdc88 JulianLevens: Item13594: Documentation for AddConcatOptionToAttrs
[14:51]
***GithubBot has left [14:51]
GithubBot[distro] Jlevens pushed 1 new commit to master: http://git.io/vu5kG
distro/master 2d887c4 JulianLevens: Item13594: Documentation for AddConcatOptionToAttrs
[14:53]
***GithubBot has left [14:53]
................ (idle for 1h16mn)
gac410jomo, I commented on the %{ }% proposal. I'm suggesting that we implement it as proposed, BUT also implement a template display mechanism that:
- Formats the template %{..}% comments as wiki text and
- renders all remaining in verbatim blocks
The existing "hide a verbatim in a non-comment" is rather hokey, and noisy, and is undocumented
[16:09]
jomohi gac410 , just posted my answer. i'm not raising concerns.. ;) :) :) [16:13]
gac410Don't be so self-deprecating. You identified a current usage, all be it rather arcane, and it needed to be considered. I think a "real template viewing" mechanism would be an improvement over the current undocumented %{ <verbatim> }% hack.
And I don't think it would be all that difficult to implement. The Include "handlers" are pluggable.
[16:15]
jomogac410: it isn't any self-depraction. Just my view to the future of the foswiki, is probably somewehre elsewhere - so developing any such "improwments" takes the valuable developers time and not really bring us to "the brighter future".
The brigher future needs general changes from the roots and the backawad compatibility should be solved as thin emulation layers on some brand new engines. (which are existing and honestly are much mor epowerfull as any of current FW engine) :)
E.g. by me we need cuts as "vrurg" started (and im hope, he will be successful) :)
thats all - :) :) im fully supporting any initiative and will test them as good as i know...
[16:21]
gac410Revolution is hard, and tends to leave bodies along the sides of the road. :) [16:23]
jomoah yes - cemetreties are full of heroes.. ;) [16:24]
gac410So about your comment about being unable to insert a topic comment from a template. It's making my head hurt.
A simple "template topic" as opposed to a SkinTopicTemplate. would not redact any comments.
gawd I wish we used a different work for topic vs skin templates.
[16:25]
jomogac410: my problem is mainly the my ability express myself. Once MD said something as: "if i'm unable clearly communicate my own thoughts = it is my problem" and *he is right*. I simly have in my mind something what i'm unable to tell to others in clear and understandable form.. ;)
So, back: if we will have ONE COMMENT syntax for each phases - here isn;'t any possibility to differentiate to which phase the comment belong. e.g. which phase will ignore the particular one?
[16:31]
gac410Right. hm... [16:34]
vrurgjomo: Sorry guys, I'm mostly busy these days, but trying not to miss if I get mentioned. :) Anything in particular I shall read in the proposals to keep in touch? [16:34]
jomovrurg: nah - i just used your initiative as an good example. ;) [16:35]
gac410nothing really related to your work. Just ramblings about Skin templates [16:35]
vrurgvrurg is so regret to miss a lot of things...
Hope to get some time today to work on the code anyway.
[16:36]
gac410jomo. how much do you need a skintemplate to insert a TML comment. That cannot be done today because %{}% comments are killed very early. So that's something completely new.
So it really has nothing to do with CDots proposal, since they are already removed from the template, before it's expanded.
[16:40]
jomoyes - as i said - it is an only the "demonstration" the *potential* problems caused by the fact - with unified comment syntax - here isn't any possibility to differentiate to which phase the comment belong. thats all. ;)
but - at the end - i'm not raising concerns - i could live with any comment syntax. ;)
[16:43]
....................................................... (idle for 4h32mn)
***ColasHme has quit IRC (Remote host closed the connection) [21:18]
............................. (idle for 2h24mn)
rouiljgac410, should Development.SupportAllMacrosInTemplateTopics (ref: http://foswiki.org/Tasks/Item13909) be listed on http://foswiki.org/Development/ReleasePlan, or is it still not really planned for a 2.2 release. [23:42]
FoswikiBot[ ReleasePlan ] [23:42]
gac410We haven't really started the plan for 2.2, but it will definitely be in there. [23:43]
The way the process works, a developer makes a proposal, and sets a "commitment date". That starts a 14 day clock. If nobody objects by raising a concern it is automatically accepted.
So that proposal was Jan 5th, so on Jan 19, if no concerns are raised, it's a go. If someone raises a concern it stops the clock, and you either negotiate a resolution, or go to a "community vote"
In this case code is already written, so after the 19th, I'll just merge it, and it will be ready for the next release.
[23:52]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)