On Wednesday, 21 November 2012 at 22:22:02 UTC, Vladimir
Panteleev wrote:
> Here's something to start with:
>
> http://dwiki.kimsufi.thecybershadow.net/
>

Thank you. :)

MediaWiki seems pretty easy to use. I just modified the Main_Page
and added the WhySwitch page (content copied from the old wiki:
http://www.prowiki.org/wiki4d/wiki.cgi).

Regards,
RMR

On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
> On Fri, Nov 16, 2012 at 08:52:39PM -0500, Jonathan M Davis wrote:
> > On Friday, November 16, 2012 13:55:31 H. S. Teoh wrote:
> > > I don't like the prospect of having to duplicate parts of std.algorithm just because I have some code that produces transient ranges -- I *know* I'm never going to need to use algorithms on them that can't handle transience anyway. It's Not Nice to be forced to duplicate code just because an arbitrary decision was made to ban transience, or just because some leaky type inference decided my range was transient when it's not, etc..
> > 
> > The problem is that supporting transience complicates ranges even further, and they're already too complicated. And supporting every possible use case is likely to require yet further modifications to ranges, complicating them even further. We have to draw the line somewhere.
> 
> Since that is the case, that really only leaves us with two choices: (1)
> declare transient ranges outright illegal, or (2) make all default
> ranges non-transient (e.g. ByLine, ByChunk), and let documentation warn
> the user that transient ranges may not work with every algorithm.
> 
> I'm leaning towards (2), because every other option brought up so far sucks one way or another. I know coding by convention is frowned upon here, but clearly, transience is an issue that requires human insight to solve on a case-by-case basis, and no simple enforceable solution exists. Thus, the only choice seems to be to leave it up to the programmer to do the right thing. The redeeming point is that we will make byLine and byChunk non-transient by default, so that users who don't want to care, don't need to care -- the code will just do the right thing by default. We can then provide byLineFast and byChunkFast for people who want the extra performance, and know how to deal with transience correctly.
> 
> This solution requires no further code changes beyond making byLine and byChunk non-transient by default, which is what you have been pushing for anyway. And it doesn't have any of the drawbacks of the other approaches.
> 
> > I have found reference type ranges to be very useful upon occasion to the point that not having them would be a major problem for some code, but if we were to start from scratch, I'd probably still argue against allowing them and just get rid of save entirely, because it's caused us a lot of problems. I really don't want to see ranges complicated even further.
> 
> [...]
> 
> If we agree on (2), then ranges will be no more complicated than they are today. The two Phobos offenders, byLine and byChunk, will be non-transient by default. The documentation will warn the user that transient ranges are to be "used at your own risk", just like casting void pointers and other risky language features that are nevertheless sometimes necessary.

I'd agree with #2, except that I don't know where we'd put warnings about transience. On isInputRange? It certainly doesn't make sense to put them on every function. At most, it would make sense to put them where front or popFront is described.

- Jonathan M Davis

On Wednesday, 21 November 2012 at 22:22:02 UTC, Vladimir Panteleev wrote:
> Here's something to start with:
>
> http://dwiki.kimsufi.thecybershadow.net/

Could you please set up a robots.txt which disables indexing until this has become officially adopted, and moved to its final address?

Also, how »stable« can we expect that instance to be? Do you make backups? Does it already make sense to invest work into it?

David

On 11/22/12, r_m_r <r_m_r@mailinator.com> wrote:
> I just modified the Main_Page
> and added the WhySwitch page (content copied from the old wiki:
> http://www.prowiki.org/wiki4d/wiki.cgi).

Is it possible to increase the default font size for D syntax highlighting?

This is what it looks like, it's almost unreadable: http://i.imgur.com/B39nC.png I would prefer this, which is 10pt in a standard code editor: http://i.imgur.com/izGsJ.png

On Thursday, 22 November 2012 at 10:41:33 UTC, Andrej Mitrovic wrote:
>
> Is it possible to increase the default font size for D syntax highlighting?
>

I don't think I can change the font size directly.
The CSS style for that <pre> tag is generated by the SyntaxHighlight GeSHi extension as shown below (copied from the page source):

/**
 * GeSHi Dynamically Generated Stylesheet
 * --------------------------------------
 * Dynamically generated stylesheet for d
 * CSS class: source-d, CSS id:
 * GeSHi (C) 2004 - 2007 Nigel McNie, 2007 - 2008 Benny Baumann
 * (http://qbnz.com/highlighter/ and http://geshi.org/)
 * --------------------------------------
 */
.d.source-d .de1, .d.source-d .de2 {font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;}
.d.source-d  {font-family:monospace;}

BTW The code displays fine on my browser. Maybe you can try changing the Minimum font size in your Browser preferences? I have mine set to a minimum of 12pt. Also, you can choose a different theme in the wiki preferences page: http://dwiki.kimsufi.thecybershadow.net/Special:Preferences#mw-htmlform-skin

Hope that helps.

Regards,
r_m_r

On 11/22/12, r_m_r <r_m_r@mailinator.com> wrote:
> I don't think I can change the font size directly.

Sorry, I should have quoted Vladimir, not you.

On 11/22/12, r_m_r <r_m_r@mailinator.com> wrote:
> BTW The code displays fine on my browser.

Which browser? It displays the same for me on Firefox and Chrome.

On 11/22/12, r_m_r <r_m_r@mailinator.com> wrote:
> Maybe you can try
> changing the Minimum font size in your Browser preferences?

That doesn't help until I increase it to a huge value which ends up changing the way all the text on the page looks (including other websites).

> Also, you can choose a
> different theme in the wiki preferences page:
> http://dwiki.kimsufi.thecybershadow.net/Special:Preferences#mw-htmlform-skin

I don't want to change the theme, I just want the code font size set to a readable default for my OS (which is Courier New 10pt on win32).

On Thursday, 22 November 2012 at 10:16:53 UTC, David Nadlinger wrote:
> On Wednesday, 21 November 2012 at 22:22:02 UTC, Vladimir Panteleev wrote:
>> Here's something to start with:
>>
>> http://dwiki.kimsufi.thecybershadow.net/
>
> Could you please set up a robots.txt which disables indexing until this has become officially adopted, and moved to its final address?

Done.

> Also, how »stable« can we expect that instance to be?

As stable as forum.dlang.org.

> Do you make backups?

Automatic daily incremental offsite backups are performed, of the filesystem and the database.

> Does it already make sense to invest work into it?

I can think of no reason not to.

On Thursday, 22 November 2012 at 10:41:33 UTC, Andrej Mitrovic wrote:
> On 11/22/12, r_m_r <r_m_r@mailinator.com> wrote:
>> I just modified the Main_Page
>> and added the WhySwitch page (content copied from the old wiki:
>> http://www.prowiki.org/wiki4d/wiki.cgi).
>
> Is it possible to increase the default font size for D syntax highlighting?
>
> This is what it looks like, it's almost unreadable: http://i.imgur.com/B39nC.png
> I would prefer this, which is 10pt in a standard code editor:
> http://i.imgur.com/izGsJ.png

That would be because your browser is using Courier New for the monospace CSS font family, which is notable for being smaller than other fonts at the same font sizes.

I've overridden the definition to use the same CSS as the forum (basically, try "Consolas" before falling back to "monospace"). Does it look better now?

If anyone would like to suggest a CSS change, you can try it out by adding CSS to http://dwiki.kimsufi.thecybershadow.net/Special:MyPage/vector.css. Only you will see the changes; once you're satisfied, let me know and I'll look into adding them to the main stylesheet.

On 11/22/12, Vladimir Panteleev <vladimir@thecybershadow.net> wrote:
> Does it look better now?

Nope, still the same.

On 11/22/12, Vladimir Panteleev <vladimir@thecybershadow.net> wrote:
> That would be because your browser is using Courier New for the monospace CSS font family, which is notable for being smaller than other fonts at the same font sizes.

I see. I can change it to 16 and then it looks good, but then dlang.org code samples look too large.

But I don't understand, why doesn't 10pt on the web mean 10pt like in the editor?

On Thursday, 22 November 2012 at 15:18:24 UTC, Andrej Mitrovic wrote:
> On 11/22/12, Vladimir Panteleev <vladimir@thecybershadow.net> wrote:
>> Does it look better now?
>
> Nope, still the same.

Can you try a force-refresh or clearing the browser cache?

What web browser and operating system do you use?