Reggae binary backend: build your project with a D compiled executable
Original discussion: http://forum.dlang.org/post/ranqlmrjornlvopsu...@forum.dlang.org Now, with the `-b binary` option, reggae creates an executable called build in the build directory (i.e. wherever the CWD was when calling the tool) that knows how to build the project. If needed, there is no longer a dependency on make or ninja. I haven't tested it extensively, but it does pass all the other tests I wrote for make and ninja, so it looks good. Atila
Re: forum.dlang.org, version 2 (BETA)
On Thursday, 4 June 2015 at 15:04:05 UTC, Vladimir Panteleev wrote: http://beta.forum.dlang.org/ Many major and minor improvements. Some major ones: - dlang.org theme, fully responsive and mobile-friendly - keyboard navigation in all views - automatically saved post drafts - get notified of new posts and replies with subscriptions - full text search - by persistent request, a new view mode (vertical-split) - post to mailing lists - even faster, believe it or not. This update is the sum of 256 commits over 34 days of development. Much nicer reading posting from mobile browser. Thanks! :-)
Re: forum.dlang.org, version 2 (BETA)
On 2015-06-05 14:57, Vladimir Panteleev wrote: 1. People receiving messages through NNTP/mailing lists will not see the formatted Markdown. Although Markdown's goal is to be readable in its plain text source code, it still allows many situations in which the source is misleading or difficult to understand. For example, special characters need to be escaped by a backslash, which can create confusion in the presence of other special characters. (Are they part of the D syntax the user is describing, or something else?) Some syntax such as tables or images can also be not very readable in source form. Some people are already sending something that looks like Markdown, i.e. ``` for code blocks. Even your post can be rendered as Markdown. 2. How should we render messages sent by NNTP/mailing-list users? Do we just assume that they're sending Markdown and render it as such? This can cause the messages to appear broken to forum users. Or do we only render Markdown if the post was sent from the forum? This means that when NNTP/ML users quote forum users' text it will be shown as plain text. 3. There is no unified standard for Markdown. The original format is not used on major sites today - StackOverflow and GitHub extend the format, and users will expect Markdown with those extensions. That standard would be the one GibHub uses. 5. You can't edit posts once sent. This means that if you accidentally messed up the formatting (e.g. you pasted code without padding it with whitespace or surrounding it in ```...``` blocks), you can't go back and edit it now. A preview button/view would (hopefully) solve that. -- /Jacob Carlborg
Re: forum.dlang.org, version 2 (BETA)
On 2015-06-05 03:45, Vladimir Panteleev wrote: It's doable but just seems a little overkill to me. Every time I looked into implementing OAuth I was swamped by how overly complicated it was (or maybe I just never found a succint-enough description). What about hooking up Github accounts or something similar? -- /Jacob Carlborg
Re: forum.dlang.org, version 2 (BETA)
On 2015-06-04 17:04, Vladimir Panteleev wrote: http://beta.forum.dlang.org/ Many major and minor improvements. Some major ones: - dlang.org theme, fully responsive and mobile-friendly - keyboard navigation in all views - automatically saved post drafts - get notified of new posts and replies with subscriptions - full text search - by persistent request, a new view mode (vertical-split) - post to mailing lists - even faster, believe it or not. This update is the sum of 256 commits over 34 days of development. Unfortunately I'm a bit disappointed. I mostly use the forum on my phone and to me it's barley any improvement at all. The problem I see are: * The font is too small in portrait mode. It's good in landscape mode * The two (index) and three columns (viewing a group) views don't really work. They truncate too much of the text. Perhaps using a different layout that is more suitable for phones could be used * All links except that ones inline in a post is too small. The breadcrumbs, settings, help and the pager. It's mostly the pager that is important * It looks like the site decreases the font size when the window gets more narrow, is that really necessary? Perhaps that's why I think the font size is too small in portrait mode * Still no pager on top :( . This is not just on the phone * I don't think it's necessary on a desktop size that page stretches out and uses the complete width. I think most responsive site has some form of max width on the page. At some point it's not necessary to increase the width any more, it just adds unnecessary whitespace The combination of a too small font size a too small pager is why I'm so disappointed. If I need to zoom on a responsive site the whole responsiveness has failed On the plus side, the links inline in the posts seem to be properly wrapped now and doesn't break the layout :) I'm using an iPhone 6, the smaller one. -- /Jacob Carlborg
Re: forum.dlang.org, version 2 (BETA)
On 2015-06-05 03:37, Vladimir Panteleev wrote: Except for the bold part, believe it or not, it's exactly the same font as we use on dlang.org, size and all (Verdana 14px). And as for the bold part, it doesn't look so bad on Windows, so what does that say about the famed OS X font rendering? :D I think it looks good (both in Firefox and Safari), the same as on form.dlang.org, just bigger. -- /Jacob Carlborg
Re: forum.dlang.org, version 2 (BETA)
Before I forget: avatar photo covers text. http://imgur.com/8r679dX -- Andrei
Simple http client Dlang library
Hello! I've created AllUCanGET, a very simple D2 http client library which you could use instead of std.net.curl module to make http connections. You can find the library with more information here: a href=http://allucanget.diaboli.pl/;http://allucanget.diaboli.pl//a.
Re: Reggae binary backend: build your project with a D compiled executable
On Sat, 06 Jun 2015 20:07:20 +, Atila Neves wrote: Original discussion: http://forum.dlang.org/post/ranqlmrjornlvopsu...@forum.dlang.org Now, with the `-b binary` option, reggae creates an executable called build in the build directory (i.e. wherever the CWD was when calling the tool) that knows how to build the project. If needed, there is no longer a dependency on make or ninja. I haven't tested it extensively, but it does pass all the other tests I wrote for make and ninja, so it looks good. Atila wow. now i'm really thinking about migrating to Reggae! ;-) signature.asc Description: PGP signature
Re: Simple http client Dlang library
On Sat, 06 Jun 2015 22:20:19 +, kryszczyniak wrote: Hello! I've created AllUCanGET, a very simple D2 http client library which you could use instead of std.net.curl module to make http connections. You can find the library with more information here: a href=http://allucanget.diaboli.pl/;http://allucanget.diaboli.pl//a. nice work, but... no sources? that means no win64 support, no gdc support, no ldc support, no freebsd support too, i believe... signature.asc Description: PGP signature
Re: Reggae binary backend: build your project with a D compiled executable
On Saturday, 6 June 2015 at 20:07:22 UTC, Atila Neves wrote: Original discussion: http://forum.dlang.org/post/ranqlmrjornlvopsu...@forum.dlang.org Now, with the `-b binary` option, reggae creates an executable called build in the build directory (i.e. wherever the CWD was when calling the tool) that knows how to build the project. If needed, there is no longer a dependency on make or ninja. I haven't tested it extensively, but it does pass all the other tests I wrote for make and ninja, so it looks good. I like what you're doing with reggae, and I salute the work. I will reiterate my suggestion to consider making Reggae a simple package import so this build functionality can be used in anyone's D program, including the Reggae tool. We already have the ability to generate a binary with the compiler, so the binary backend seems a little redundant. You have all the great features one would need: Targets, dependencies, flags, build driver, etc... so it seems plausible to move some of your driver code to the payload/reggae package to make one's task of building a custom driver trivial. I don't suggest making a libreggae library as a separate repository from the Reggae tool, but rather simply do the refactoring to make payload/reggae folder importable from any D program, including the Reggae tool itself. Mike
Re: forum.dlang.org, version 2 (BETA)
On Saturday, 6 June 2015 at 16:02:23 UTC, Andrei Alexandrescu wrote: Before I forget: avatar photo covers text. http://imgur.com/8r679dX -- Andrei I think it's otherwise! :) Matheus.
