working on the dlang.org website

I just watched Andrei's *Quo Vadis *talk from this year's DConf and I liked it a lot. I strongly agreed with his notion that the D community needs to embrace "operational professionalism"; I've been thinking along those same lines for months and it's the one thing that the D community really, *real

Re: working on the dlang.org website

Would it be possible to add links to national dlang communities to the bottom of the page to make comers easier to find information and help on their native language?

Re: working on the dlang.org website

On 2013-07-14 05:19, Val Markovic wrote: I just watched Andrei's /Quo Vadis /talk from this year's DConf and I liked it a lot. I strongly agreed with his notion that the D community needs to embrace "operational professionalism"; I've been thinking along those same lines for months and it's the o

Re: working on the dlang.org website

Jacob Carlborg: I completely agree with you and I think it madness that the site is written in Ddoc. But apparently Walter and company loves it. Do you like this? It's made with Python: http://sphinx-doc.org/ Bye, bearophile

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: ... Thanks for the input! I do personally agree that official web page is one of most lacking areas of D public image. Maybe that is because there are no people among core developers specializing on web development (or am I ignora

Re: working on the dlang.org website

On 7/14/2013 2:30 AM, Jacob Carlborg wrote: I think it madness that the site is written in Ddoc. Different, sure. Madness - why?

Re: working on the dlang.org website

On 2013-07-14 14:34, bearophile wrote: Do you like this? It's made with Python: http://sphinx-doc.org/ Ddoc in it self is not that bad, for documenting code. It's just that I would never create a web site using it. I would go with a server side script. I prefer Ruby on Rails for that. -- /

Re: working on the dlang.org website

On 7/14/2013 6:49 AM, Dicebot wrote: But maintaining whole stuff via git repo + makefiles is definitely cumbersome, no idea why that was chosen. 1. github is how the entire rest of D is maintained, it would be strange if the website was handled via some completely different system. 2. github

Re: working on the dlang.org website

This discussion seems to have gone off track. I pointed out three things that I thought should be addressed to ease the use of contributing to the dlang.org site (and other D-project components), and those three things were: a) lower response latency on pull requests, b) better documentation of th

Re: working on the dlang.org website

On 7/14/2013 2:18 PM, Val Markovic wrote: I pointed out three things that I thought should be addressed to ease the use of contributing to the dlang.org site (and other D-project components), and those three things were: a) lower response latency on pull requests, b) better doc

Re: working on the dlang.org website

One of the things we should add to the new README is a tip pointing people toward the DDOC = macro in std.ddoc. That's the skeleton html for the website and is pretty plain.

Re: working on the dlang.org website

On Sun, Jul 14, 2013 at 2:37 PM, Walter Bright wrote: > > I agree with your three points. I'll add that anyone can do a pull request > to address any/all of these. > How can someone send a pull request to address the long latency of responding to pull requests? The other issues I pointed out are

Re: working on the dlang.org website

On 7/14/2013 2:59 PM, Val Markovic wrote: How can someone send a pull request to address the long latency of responding to pull requests? There are 13 open PRs, and about 335 pulled ones. While we can and must do better, I don't think the situation is as dire as you suggest. There are curre

Re: working on the dlang.org website

On Sun, Jul 14, 2013 at 3:34 PM, Walter Bright wrote: > While we can and must do better, I don't think the situation is as dire as > you suggest. > I think it's more dire than you realize, but I could be wrong. Here are a few links to pull requests on dlang.org that seem to need love from the mai

Re: working on the dlang.org website

On 7/14/13 5:20 PM, Walter Bright wrote: On 7/14/2013 2:30 AM, Jacob Carlborg wrote: I think it madness that the site is written in Ddoc. Different, sure. Madness - why? If you look at for example this file: https://github.com/D-Programming-Language/dlang.org/blob/master/lex.dd All I see i

Re: working on the dlang.org website

On 7/14/2013 7:19 PM, Ary Borenszweig wrote: On 7/14/13 5:20 PM, Walter Bright wrote: On 7/14/2013 2:30 AM, Jacob Carlborg wrote: I think it madness that the site is written in Ddoc. Different, sure. Madness - why? If you look at for example this file: https://github.com/D-Programming-Lang

Re: working on the dlang.org website

On 2013-07-15 05:22, Walter Bright wrote: HTML doesn't work for other kinds of output that is supported by the makefiles - ebook, pdf, etc. I thought the PDF was generated from the HTML output. I wrote the original Digital Mars web site in plain html. That's what motivated me to invent Ddoc.

Re: working on the dlang.org website

On 2013-07-14 22:20, Walter Bright wrote: Different, sure. Madness - why? "Madness" might be stretching it. You're making it unnecessary hard for someone not familiar with how the D website is structured. Example, I added a couple of new files to Phobos (std.serialization), which it properl

Re: working on the dlang.org website

On 2013-07-15 08:40, Jacob Carlborg wrote: "Madness" might be stretching it. You're making it unnecessary hard for someone not familiar with how the D website is structured. Example, I added a couple of new files to Phobos (std.serialization), which it properly generates the HTML files for. But

Re: working on the dlang.org website

On 2013-07-14 23:18, Val Markovic wrote: 3. Ruby on Rails (or Django or any other web framework that dynamically builds a server response) would be a terrible choice for a static website. It would be nothing but overhead for no benefit. Nothing on dlang.org is dynamically gene

Re: working on the dlang.org website

On 2013-07-15 05:22, Walter Bright wrote: Ddoc isn't any harder than any of the innumerable markup languages out there, like mediawiki. But how do I add support for Sass, CoffeeScript and similar languages that web developers expect today? It's dead easy in a framework like Ruby on Rails.

Re: working on the dlang.org website

On Monday, 15 July 2013 at 03:22:59 UTC, Walter Bright wrote: For example, if I want to change the copyright notice, I can: 1. edit hundreds of files -- or -- 2. edit a Ddoc macro It's no contest. Even the very simplest roll-your-own framework would remove this necessity. Even simpler

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 20:35:45 UTC, Walter Bright wrote: On 7/14/2013 6:49 AM, Dicebot wrote: But maintaining whole stuff via git repo + makefiles is definitely cumbersome, no idea why that was chosen. 1. github is how the entire rest of D is maintained, it would be strange if the webs

Re: working on the dlang.org website

On Monday, 15 July 2013 at 06:35:44 UTC, Jacob Carlborg wrote: On 2013-07-15 05:22, Walter Bright wrote: ... Makes me wonder if dlang.org backend reflavored to use vibe.d + some database has any chance to be accepted as a new upstream :) Dogfooding can done in a variety of ways ;)

Re: working on the dlang.org website

Anyone know what happen to the prototype that someone made using vibe.d? It looked really good, and worked a lot faster than the current one. It was roughly modelled on the php docs.

Re: working on the dlang.org website

On Monday, 15 July 2013 at 11:20:30 UTC, John Colvin wrote: Anyone know what happen to the prototype that someone made using vibe.d? It looked really good, and worked a lot faster than the current one. It was roughly modelled on the php docs. This one: http://vibed.org/temp/d-programming-la

Re: working on the dlang.org website

On Monday, 15 July 2013 at 06:56:38 UTC, Jacob Carlborg wrote: But how do I add support for Sass, CoffeeScript and similar languages that web developers expect today? This is almost as silly as Walter's copyright thing, since those languages are converted to regular js+css which are linked in

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: There's some low-hanging fruit with the site that shouldn't be too hard to fix: there's an incredibly annoying "content flash" after any page is loaded (it loads fine, you see the text, then the text disappears for a second, then ap

Re: working on the dlang.org website

On Monday, 15 July 2013 at 12:33:55 UTC, Flamaros wrote: The documentation need to be a specific section that allow us to browse all versions (documentation is related to a specific version of the compiler). That is actually a good call. No reason why documentation part should be done in same

Re: working on the dlang.org website

On 2013-07-15 14:46, Dicebot wrote: That is actually a good call. No reason why documentation part should be done in same way as rest of the website if styling stays the same. Yes, exactly. Consider Ruby on Rails: Main page: http://rubyonrails.org/ Guides: http://guides.rubyonrails.org/ API r

Re: working on the dlang.org website

On 2013-07-15 14:25, Adam D. Ruppe wrote: This is almost as silly as Walter's copyright thing, since those languages are converted to regular js+css which are linked in just like anything else. In fact, it is identical to the copyright edit except maybe editing the makefile to generate the file

Re: working on the dlang.org website

On 7/14/13 6:18 PM, Val Markovic wrote:> 3. Ruby on Rails (or Django or any other web framework that dynamically builds a server response) would be a terrible choice for a static website. It would be nothing but overhead for no benefit. Nothing on dlang.org is dynamically gener

Re: working on the dlang.org website

On Mon, Jul 15, 2013 at 02:33:53PM +0200, Flamaros wrote: > On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: > > >There's some low-hanging fruit with the site that shouldn't be too > >hard to fix: there's an incredibly annoying "content flash" after any > >page is loaded (it loads fine

Re: working on the dlang.org website

On Monday, 15 July 2013 at 14:42:17 UTC, H. S. Teoh wrote: AFAICT, it's just to generate the useless blob of links at the top of the page. I'm pretty sure the flash is hypenate.js. The links can mess up scrolling though as they appear. We need a *real* index, not a blob of links. And, of

Re: working on the dlang.org website

On 7/15/2013 1:20 AM, John Colvin wrote: On Monday, 15 July 2013 at 03:22:59 UTC, Walter Bright wrote: For example, if I want to change the copyright notice, I can: 1. edit hundreds of files -- or -- 2. edit a Ddoc macro It's no contest. Even the very simplest roll-your-own framework wo

Re: working on the dlang.org website

On 7/15/2013 6:12 AM, Ary Borenszweig wrote: If Walter wants to modify the copyright notice, he could modify the file _includes/copyright.html. No need to search for a macro named copyright. Are you also going to fix all your .c files to replace: #define ABC 3 #define DEF(i) ((i) + 3) w

Re: working on the dlang.org website

On 7/15/2013 3:08 AM, Dicebot wrote: Yeah, sure, I have no problem having website itself maintained via GitHub - but in my opinion it makes it much more static than it should be. For example, I'd absolutely love to see news & announcements added to the main page but don't see how it is going to h

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: There's some low-hanging fruit with the site that shouldn't be too hard to fix: there's an incredibly annoying "content flash" after any page is loaded (it loads fine, you see the text, then the text disappears for a second, then appe

Re: working on the dlang.org website

On Monday, 15 July 2013 at 19:20:00 UTC, Walter Bright wrote: That's why the d_programming twitter feed was added to the front page. Twitter is incredibly restrictive in its format. People coming to front page want to get a detailed explained overview of latest news, not 140-symbol mysteries.

Re: working on the dlang.org website

On 7/15/2013 12:39 PM, Dicebot wrote: On Monday, 15 July 2013 at 19:20:00 UTC, Walter Bright wrote: That's why the d_programming twitter feed was added to the front page. Twitter is incredibly restrictive in its format. People coming to front page want to get a detailed explained overview of l

Re: working on the dlang.org website

On Monday, 15 July 2013 at 19:54:54 UTC, Walter Bright wrote: Given how enormously popular Twitter is for breaking news and announcements, I think you're wrong about that. I have just check web pages for several popular programming languages and have found zero using twitter instead of a news

Re: working on the dlang.org website

On 7/15/2013 1:11 PM, Dicebot wrote: On Monday, 15 July 2013 at 19:54:54 UTC, Walter Bright wrote: Given how enormously popular Twitter is for breaking news and announcements, I think you're wrong about that. I have just check web pages for several popular programming languages and have found

Re: working on the dlang.org website

Am 15.07.2013 13:32, schrieb Dicebot: > On Monday, 15 July 2013 at 11:20:30 UTC, John Colvin wrote: >> Anyone know what happen to the prototype that someone made using vibe.d? >> >> It looked really good, and worked a lot faster than the current one. >> It was roughly modelled on the php docs. > >

Re: working on the dlang.org website

On 7/15/13 4:13 PM, Walter Bright wrote: On 7/15/2013 6:12 AM, Ary Borenszweig wrote: If Walter wants to modify the copyright notice, he could modify the file _includes/copyright.html. No need to search for a macro named copyright. Are you also going to fix all your .c files to replace: #

Re: working on the dlang.org website

On Monday, 15 July 2013 at 19:27:38 UTC, Brad Anderson wrote: On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: There's some low-hanging fruit with the site that shouldn't be too hard to fix: there's an incredibly annoying "content flash" after any page is loaded (it loads fine, you

Re: working on the dlang.org website

On Monday, 15 July 2013 at 20:34:07 UTC, Walter Bright wrote: On 7/15/2013 1:11 PM, Dicebot wrote: On Monday, 15 July 2013 at 19:54:54 UTC, Walter Bright wrote: Given how enormously popular Twitter is for breaking news and announcements, I think you're wrong about that. I have just check web

Re: working on the dlang.org website

On 2013-07-15 20:48, Brad Anderson wrote: unfortunately, do not support CSS3 hyphens so they still use the slow hyphenator.js. pls remove hyphenator.js altogehter. i see everyone complaining about it and no one wanting it. the words in the english language are usually short enough so that hyp

Re: working on the dlang.org website

On Tue, Jul 16, 2013 at 10:16:28AM -0500, captaindet wrote: > On 2013-07-15 20:48, Brad Anderson wrote: > >unfortunately, do not support CSS3 hyphens so they still use the slow > >hyphenator.js. > > pls remove hyphenator.js altogehter. i see everyone complaining about > it and no one wanting it. t

Re: working on the dlang.org website

Having hyphenator.js on the site slows down the browsing experience immensely, especially on mobile. I know I personally avoid the dlang.orgsite on my Galaxy Nexus and on my Nexus 7 because of this reason. Since the whole web is right-aligned and users would much rather have a site that loads fast

Re: working on the dlang.org website

On Tuesday, 16 July 2013 at 20:10:15 UTC, Val Markovic wrote: Having hyphenator.js on the site slows down the browsing experience immensely, especially on mobile. I know I personally avoid the dlang.orgsite on my Galaxy Nexus and on my Nexus 7 because of this reason. Since the whole web is ri

Re: working on the dlang.org website

On Monday, 15 July 2013 at 13:12:38 UTC, Ary Borenszweig wrote: You can also try GitHub pages. And since D already has its code in github it's very simple. http://pages.github.com/ I would advise against, since this creates a strong dependency on github. Currently the community would be

Re: working on the dlang.org website

On Monday, 15 July 2013 at 06:53:37 UTC, Jacob Carlborg wrote: On 2013-07-14 23:18, Val Markovic wrote: 3. Ruby on Rails (or Django or any other web framework that dynamically builds a server response) would be a terrible choice for a static website. It would be nothing but overhead for no ben

Re: working on the dlang.org website

On Wednesday, 17 July 2013 at 07:46:28 UTC, Chad Joan wrote: FWIW, I was able to pick up and understand ddoc very quickly. It is awesome for docs (you know, that thing it was made for). I also love the idea of generating webpages from my source code: as long as it's API docs. I don't think

Re: working on the dlang.org website

On 2013-07-17 09:46, Chad Joan wrote: Please no RoR/PHP/JavaScript/etc. It's already hard enough to contribute to this thing as it is. These would add a bunch of dependencies for little gain, and possibly a bunch of alienation. Yes, it adds dependencies but it's easy to use and is well docum

Re: working on the dlang.org website

On 07/17/2013 05:22 AM, Jacob Carlborg wrote:> On 2013-07-17 09:46, Chad Joan wrote: ... Ddoc isn't hard to use, it's too limited in what it can do. What is hard is everything around it, like building and so on, as you mentioned. With a big web development framework, like Rails, it's well do

Re: working on the dlang.org website

On 07/14/2013 05:19 AM, Val Markovic wrote: 2. Looking at the Network data in the Chrome DevTools, realize the site isn't using a CDN. Make a note of mentioning this to the site maintainers; using a CDN is critical to performance and ever since CloudFlare came on the scene (fast & fr

Re: working on the dlang.org website

Didn't see hypenation on the web before, looks alien to me. From the typesetting point of view I find manpages with a larger font pleasure to read. http://man7.org/linux/man-pages/man3/fclose.3.html They are neither justified nor hyphenated.

Re: working on the dlang.org website

On Mon, Jul 22, 2013 at 09:59:57PM +0200, Kagamin wrote: > Didn't see hypenation on the web before, looks alien to me. From the > typesetting point of view I find manpages with a larger font > pleasure to read. > http://man7.org/linux/man-pages/man3/fclose.3.html > They are neither justified nor hy

Re: working on the dlang.org website

On Monday, 22 July 2013 at 20:49:09 UTC, H. S. Teoh wrote: On Mon, Jul 22, 2013 at 09:59:57PM +0200, Kagamin wrote: Didn't see hypenation on the web before, looks alien to me. From the typesetting point of view I find manpages with a larger font pleasure to read. http://man7.org/linux/man-pages

Re: working on the dlang.org website

On Mon, Jul 22, 2013 at 11:48:10PM +0200, Brad Anderson wrote: > On Monday, 22 July 2013 at 20:49:09 UTC, H. S. Teoh wrote: > >On Mon, Jul 22, 2013 at 09:59:57PM +0200, Kagamin wrote: > >>Didn't see hypenation on the web before, looks alien to me. From the > >>typesetting point of view I find manpa

Re: working on the dlang.org website

On Monday, 22 July 2013 at 22:35:20 UTC, H. S. Teoh wrote: On Mon, Jul 22, 2013 at 11:48:10PM +0200, Brad Anderson wrote: On Monday, 22 July 2013 at 20:49:09 UTC, H. S. Teoh wrote: >On Mon, Jul 22, 2013 at 09:59:57PM +0200, Kagamin wrote: >>Didn't see hypenation on the web before, looks alien to

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 20:19:06 UTC, Jacob Carlborg wrote: On 2013-07-14 14:34, bearophile wrote: Do you like this? It's made with Python: http://sphinx-doc.org/ Ddoc in it self is not that bad, for documenting code. It's just that I would never create a web site using it. I would go wi

Re: working on the dlang.org website

On Monday, 22 July 2013 at 15:40:47 UTC, Martin Nowak wrote: On 07/14/2013 05:19 AM, Val Markovic wrote: 2. Looking at the Network data in the Chrome DevTools, realize the site isn't using a CDN. Make a note of mentioning this to the site maintainers; using a CDN is critical to performanc

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 20:35:45 UTC, Walter Bright wrote: 3. HTML, PDF, Ebook, and CHM outputs are generated from Ddoc. Walter, with respect, I know you're too smart to be saying something silly like this. Surely you know that ebooks and CHM are specially-compiled HTML files. To imply th

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 07:47:03 UTC, nazriel wrote: Hyphenate.js indeed has an impact on load times and removing it in favor of CSS3 would fix the problem. Of course there is probability that people with '90s browsers will complain (stares at Nick ;>) but it is their choice to stick with suc

Re: working on the dlang.org website

On 2013-07-23 09:47, nazriel wrote: There is absolutely nothing that Ruby, PHP or anything else would buy us at this point. It would be just killing fly with the hammer. I guess you don't see the advantage of having: * Built in support for Sass, CoffeeScript and similar techniques * Using a w

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 12:29:38 UTC, Jacob Carlborg wrote: * Built in support for Sass, CoffeeScript and similar techniques * Using a well known framework that have plenty of documentation available * Having a server and database backing up new features as such comments There is nothing

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 13:19:12 UTC, Dicebot wrote: There is nothing here D can't do. Dogfooding ftw. hell, I've done my own versions of that stuff in D! Though most the similarities are actually coincidence since I've never actually used the Ruby stuff, there are a lot of similarities.

Re: working on the dlang.org website

On Tue, Jul 23, 2013 at 09:47:02AM +0200, nazriel wrote: [...] > Hyphenate.js indeed has an impact on load times and removing it > in favor of CSS3 would fix the problem. Of course there is > probability that people with '90s browsers will complain (stares > at Nick ;>) but it is their choice to st

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 14:48:11 UTC, H. S. Teoh wrote: Seriously, we need to take a deep breath, step back, and get the right perspective on things. Hyphenation is mostly a *non-issue*. Most people don't even notice it! Here is yet another point of view - hyphenation makes text ugly and m

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 14:56:46 UTC, Dicebot wrote: Here is yet another point of view - hyphenation makes text ugly and more difficult to read It certainly looks strange as it's unusual for the web.

Re: working on the dlang.org website

On 2013-07-23 15:19, Dicebot wrote: There is nothing here D can't do. Dogfooding ftw. I give up, there's obviously no point in arguing. -- /Jacob Carlborg

Re: working on the dlang.org website

23-Jul-2013 18:46, H. S. Teoh пишет: On Tue, Jul 23, 2013 at 09:47:02AM +0200, nazriel wrote: [...] Hyphenate.js indeed has an impact on load times and removing it in favor of CSS3 would fix the problem. Of course there is probability that people with '90s browsers will complain (stares at Nick

Re: working on the dlang.org website

On 7/23/2013 2:23 AM, Borden wrote: On Sunday, 14 July 2013 at 20:35:45 UTC, Walter Bright wrote: 3. HTML, PDF, Ebook, and CHM outputs are generated from Ddoc. Walter, with respect, I know you're too smart to be saying something silly like this. Surely you know that ebooks and CHM are special

Re: working on the dlang.org website

On Tuesday, 23 July 2013 at 21:00:08 UTC, Walter Bright wrote: But in general, PR's that are flagged as "We can’t automatically merge this pull request" tend to not get much attention. Despite that, we can and should do better. Only committers see that notice. Contributors who do not have com

Re: working on the dlang.org website

On 7/23/2013 4:57 PM, Vladimir Panteleev wrote: On Tuesday, 23 July 2013 at 21:00:08 UTC, Walter Bright wrote: But in general, PR's that are flagged as "We can’t automatically merge this pull request" tend to not get much attention. Despite that, we can and should do better. Only committers se

Re: working on the dlang.org website

On Tuesday, July 23, 2013 17:42:30 Walter Bright wrote: > On 7/23/2013 4:57 PM, Vladimir Panteleev wrote: > > On Tuesday, 23 July 2013 at 21:00:08 UTC, Walter Bright wrote: > >> But in general, PR's that are flagged as "We can’t automatically merge > >> this > >> pull request" tend to not get much

Re: working on the dlang.org website

On 2013-07-24 01:57, Vladimir Panteleev wrote: Only committers see that notice. Contributors who do not have commit access do not see that notice. If you need a pull request author to update their pull request, you need to let them know explicitly. I thought I he was referring to the auto test

Re: working on the dlang.org website

On Wednesday, 24 July 2013 at 06:44:25 UTC, Jacob Carlborg wrote: On 2013-07-24 01:57, Vladimir Panteleev wrote: Only committers see that notice. Contributors who do not have commit access do not see that notice. If you need a pull request author to update their pull request, you need to let t

Re: working on the dlang.org website

On 2013-07-24 12:16, Vladimir Panteleev wrote: This does not apply to the dlang.org repo, which is not being tested. Right. It should though, then it can catch merge and compile errors. -- /Jacob Carlborg

Re: working on the dlang.org website

Anybody gets a timeout in hyphenate.js on http://dlang.org/phobos/core_memory.html ? A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://dlang.org/js/hyphenate.js:55 ---

Re: working on the dlang.org website

On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: Anybody gets a timeout in hyphenate.js on http://dlang.org/phobos/core_memory.html ? A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will c

Re: working on the dlang.org website

On Tue, Jul 30, 2013 at 06:25:30PM +0200, Damian wrote: > On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: > >Anybody gets a timeout in hyphenate.js on > >http://dlang.org/phobos/core_memory.html ? > > > > > >A script on this page may be busy, or it may have stopped > >responding. You c

Re: working on the dlang.org website

On Tuesday, 30 July 2013 at 16:48:49 UTC, H. S. Teoh wrote: On Tue, Jul 30, 2013 at 06:25:30PM +0200, Damian wrote: On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: >Anybody gets a timeout in hyphenate.js on >http://dlang.org/phobos/core_memory.html ? > > >A script on this page may b

Re: working on the dlang.org website

On 7/30/13, John Colvin wrote: > I really wish I could do that. Unfortunately I need js for the > forum split-view and NotScripts isn't sophisticated enough to > whitelist subdomains. I use YesScript to block JS in specific websites, maybe that could work for you.

Re: working on the dlang.org website

On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: Anybody gets a timeout in hyphenate.js on http://dlang.org/phobos/core_memory.html ? A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will c

Re: working on the dlang.org website

On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: Anybody gets a timeout in hyphenate.js on http://dlang.org/phobos/core_memory.html ? A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will c

Re: working on the dlang.org website

On 07/30/2013 02:00 PM, Wyatt wrote: On Tuesday, 30 July 2013 at 16:18:38 UTC, Kagamin wrote: Anybody gets a timeout in hyphenate.js [..] Yeah. I've seen it. Even though it's supposed to be disabled for Firefox. I'm waiting eagerly for this pull request to get merged so we can end this farce:

Re: working on the dlang.org website

On Wednesday, 31 July 2013 at 07:35:34 UTC, Jeff Nowakowski wrote: By the way, the worst idea I've seen is to do hyphenation statically on the server side. How does the server know in advance how wide my browser window is or the text size? It can't. It's the client's job to flow the text. Bot

Re: working on the dlang.org website

On Wednesday, 31 July 2013 at 14:14:50 UTC, Vladimir Panteleev wrote: On Wednesday, 31 July 2013 at 07:35:34 UTC, Jeff Nowakowski wrote: By the way, the worst idea I've seen is to do hyphenation statically on the server side. How does the server know in advance how wide my browser window is or

Re: working on the dlang.org website

On Wednesday, 31 July 2013 at 21:50:15 UTC, Brad Anderson wrote: Someone in IRC, Hackerpilot I believe, related how they copied and pasted some code from dlang.org into their editor and random things weren't getting syntax highlighted. He only noticed what was causing it when he was moving th

Re: working on the dlang.org website

On 07/31/2013 10:14 AM, Vladimir Panteleev wrote: On Wednesday, 31 July 2013 at 07:35:34 UTC, Jeff Nowakowski wrote: By the way, the worst idea I've seen is to do hyphenation statically on the server side. How does the server know in advance how wide my browser window is or the text size? It can

Re: working on the dlang.org website

Better late than never (the last couple weeks have been very busy): On Tuesday, 23 July 2013 at 21:00:08 UTC, Walter Bright wrote: It's true that they are based on HTML output. However, and this is a big however, they need significantly different HTML output than one puts on a web site. This i

Re: working on the dlang.org website

On Sunday, 14 July 2013 at 04:56:46 UTC, Val Markovic wrote: So, Andrei also mentioned how the community needs to improve the dlang.orgsite and make it a first-class priority. It's the point of contact for newcomers so it's very important we get it right. Since I know a thing-or-two about web

Re: working on the dlang.org website

On Saturday, 10 August 2013 at 17:29:40 UTC, Ruslan Mullakhmetov wrote: (2) Flashing and slow responses are annoying but not so crucial (as from my experience), thought somebody waits for up to 7 seconds to load web page - agree, that should be fixed, but again, i do not have such problem or di

Re: working on the dlang.org website

On Saturday, 10 August 2013 at 18:22:53 UTC, Brad Anderson wrote: On Saturday, 10 August 2013 at 17:29:40 UTC, Ruslan Mullakhmetov wrote: (2) Flashing and slow responses are annoying but not so crucial (as from my experience), thought somebody waits for up to 7 seconds to load web page - agree,

Re: working on the dlang.org website

On 08/10/2013 04:32 PM, Kapps wrote: The documentation is still almost unusable for me. If I load a tab to view any documentation (example link: http://dlang.org/phobos/object.html#.RTInfo) it will literally freeze Firefox (26, Nightly, happened with 25 and previous versions as well) completely

Re: working on the dlang.org website

On Sat, Aug 10, 2013 at 05:59:08PM -0400, Jeff Nowakowski wrote: > On 08/10/2013 04:32 PM, Kapps wrote: > > > >The documentation is still almost unusable for me. If I load a tab to > >view any documentation (example link: > >http://dlang.org/phobos/object.html#.RTInfo) it will literally freeze > >F

Re: working on the dlang.org website

On 8/10/2013 6:06 AM, Borden wrote: Therefore, regardless of how irrational your customers are, there is often a benefit to giving them what they want. Rarely do all customers want the same thing.

Re: working on the dlang.org website

I found a nice documentation website : http://docs.autodesk.com/FBX/2014/ENU/FBX-SDK-Documentation/index.html?url=cpp_ref/_common_2_common_8cxx-example.html,topicNumber=cpp_ref__common_2_common_8cxx_example_htmlc507b7ce-aa2f-4c44-b08f-90c94f43730b There is all sources of sample, and code is highl

  1   2   >