September 06
On Tuesday, 5 September 2017 at 15:46:27 UTC, Laeeth Isharc wrote:
> If you want a larger VM email me specs and I will set one up for you.

My doc generator can eat over 4 gigabytes... but for just minutes at a time, before going back to 16 megabytes to host plainly.... or 2 GB again to host with full server-side search.

But I should be able to work with a fraction of that for the typical dub library... I'm just not sure what yet. And I might be able to optimize that a lot (I just run it at home for my own use with a whopping 16 GB, so I'm in no rush... I just don't want to run arbitrary crap from home off dub)


> I guess the doc generation doesn't need much changing on dub.  Maybe an extra command line option to build and publish docs

If it has to be configured, it isn't going to be used. I want it automatic.
September 06
On Monday, 4 September 2017 at 10:47:47 UTC, Manu wrote:
> I've seen a lot of dub projects with embedded ddoc that follows phobos
> example.
> These projects are then hosted on code.dlang.org, but often, the docs are
> never generated and hosted anywhere.
> In the event they are, links to docs are ad-hoc and unpredictable, and the
> formatting/styling/etc is not standard/consistent.
>
> Suggest; code.dlang.org should attempt to generate ddoc for each hosted project, host it, and clearly link to it from the project front-page. Hosted docs should be styled consistently (matching phobos?).

Having automatically updated docs hosted on code.dlang.org will motivate package developers to write better ddoc comments for their code.

It will get library packages more usable, and attract more users.


September 06
On Wednesday, 6 September 2017 at 14:04:56 UTC, Vadim Lopatin wrote:
> Having automatically updated docs hosted on code.dlang.org will motivate package developers to write better ddoc comments for their code.

I would go so far as to automatically downvote things with poor docs...
September 09
On 7 September 2017 at 00:17, Adam D. Ruppe via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> On Wednesday, 6 September 2017 at 14:04:56 UTC, Vadim Lopatin wrote:
>
>> Having automatically updated docs hosted on code.dlang.org will motivate package developers to write better ddoc comments for their code.
>>
>
> I would go so far as to automatically downvote things with poor docs...
>

+1


September 11
On 9/5/17 5:46 PM, Andrei Alexandrescu wrote:
> On 09/05/2017 12:05 PM, Seb wrote:
>> On Tuesday, 5 September 2017 at 07:59:09 UTC, denizzzka wrote:
>>> On Monday, 4 September 2017 at 10:47:47 UTC, Manu wrote:
>>>> Suggest; code.dlang.org should attempt to generate ddoc for each hosted project, host it, and clearly link to it from the project front-page. Hosted docs should be styled consistently (matching phobos?).
>>>>
>>>> Thoughts?
>>>> - Manu
>>>
>>> It would be nice if the DUB will be able to generate "docsets" for offline documentation browsers:
>>>
>>> https://kapeli.com/dash (can be integrated into various IDEs!)
>>> https://zealdocs.org/
>>> http://devdocs.io/
>>
>> This has been merged this week:
>> http://devdocs.io/d/
> 
> Nice! Who did the work? -- Andrei
> 

https://github.com/Thibaut/devdocs/pull/661

Looks great!

-Steve
6 days ago
On Monday, 4 September 2017 at 11:15:08 UTC, Joakim wrote:
> While it's an interesting suggestion, dub has 355 open issues, would be better if more people pitched in on those:
>
> https://github.com/dlang/dub/issues

It looks like the current policy is to leave issues open unless they're exact duplicates or have a pull request that mentions fixing them. (Not quite so dour, but it's not great.) That artificially inflates the count with stuff like:

* There's already a way to do that, but it doesn't match what you want
* We don't have anything that matches, but we're not going to add it without a large swell of requests
* Reported crash / error / etc from four years ago that was probably fixed three years ago
* Issue was fixed but the pull request didn't reference the issue

I'm quite willing to do bug triage, but I don't have the authority.
6 days ago
On Tuesday, 12 September 2017 at 18:42:35 UTC, dhasenan wrote:
> On Monday, 4 September 2017 at 11:15:08 UTC, Joakim wrote:
> I'm quite willing to do bug triage, but I don't have the authority.

That's great!
Simply start going through the issues and comment when you think it should be closed. This will do fine for the beginning and most likely we can even give you the needed permissions ;-)
6 days ago
On Tuesday, 12 September 2017 at 18:42:35 UTC, dhasenan wrote:
> On Monday, 4 September 2017 at 11:15:08 UTC, Joakim wrote:
>> While it's an interesting suggestion, dub has 355 open issues, would be better if more people pitched in on those:
>>
>> https://github.com/dlang/dub/issues
>
> It looks like the current policy is to leave issues open unless they're exact duplicates or have a pull request that mentions fixing them. (Not quite so dour, but it's not great.) That artificially inflates the count with stuff like:
>
> * There's already a way to do that, but it doesn't match what you want
> * We don't have anything that matches, but we're not going to add it without a large swell of requests
> * Reported crash / error / etc from four years ago that was probably fixed three years ago
> * Issue was fixed but the pull request didn't reference the issue
>
> I'm quite willing to do bug triage, but I don't have the authority.

Yeah, Sonke is very liberal about leaving issues open and a tool like this has a lot of features people want, so it isn't as bad as it looks.  I went through many of the issues and got Seb to close 5-6 of them, and then was made a member of the dlang/dub team.  Just comment with one of our nicks on any issue and we'll do what's needed.
Next ›   Last »
1 2 3