Re: Documentation for any* dub package, any version

2018-02-26 Thread Martin Tschierschke via Digitalmars-d-announce
On Tuesday, 27 February 2018 at 02:07:34 UTC, Norm wrote: On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for

Re: Documentation for any* dub package, any version

2018-02-26 Thread H. S. Teoh via Digitalmars-d-announce
On Tue, Feb 27, 2018 at 03:07:10AM +, psychoticRabbit via Digitalmars-d-announce wrote: [...] > Uhh? I don't get...why coders need to write documentation? [...] To communicate with other coders who will need to read and maintain the code. And by "other coders", of course, I mean yourself, 2

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 19:30:38 UTC, WebFreak001 wrote: amazing! I planned on adding a documentation tab in the current dub package overhaul, but I wasn't sure on where to get the data from, if I can add this to embed on the dub website (ala iframe) it would make a lot much easier!

Re: Documentation for any* dub package, any version

2018-02-26 Thread psychoticRabbit via Digitalmars-d-announce
On Tuesday, 27 February 2018 at 02:57:08 UTC, Adam D. Ruppe wrote: Saturday morning, a user complained that several leading dub packages had poor documentation, if they could find it at all. That's changing, right now. Before long, packages without docs are going to suffer. This will put

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Tuesday, 27 February 2018 at 01:53:23 UTC, H. S. Teoh wrote: It's a sorry state of affairs. I dream of the day when I can just write code and documentation as-is, and downstream users can just use whatever doc formatting system they like and it will all Just Work(tm). Join me, and

Re: Documentation for any* dub package, any version

2018-02-26 Thread Jonathan M Davis via Digitalmars-d-announce
On Tuesday, February 27, 2018 02:26:49 Adam D. Ruppe via Digitalmars-d- announce wrote: > But even you, who know how to use ddoc very well and have > obviously spent some time on it here, made trivial mistakes here > that just don't happen with adrdox. Any time you do something manually instead

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Tuesday, 27 February 2018 at 02:07:34 UTC, Norm wrote: This is really awesome. It would be really cool if this could feedback a coverage score to code.dlang.org that indicates the level of documentation in a library. Something like the % of functions/classes/modules that are documented and

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Tuesday, 27 February 2018 at 01:43:55 UTC, Jonathan M Davis wrote: Well, then basically, projects are going to need to decide to go with adrdox over ddoc if they want clean documentation. That's right, and I can't imagine anyone is going to put hours of work into ddoc when they can spend

Re: Documentation for any* dub package, any version

2018-02-26 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, February 26, 2018 17:53:23 H. S. Teoh via Digitalmars-d-announce wrote: > On Mon, Feb 26, 2018 at 06:43:55PM -0700, Jonathan M Davis via > Digitalmars-d-announce wrote: [...] > > > Well, then basically, projects are going to need to decide to go with > > adrdox over ddoc if they want

Re: Documentation for any* dub package, any version

2018-02-26 Thread Norm via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. [...] This is really awesome. It

Re: Documentation for any* dub package, any version

2018-02-26 Thread H. S. Teoh via Digitalmars-d-announce
On Mon, Feb 26, 2018 at 06:43:55PM -0700, Jonathan M Davis via Digitalmars-d-announce wrote: [...] > Well, then basically, projects are going to need to decide to go with > adrdox over ddoc if they want clean documentation. They'll probably > get better documentation with adrdox than the default

Re: Documentation for any* dub package, any version

2018-02-26 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, February 26, 2018 19:51:27 Adam D. Ruppe via Digitalmars-d- announce wrote: > On Monday, 26 February 2018 at 15:49:19 UTC, Jonathan M Davis > > wrote: > > Yeah. Any project that uses .ddoc files to define additional > > macros isn't going to work properly > > It is actually more than

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 21:16:07 UTC, Antonio Corbi wrote: Trying it onto gtk-d got an error saying to send you the failing link, so here you are : gtk-d is actually just too big for this, so it timed out. But I also already made gtkd docs on the main site:

Re: Documentation for any* dub package, any version

2018-02-26 Thread Antonio Corbi via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. Hi Adam! Thanks for this superb

Re: An optional/maybe type with range semantics

2018-02-26 Thread Meta via Digitalmars-d-announce
On Monday, 26 February 2018 at 20:04:14 UTC, aliak wrote: Meta: Is this your stuff btw? -> https://github.com/skirino/d-option :) me thinks I may have gotten some inspiration from you if so, so thanks! Nope. I'm MetaLang on Github.

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 20:15:13 UTC, aliak wrote: Awesome. good start at least, and just to throw an approach out there for your consideration, a .adrdox.yml file with a include/exclude/style/etc keys might be a good way to go. Yeah, that's basically what I was thinking (though not

Re: Documentation for any* dub package, any version

2018-02-26 Thread aliak via Digitalmars-d-announce
On Monday, 26 February 2018 at 18:17:51 UTC, Adam D. Ruppe wrote: Oh, fixed now. since there's no ddoc at all in that file, it should have been skipped, I just had a testing "return true;" in the method I forgot to remove. Nice :D Looks good. ketmar sent me a patch to parse a .adrdox_ignore

Re: An optional/maybe type with range semantics

2018-02-26 Thread aliak via Digitalmars-d-announce
On Monday, 26 February 2018 at 16:02:58 UTC, Dukc wrote: I kinda start to see the idea... Granted, nullable is in a way a range that can hold exactly one or exactly zero elements. Not a bad idea at all. Aye, ranges do not need nullability indeed. Optional doesn't need to adhere to the

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 15:49:19 UTC, Jonathan M Davis wrote: Yeah. Any project that uses .ddoc files to define additional macros isn't going to work properly It is actually more than that: I don't support user-defined ddoc macros at all. About 3/4 of the ones I've seen are just link

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 19:47:29 UTC, Jesse Phillips wrote: It also would be good for you to like to the Dub page and Git Repo. Yeah, its on my list. The project homepage from the dub.json too. Couldn't you provide a robots.txt file which Google should honor so that 'nofollow' isn't

Re: Documentation for any* dub package, any version

2018-02-26 Thread Jesse Phillips via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: I'd like to get the code.dlang.org folks to add the correct link to the main package site so people can easily discover this just put nofollow on it plz so google doesn't trigger generation of pages people don't actually

Re: Documentation for any* dub package, any version

2018-02-26 Thread WebFreak001 via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. [...] amazing! I planned on adding

Re: Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
On Monday, 26 February 2018 at 15:21:55 UTC, aliak wrote: Questions: Tried it with optional and undocumented stuff is also shown. Oh, fixed now. since there's no ddoc at all in that file, it should have been skipped, I just had a testing "return true;" in the method I forgot to remove. And

Re: An optional/maybe type with range semantics

2018-02-26 Thread Dukc via Digitalmars-d-announce
On Monday, 26 February 2018 at 15:27:11 UTC, Meta wrote: The idea is to treat `Option!T` as a regular input range so it can be used with all the regular range algorithms without special casing it. You're right in that the null/non-null dichotomy is equivalent to the notion of a range being

Re: Documentation for any* dub package, any version

2018-02-26 Thread Jonathan M Davis via Digitalmars-d-announce
On Monday, February 26, 2018 14:59:07 Adam D. Ruppe via Digitalmars-d- announce wrote: > It isn't 100% compatible with ddoc. For example, this > user-defined macro was not expanded: > http://dxml.dpldocs.info/dxml.dom.html#source Yeah. Any project that uses .ddoc files to define additional macros

Re: An optional/maybe type with range semantics

2018-02-26 Thread Meta via Digitalmars-d-announce
On Monday, 26 February 2018 at 15:21:27 UTC, Dukc wrote: Honestly, I fail to see the idea behind this... Ranges do not need any nullability on top of them IMO, because an empty range can already be used to denote a kind of "default", "unassigned" or "nothing" - type of value. On the other

Re: Documentation for any* dub package, any version

2018-02-26 Thread aliak via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. Simply go to

Re: An optional/maybe type with range semantics

2018-02-26 Thread Dukc via Digitalmars-d-announce
On Sunday, 25 February 2018 at 18:03:35 UTC, aliak wrote: Alo, Just finished up a first take on an optional type for D. It's essentially a mix of Nullable and std.range.only, but with a lot more bells and whistles. I would love to hear any feedback on code, or features, or bad design or

Re: Documentation for any* dub package, any version

2018-02-26 Thread Guillaume Piolat via Digitalmars-d-announce
On Monday, 26 February 2018 at 14:59:07 UTC, Adam D. Ruppe wrote: Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. This is very much awesome, much

Documentation for any* dub package, any version

2018-02-26 Thread Adam D. Ruppe via Digitalmars-d-announce
Many of you will already know this from the other thread or from my twitter, but I just added a on-demand downloader to my dpldocs.info domain to fetch and build docs for any* dub package. Simply go to projectname.dpldocs.info/vX.Y.Z/ and it will generate docs for dub package projectname,