Re: Deadcode - Widgets and Styling post
On Monday, 9 February 2015 at 22:36:45 UTC, David Ellsworth wrote: On Monday, 9 February 2015 at 21:08:18 UTC, Brad Anderson wrote: I've never seen anyone post under the name deadcode on the forums so don't think there is much potential for confusion (especially since one is a project and another is a person). I think you should keep the name. Well, even if I do start posting here more frequently, I think I'll still be okay with this. As you said one is a project and the other is a person! I don't think anybody here will be confused. :) Cool. If you are ok with it then I'll stick with the name. Thx. Jonas
Re: DDocs.org: auto-generated documentation for all DUB projects (WIP)
On 11/02/2015 11:40 a.m., Kiith-Sa wrote: DDocs.org (http://ddocs.org) is a repository of documentation for DUB projects that automatically re-generates docs as new projects/releases/branch changes are added. The idea is to make documenting D projects as simple as possible, to the point where you don't need to do any work to get documentation for your project other than adding it to the DUB registry. Also, users can now browse documentation for DUB projects even if the author was too lazy to generate it themselves (assuming thy did include some documentation comments). Note that this is still in a very early stage, it was put together in a very quick-and-dirty style by a person with little webdev experience. Currently it just scans `code.dlang.org`, looking for changes (yes, I know, this will break as soon as code.dlang.org changes, I plan to raise issue/s (PRs?) to the dub registry project so it can have a full/stable API, but I wanted to get something to work *right now*. Code is here: * ddocs.org: https://github.com/kiith-sa/ddocs.org * hmod-dub: https://github.com/kiith-sa/hmod-dub * harbored-mod: https://github.com/kiith-sa/harbored-mod Background: When optimizing harbored-mod by testing it on big D projects (gtk-d, tango, vibe.d, etc.), I wrote a simple tool to fetch/generate docs for any DUB project; I got carried away and used that as base for a tool that checks for changes in the DUB registry and generates docs for all projects. Right this needs to be made first class link wise on dlang.org and code.dlang.org
Re: Pragmatic D Tutorial
On Mon 07/10/2013 21:18, qznc wrote: I believe one of the things D needs right now is more documentation. Therefore, I started writing a tutorial. It is aimed at people who can already program well in other languages. This means nothing about loops or structs, because I expect most people to know this stuff. I do not consider D to be a language for beginners anyways. It is aiming for pragmatic not comprehensive advice. For example, I mostly ignore LDC and GDC except for the optimization chapter. Since I am working on Linux exclusively and I like the command line, I cannot teach to Windows users. Sorry. This is still very incomplete and my our newborn family member requires quite some attention. So expect this to develop with glacial speed. ;) Nevertheless, I want to put this version 0.1 out to get some feedback. What do you think about the topic selection? What topics are missing? Serious errors so far? http://beza1e1.tuxen.de/d-tut-0.1/index.html Wreck it! :) Is this still being updated? It fairly extensive. How much of this is integrated in wiki/dlang?
Re: DlangIDE
On Tuesday, 10 February 2015 at 14:05:38 UTC, Vadim Lopatin wrote: On Friday, 6 February 2015 at 18:31:19 UTC, extrawurst wrote: Good work! On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote: * Code completion * Go to definition Please do not create yet another parser/lexer for this, looks like DCD would be a good fit for the job: https://github.com/Hackerpilot/DCD ~Stephan Ok, I will check it. BWT, thank you for pull request with build log parsing and navigation to place of error or warning in code. My pleasure, I am really looking forward for this IDE, I think it has all the features I want in an awesome showcase of a D Product: * all written in D * platform independent * assembling mature D tools like DCD for code completion and DScanner for analysis (To-Be-Done i know) I think focusing on the last part is important because it speeds up development and makes use of the great and proven work of others instead of reinventing the wheel. added an issue to track ideas on DCD integration: https://github.com/buggins/dlangide/issues/20 ~Stephan
Re: DConf 2015 Second call for proposals
On Tuesday, 10 February 2015 at 20:02:32 UTC, Andrei Alexandrescu wrote: Hi everyone, The call for proposals for DConf 2015 has had scarce response until now. Please consider submitting before the deadline on February 28. There's a lot of interesting recent work on D that provides a rich basis for dissemination. Please consider submitting stuff you consider interesting. Even if you didn't create a specific artifact, if you are an expert in it you should consider presenting it with credit. (This is common at such events and has occurred in the past at DConf with great success - see e.g. Vladimir's excellent overview of Web tooling for D.) Just like in the past editions, DConf depends on you - literally. DConf can only take place if it has enough valuable content. Please consider sharing your work. Thanks, Andrei I didn't see it mentioned anywhere, so I presume there isn't any financial assistance for travel costs for speakers this year. Is that correct?
DConf 2015 Second call for proposals
Hi everyone, The call for proposals for DConf 2015 has had scarce response until now. Please consider submitting before the deadline on February 28. There's a lot of interesting recent work on D that provides a rich basis for dissemination. Please consider submitting stuff you consider interesting. Even if you didn't create a specific artifact, if you are an expert in it you should consider presenting it with credit. (This is common at such events and has occurred in the past at DConf with great success - see e.g. Vladimir's excellent overview of Web tooling for D.) Just like in the past editions, DConf depends on you - literally. DConf can only take place if it has enough valuable content. Please consider sharing your work. Thanks, Andrei
Re: DDocs.org: auto-generated documentation for all DUB projects (WIP)
On Tuesday, 10 February 2015 at 22:40:18 UTC, Kiith-Sa wrote: DDocs.org (http://ddocs.org) is a repository of documentation for DUB projects that automatically re-generates docs as new projects/releases/branch changes are added. Killer project! Nice work!
Re: DDocs.org: auto-generated documentation for all DUB projects (WIP)
On Tuesday, 10 February 2015 at 23:53:19 UTC, MrSmith wrote: On Tuesday, 10 February 2015 at 22:40:18 UTC, Kiith-Sa wrote: DDocs.org (http://ddocs.org) is a repository of documentation for DUB projects that automatically re-generates docs as new projects/releases/branch changes are added. The idea is to make documenting D projects as simple as possible, to the point where you don't need to do any work to get documentation for your project other than adding it to the DUB registry. Also, users can now browse documentation for DUB projects even if the author was too lazy to generate it themselves (assuming thy did include some documentation comments). Note that this is still in a very early stage, it was put together in a very quick-and-dirty style by a person with little webdev experience. Currently it just scans `code.dlang.org`, looking for changes (yes, I know, this will break as soon as code.dlang.org changes, I plan to raise issue/s (PRs?) to the dub registry project so it can have a full/stable API, but I wanted to get something to work *right now*. Code is here: * ddocs.org: https://github.com/kiith-sa/ddocs.org * hmod-dub: https://github.com/kiith-sa/hmod-dub * harbored-mod: https://github.com/kiith-sa/harbored-mod Background: When optimizing harbored-mod by testing it on big D projects (gtk-d, tango, vibe.d, etc.), I wrote a simple tool to fetch/generate docs for any DUB project; I got carried away and used that as base for a tool that checks for changes in the DUB registry and generates docs for all projects. That is pretty cool! I will put a link to it in all my project readmes. I've noticed that License: a$(WEB boost.org/LICENSE_1_0.txt, Boost License 1.0). gets rendered as a. Am I doing it wrong? There's a bunch of macros used in many D projects not documented in the language reference. They seem to be defined somewhere in Phobos/Druntime (? - not sure), not really built in, but I add them as I find them so compatibility is kept. Added $WEB to harbored-mod now. There already also is LINK, LINK2, and HTTP... and of course Markdown [link](http://link.org) - but that doesn't work with plain DDoc generators. The change can take a while to propagate to your packages as ddocs.org waits a few days before regenerating docs for releases that already have docs generated and 2 days for known branches (~master) so it doesn't constantly regenerate docs for everything - it is feasible now but won't be if the DUB registry gets bigger as fast as I expect.
DDocs.org: auto-generated documentation for all DUB projects (WIP)
DDocs.org (http://ddocs.org) is a repository of documentation for DUB projects that automatically re-generates docs as new projects/releases/branch changes are added. The idea is to make documenting D projects as simple as possible, to the point where you don't need to do any work to get documentation for your project other than adding it to the DUB registry. Also, users can now browse documentation for DUB projects even if the author was too lazy to generate it themselves (assuming thy did include some documentation comments). Note that this is still in a very early stage, it was put together in a very quick-and-dirty style by a person with little webdev experience. Currently it just scans `code.dlang.org`, looking for changes (yes, I know, this will break as soon as code.dlang.org changes, I plan to raise issue/s (PRs?) to the dub registry project so it can have a full/stable API, but I wanted to get something to work *right now*. Code is here: * ddocs.org: https://github.com/kiith-sa/ddocs.org * hmod-dub: https://github.com/kiith-sa/hmod-dub * harbored-mod: https://github.com/kiith-sa/harbored-mod Background: When optimizing harbored-mod by testing it on big D projects (gtk-d, tango, vibe.d, etc.), I wrote a simple tool to fetch/generate docs for any DUB project; I got carried away and used that as base for a tool that checks for changes in the DUB registry and generates docs for all projects.
Re: DConf 2015 Second call for proposals
On 2/10/2015 1:50 PM, John Colvin wrote: I didn't see it mentioned anywhere, so I presume there isn't any financial assistance for travel costs for speakers this year. Is that correct? It'll be the same as usual - airplane/car/hotel
Re: DConf 2015 Second call for proposals
On 2/10/15 1:50 PM, John Colvin wrote: I didn't see it mentioned anywhere, so I presume there isn't any financial assistance for travel costs for speakers this year. Is that correct? WHOA! That's a huge miscommunication on our part. Fixed. http://dconf.org/2015/index.html Andrei
Re: Deadcode - Widgets and Styling post
On Tuesday, 10 February 2015 at 06:42:45 UTC, Phil wrote: This looks great. Do you have any idea roughly when an alpha release will be available? Some months I would guess. On Monday, 9 February 2015 at 22:36:45 UTC, David Ellsworth wrote: On Monday, 9 February 2015 at 21:08:18 UTC, Brad Anderson wrote: I've never seen anyone post under the name deadcode on the forums so don't think there is much potential for confusion (especially since one is a project and another is a person). I think you should keep the name. Well, even if I do start posting here more frequently, I think I'll still be okay with this. As you said one is a project and the other is a person! I don't think anybody here will be confused. :)
Re: DDocs.org: auto-generated documentation for all DUB projects (WIP)
On Tuesday, 10 February 2015 at 22:40:18 UTC, Kiith-Sa wrote: DDocs.org (http://ddocs.org) is a repository of documentation for DUB projects that automatically re-generates docs as new projects/releases/branch changes are added. The idea is to make documenting D projects as simple as possible, to the point where you don't need to do any work to get documentation for your project other than adding it to the DUB registry. Also, users can now browse documentation for DUB projects even if the author was too lazy to generate it themselves (assuming thy did include some documentation comments). Note that this is still in a very early stage, it was put together in a very quick-and-dirty style by a person with little webdev experience. Currently it just scans `code.dlang.org`, looking for changes (yes, I know, this will break as soon as code.dlang.org changes, I plan to raise issue/s (PRs?) to the dub registry project so it can have a full/stable API, but I wanted to get something to work *right now*. Code is here: * ddocs.org: https://github.com/kiith-sa/ddocs.org * hmod-dub: https://github.com/kiith-sa/hmod-dub * harbored-mod: https://github.com/kiith-sa/harbored-mod Background: When optimizing harbored-mod by testing it on big D projects (gtk-d, tango, vibe.d, etc.), I wrote a simple tool to fetch/generate docs for any DUB project; I got carried away and used that as base for a tool that checks for changes in the DUB registry and generates docs for all projects. That is pretty cool! I will put a link to it in all my project readmes. I've noticed that License: a$(WEB boost.org/LICENSE_1_0.txt, Boost License 1.0). gets rendered as a. Am I doing it wrong?
Re: DlangIDE
On Friday, 6 February 2015 at 17:56:05 UTC, Jeremy Powers wrote: What is best shortcut for it? Ideally key shortcuts would match existing IDEs, so don't have to relearn. I'm used to these: https://www.jetbrains.com/idea/help/keyboard-shortcuts-and-mouse-reference.html (un/comment is ctrl+/ or cmd+/ on mac, ctrl+shift+/ for block comments) Implemented toggling line comments with ctrl+/ and block comments with ctrl+shift+/ Merged pull request with ability to navigate to source code by clicking on build log lines. As well I've added some coloring to build log. I see strange issue on Ubuntu: Ctrl key is not working in SDL2 - neither KeyDown nor key modifiers state flag. As a result, shortcuts like Ctrl+Z, Ctrl+C, Ctrl+/ do not work. Does someone see the same?
Re: DlangIDE
On Friday, 6 February 2015 at 18:31:19 UTC, extrawurst wrote: Good work! On Friday, 6 February 2015 at 14:03:07 UTC, Vadim Lopatin wrote: * Code completion * Go to definition Please do not create yet another parser/lexer for this, looks like DCD would be a good fit for the job: https://github.com/Hackerpilot/DCD ~Stephan Ok, I will check it. BWT, thank you for pull request with build log parsing and navigation to place of error or warning in code.
