Re: To all DConf speakers: please upload slides!
On Thursday, 12 May 2016 at 23:14:05 UTC, Leandro Lucarella wrote: Steven Schveighoffer, el 12 de May a las 16:55 me escribiste: On 5/12/16 4:13 PM, Seb wrote: >On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: >>To do the editing of HD videos we need presentation slides >>which are currently scattered over different places. It >>would help a lot to have them all in >>github.com/dlang/dlang.org repo - please submit pull >>requests asap! > >Just a minor complaint - would it be possible for the next >dconf to have the slides (or a link to them) on dconf.org >before the talk starts? Thanks for the great work! I think it's better to not have the slides available until the talk starts. There may be jokes/surprises in the slides that you don't want to give away before the talk happens :) Exactly, I would say it depends on the talk, for my talk I didn't want to provide the slides beforehand ;-) Here's a crazy idea: provide a simple/short URL to the slides as the second slide of your talk (and speak out loud the URL just in case the camera doesn't get it) :) Bonus: getting the slides on the presenting machine becomes easy too. (Just make sure that the relevant software supports the features that your presentation uses, cough...)
Re: To all DConf speakers: please upload slides!
Steven Schveighoffer, el 12 de May a las 16:55 me escribiste: > On 5/12/16 4:13 PM, Seb wrote: > >On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: > >>To do the editing of HD videos we need presentation slides which are > >>currently scattered over different places. It would help a lot to have > >>them all in github.com/dlang/dlang.org repo - please submit pull > >>requests asap! > > > >Just a minor complaint - would it be possible for the next dconf to have > >the slides (or a link to them) on dconf.org before the talk starts? > >Thanks for the great work! > > I think it's better to not have the slides available until the talk > starts. There may be jokes/surprises in the slides that you don't > want to give away before the talk happens :) Exactly, I would say it depends on the talk, for my talk I didn't want to provide the slides beforehand ;-) -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ -- 1950 we were 3 billion people on the earth, today we are 6 billion people
Re: Adventures in D Programming
Dne 12.5.2016 v 23:08 Matthias Klumpp via Digitalmars-d-announce napsal(a): First of all, that blogpost generated way more buzz than I expected - looks like D is highly interesting to people, which is great news :-) To elaborate a bit more on the version incompatibilities thing: E.g. me as a new user reads about std.concurrency.Generator, wants to use it, and it turns out that the standard library doesn't contain it yet (in GDC). Same for std.experimental.logger. Okay, means I can't use these. This is something I do not like. It would be awesome if I could use new version of phobos (dub package for eg.) in a dmd, ldc or gdc. Having language which is so unstable so is almost impossible to use standard library with older frontend is really anoying. Then, I wanted to use std.getopt - turns out the semantics have changed and new stuff has been added there too, which I can't use. Meh, if the docs would have at least told me that. I knew it :). I end up with same problem with std.getopt. It was a reason for this post: http://forum.dlang.org/post/srhttrxrqawhspibd...@forum.dlang.org std.getopt has been backward compatible but it was not forward compatible. So because there is only latest docs available you are doomed :(. Then, I want to use D-YAML, which depends on std.stream. But std.stream is completely deprecated, with no clear path for me to see to replace it. That's really bad, and it also means I can't compile my code with making the use of deprecated stuff fail the compilation. I am not sure what exactly this deprecation message say, but you definitely should not used std.stream at all in a first place ;-). That was by far the most frustrating things I experienced in D. So ideally the docs would be split for different Phobos versions, that would already be a great help. Yes this would help a lot. Then, when deprecating stuff, showing a thing that replaces it or the proper way to write code using it would also be really nice. E.g. wile I welcome the deprecation of std.net.curl in principle (having to link against an external library in the standard lib is odd), announcing to drop it before any replacement which offers feature-parity is written is bad (sidenote: IMHO the advanced net stuff shouldn't be in the standard library, because it's harder to update in case of security updates and bad crypto). It would actually be really awesome if Phobos wasn't tied to a compiler, and all D compilers which are standard-compliant could compile it. Then, one could assume that people have the most recent Phobos. But it looks like it will take a longer time to get there, if at all. I hope it would not take so much time. This is really important if D want to succeed. Another thing that I didn't mention in the blogpost, but which might be interesting is that D - unlike Rust and Go - doesn't have a way that lets developers do a shallow-dive into the language by giving practical examples. For example, Go has the really awesome Go Tour[1] which lets you explore and learn the basic concepts of the language by example. For me, going through the tour was enough to actually start writing Go code, and while it certainly isn't complete, it is a nice way to show off the language and give people a taste of how it looks like. Rust has something similar with its tutorial[2]. For D, I haven't found an "in a nutshell" tutorial, and needed to read a bit more documentation and employ my existing C/C++ knowledge in some cases. Having something like the Go tour for D would IMHO be an wesome way to attract people to try D. There is already http://tour.dlang.io, but I do not have yet time to try it so I can't speak about maturity and so on. Other problem is with complexity of D. I believe even I can write book about D, which make people able to write almost anything in D. But they will not be able to read all D code. Go is OTOH really easy language so you need book with around 200 pages to explain everything. But with D I am not sure that even 1000 of pages would be enough :(. Cheers, Matthias [1]: https://tour.golang.org/welcome/1 [2]: https://doc.rust-lang.org/book/guessing-game.html
Re: To all DConf speakers: please upload slides!
Dne 12.5.2016 v 22:55 Steven Schveighoffer via Digitalmars-d-announce napsal(a): On 5/12/16 4:13 PM, Seb wrote: On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation slides which are currently scattered over different places. It would help a lot to have them all in github.com/dlang/dlang.org repo - please submit pull requests asap! Just a minor complaint - would it be possible for the next dconf to have the slides (or a link to them) on dconf.org before the talk starts? Thanks for the great work! I think it's better to not have the slides available until the talk starts. No, you are wrong. It would be really nice to have them. I would say it was one of the biggest failures of dconf for people who can't attend. There may be jokes/surprises in the slides that you don't want to give away before the talk happens :) -Steve If there is anything you do not want to make available before talks. You don't have to ;).
Re: Adventures in D Programming
On 05/12/2016 11:08 PM, Matthias Klumpp wrote: Then, I want to use D-YAML, which depends on std.stream. But std.stream is completely deprecated, with no clear path for me to see to replace it. That's really bad, and it also means I can't compile my code with making the use of deprecated stuff fail the compilation. Deprecations are warnings by default. Using deprecated stuff shouldn't fail compilation unless you're using `-de` (dmd flag). E.g. wile I welcome the deprecation of std.net.curl in principle (having to link against an external library in the standard lib is odd), announcing to drop it before any replacement which offers feature-parity is written is bad I don't think that has been announced. It's only been discussed, no? For D, I haven't found an "in a nutshell" tutorial, and needed to read a bit more documentation and employ my existing C/C++ knowledge in some cases. Having something like the Go tour for D would IMHO be an wesome way to attract people to try D. That's being worken on: http://tour.dlang.io/
Re: Adventures in D Programming
On Monday, 9 May 2016 at 09:29:36 UTC, qznc wrote: On Sunday, 8 May 2016 at 22:22:08 UTC, Peter Häggman wrote: [...] You've quoted the wrong part of the paragraph. The real problem he encountered was not the doc, it was the phobos bugs in the older version shipped with GDC/LDC: "For GDC, which I used to compile my code due to LDC having bugs at that time, this means that it is shipping with a very outdated copy of Phobos" The the doc thing is "just" a symptom. Older offline doc is always available in the release archive, it's easy to understand that so it's not the actual problem. You are correct, but can this be solved? Newer Phobos versions fix bugs. GDC needs a newer Phobos? Well, this is translated into GDC needs more manpower. Everything does. Nothing new. First of all, that blogpost generated way more buzz than I expected - looks like D is highly interesting to people, which is great news :-) To elaborate a bit more on the version incompatibilities thing: E.g. me as a new user reads about std.concurrency.Generator, wants to use it, and it turns out that the standard library doesn't contain it yet (in GDC). Same for std.experimental.logger. Okay, means I can't use these. Then, I wanted to use std.getopt - turns out the semantics have changed and new stuff has been added there too, which I can't use. Meh, if the docs would have at least told me that. Then, I want to use D-YAML, which depends on std.stream. But std.stream is completely deprecated, with no clear path for me to see to replace it. That's really bad, and it also means I can't compile my code with making the use of deprecated stuff fail the compilation. That was by far the most frustrating things I experienced in D. So ideally the docs would be split for different Phobos versions, that would already be a great help. Then, when deprecating stuff, showing a thing that replaces it or the proper way to write code using it would also be really nice. E.g. wile I welcome the deprecation of std.net.curl in principle (having to link against an external library in the standard lib is odd), announcing to drop it before any replacement which offers feature-parity is written is bad (sidenote: IMHO the advanced net stuff shouldn't be in the standard library, because it's harder to update in case of security updates and bad crypto). It would actually be really awesome if Phobos wasn't tied to a compiler, and all D compilers which are standard-compliant could compile it. Then, one could assume that people have the most recent Phobos. But it looks like it will take a longer time to get there, if at all. Another thing that I didn't mention in the blogpost, but which might be interesting is that D - unlike Rust and Go - doesn't have a way that lets developers do a shallow-dive into the language by giving practical examples. For example, Go has the really awesome Go Tour[1] which lets you explore and learn the basic concepts of the language by example. For me, going through the tour was enough to actually start writing Go code, and while it certainly isn't complete, it is a nice way to show off the language and give people a taste of how it looks like. Rust has something similar with its tutorial[2]. For D, I haven't found an "in a nutshell" tutorial, and needed to read a bit more documentation and employ my existing C/C++ knowledge in some cases. Having something like the Go tour for D would IMHO be an wesome way to attract people to try D. Cheers, Matthias [1]: https://tour.golang.org/welcome/1 [2]: https://doc.rust-lang.org/book/guessing-game.html
Re: To all DConf speakers: please upload slides!
On 5/12/16 4:13 PM, Seb wrote: On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation slides which are currently scattered over different places. It would help a lot to have them all in github.com/dlang/dlang.org repo - please submit pull requests asap! Just a minor complaint - would it be possible for the next dconf to have the slides (or a link to them) on dconf.org before the talk starts? Thanks for the great work! I think it's better to not have the slides available until the talk starts. There may be jokes/surprises in the slides that you don't want to give away before the talk happens :) -Steve
Re: 2DRPG - Small console game
On Thu, May 12, 2016 at 06:30:04PM +, Vladimirs Nordholm via Digitalmars-d-announce wrote: [...] > Sadly this game is Windows only, meaning POSIX users cannot play it. > This is due to technical limitations in my own console engine, scone > (https://github.com/vladdeSV/scone), which cannot read input on POSIX > terminals. [...] Have you looked at Adam Ruppe's terminal.d? https://github.com/adamdruppe/arsd/blob/master/terminal.d It provides uniform access to Posix and Windows consoles, and can handle rudimentary colors, tile-based screen access, as well as keystroke / mouse events. I've been using it in my own console projects, and it works quite well. T -- Do not reason with the unreasonable; you lose by definition.
Re: To all DConf speakers: please upload slides!
On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation slides which are currently scattered over different places. It would help a lot to have them all in github.com/dlang/dlang.org repo - please submit pull requests asap! Just a minor complaint - would it be possible for the next dconf to have the slides (or a link to them) on dconf.org before the talk starts? Thanks for the great work!
Re: 2DRPG - Small console game
On Thursday, 12 May 2016 at 18:30:04 UTC, Vladimirs Nordholm wrote: I have had lots of fun during the development of 2DRPG. There have been many difficulties, but I have learned much from making this game. Sadly this game is Windows only, meaning POSIX users cannot play it. This is due to technical limitations in my own console engine, scone (https://github.com/vladdeSV/scone), which cannot read input on POSIX terminals. If anyone would like to test the game, it would be awesome. Any sort of feedback is always appreciated! I managed to build and run it under wine/wineconsole and make it through one playthrough. The only issue is that all the non-printable characters showed up as euro signs, I guess I may need to play with the font selection some more for that. Games with time limits are not my cup of tea - other than that, it was nice, well done.
2DRPG - Small console game
For the past couple of months me and my classmate have been working on a small console game, which we will compete with in a game creation competition arranged by my school. Deadline was today (12 May, 2016), and I am glad to announce the first playable, completable version of 2DRPG is now available! Github repo at https://github.com/vladdeSV/2drpg 'Tile-based exploration game, in which you take place as someone. Craft items to help your way, or complete quests to satisfy the inhabitants of this world.' Programmed by me (vladde) and designed by classmate Fredrik, this game features up to half an hour gameplay, with humorous and strange vibes. I have had lots of fun during the development of 2DRPG. There have been many difficulties, but I have learned much from making this game. Sadly this game is Windows only, meaning POSIX users cannot play it. This is due to technical limitations in my own console engine, scone (https://github.com/vladdeSV/scone), which cannot read input on POSIX terminals. If anyone would like to test the game, it would be awesome. Any sort of feedback is always appreciated! Greetings, vladde
Re: To all DConf speakers: please upload slides!
On Wednesday, 11 May 2016 at 09:17:54 UTC, Dicebot wrote: To do the editing of HD videos we need presentation slides which are currently scattered over different places. It would help a lot to have them all in github.com/dlang/dlang.org repo - please submit pull requests asap! Lightning talk slides also to be included? Mine are at http://biobeat.org/dconf2016.pdf
Re: DustMite now has -j
On 5/11/16 10:53 PM, Vladimir Panteleev wrote: By popular demand. https://github.com/CyberShadow/DustMite/compare/e175b95da070d84029f75ba8a15f5d900fb90704...15693cbd5a5c0f47ee9cc68be9dada39b99c3836 Fantastic. Thanks!! -- Andrei
Re: dplug v3.0.0, added Audio Unit support
On Wednesday, 11 May 2016 at 15:52:06 UTC, Guillaume Piolat wrote: Audio Unit format has been implemented as of dplug version 3. A technical hurdle was to be able to pass Objective-C classes implementing an Objective-C @protocol. @protocols are a bit like D interfaces for which the compiler creates dispatch tables at compile-time. The solution is to create a similarly named @protocol with same methods to simulate this work, using the ObjC runtime. https://github.com/p0nce/dplug/blob/master/au/dplug/au/cocoaviewfactory.d#L81
