Le 13/11/2012 03:59, Andrei Alexandrescu a écrit :
> On 11/12/12 6:29 PM, deadalnix wrote:
>> Le 13/11/2012 03:01, Andrei Alexandrescu a écrit :
>>> On 11/12/12 5:40 PM, deadalnix wrote:
>>>> I never used moveFront and alike.
>>>
>>> They're used by algorithms that you might be using.
>>>
>>> Andrei
>>
>> I'm not saying they are useless, or that I never used them under the
>> hood.
>
> Then what is it that you are saying? Honest question.
>
> Andrei

That mastering every range feature isn't required to work effectively with ranges.

Buna Andrei,

I initiated a discussion[1] about the state of the D wiki[2].

[1] http://forum.dlang.org/thread/k6jak1$quh$1@digitalmars.com [2] http://www.prowiki.org/wiki4d

There were three people agreeing that the current wiki engine might be a cause for the bad state of the content. Nobody wants to use this engine.

Tobias Pankrath proposed the github wiki engine (free software[3]) and I agreed that it would be best to just enable the wiki in a new project at the D github account[4].

[3] https://github.com/github/gollum
[4] https://github.com/D-Programming-Language

Now we need a decision on this issue and probably somebody to turn on the github wiki.

Multumesc, Thomas Koch

On 11/12/2012 11:09 PM, bearophile wrote:
> In this thread
> http://forum.dlang.org/thread/50A0EEA4.7010706@webdrake.net
>
> Joseph Rushton Wakeling suggests code like this to compile:
>
> struct Foo(_T) {
>      alias _T T;
> }
> void bar(FooT)(FooT foo, FooT.T x) {
> }
> void main() {
>      Foo!int foo;
>      bar(foo, 1); // line 8
> }

I'm not actually suggesting that the particular syntax above necessarily ought to work, but I'd like an easy way to ensure that one template parameter can be determined from another.

Joseph Rushton Wakeling:

> I'm not actually suggesting that the particular syntax above necessarily ought to work, but I'd like an easy way to ensure that one template parameter can be determined from another.

Right. But I think that syntax is the most natural one for that.

And Hara now thinks it's an idea worth considering:
http://d.puremagic.com/issues/show_bug.cgi?id=9004#c3

Bye,
bearophile

On 11/13/2012 03:01 PM, bearophile wrote:
> Right. But I think that syntax is the most natural one for that.

Agree. :-)

> And Hara now thinks it's an idea worth considering:
> http://d.puremagic.com/issues/show_bug.cgi?id=9004#c3

Excellent!  Thank you so much for bringing it to notice like this.

On 11/13/12 3:23 AM, Thomas Koch wrote:
> Buna Andrei,
>
> I initiated a discussion[1] about the state of the D wiki[2].
>
> [1] http://forum.dlang.org/thread/k6jak1$quh$1@digitalmars.com
> [2] http://www.prowiki.org/wiki4d
>
> There were three people agreeing that the current wiki engine might be a
> cause for the bad state of the content. Nobody wants to use this engine.
>
> Tobias Pankrath proposed the github wiki engine (free software[3]) and I
> agreed that it would be best to just enable the wiki in a new project at the
> D github account[4].
>
> [3] https://github.com/github/gollum
> [4] https://github.com/D-Programming-Language
>
> Now we need a decision on this issue and probably somebody to turn on the
> github wiki.
>
> Multumesc, Thomas Koch

I think that's a great idea. I'm not a frequent user of our Wiki, but e.g. for DIPs it's nice to have a better engine. I don't see why Walter would oppose a change.

The only thing we need to worry about is preserving links lest Google search pagerank gets lost. Is it possible to keep the old link convention?


Andrei

On 11/13/12, Thomas Koch <thomas@koch.ro> wrote:
> Now we need a decision on this issue

I think we need a proper discussion and a vote, not a decision yet. We should try and evaluate the wikis that are out there before settling for github right away. For one thing http://prowiki.org is pretty fast, whereas GitHub seems to be hosted in the States and is slower to access in Europe (it sure is slower to access for me compared to more popular websites, but that might not be true for others of course..).

And I think searchability is really important (prowiki sometimes sucks at this, but github is worse). The biggest problem I see with prowiki is the spamming issue.

Can gollum make nice colorized tables like this? http://prowiki.org/wiki4d/wiki.cgi?GuiLibraries Note also how the text reflows when you resize the window, I never see that happening with github wikis, they seem to be fixed in size.

It's too bad ProWiki is in Perl, if it was written in D we could contribute to it and modify it to our own needs.

On 11/13/12, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
> The biggest problem I see with prowiki
> is the spamming issue.

Another big issue is it's lack of syntax highlighting. gollum wins there, but other wikis might support D too. I'm not sure which do though.

On Tuesday, 13 November 2012 at 16:20:38 UTC, Andrej Mitrovic wrote:
> On 11/13/12, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
>> The biggest problem I see with prowiki
>> is the spamming issue.
>
> Another big issue is it's lack of syntax highlighting. gollum wins
> there, but other wikis might support D too. I'm not sure which do
> though.

Syntax highlighting is not a problem as highlight.js [1] can be easily added to any website (including any wiki engine) and it supports D syntax coloring (I'm provider and maintainer of that support code).

It can work on server too (trough node.js) if someone complains about it being a JavaScript tool.

[1] http://softwaremaniacs.org/soft/highlight/en/

On 11/13/12, Aleksandar Ruzicic <krckoorascic@gmail.com> wrote:
> Syntax highlighting is not a problem as highlight.js [1] can be easily added

It doesn't work in older browsers.