I use this experimental sample website regularly for Phobos
documentation because it's organized much better than what is on
the official website.
Example:
http://vibed.org/temp/d-programming-language.org/phobos/std/array.html
Of course it's better to have the official website directly host
an improved format, but I don't know if that's a huge undertaking
or not, so in the meantime
I'd rather not wait for something like it to materialize in here
because I have real work to do and it's a productivity booster,
so is it possible to have the vibe.d website updated to the
latest documentation? It'll be appreciated greatly if this can be
done, thanks!
--rt

I use this experimental sample website regularly for Phobos
documentation because it's organized much better than what is on the
official website.
Example:
http://vibed.org/temp/d-programming-language.org/phobos/std/array.html
Of course it's better to have the official website directly host an
improved format, but I don't know if that's a huge undertaking or not,
so in the meantime
I'd rather not wait for something like it to materialize in here because
I have real work to do and it's a productivity booster, so is it
possible to have the vibe.d website updated to the latest documentation?
It'll be appreciated greatly if this can be done, thanks!

I use this experimental sample website regularly for Phobos
documentation because it's organized much better than what is
on the
official website.
Example:
http://vibed.org/temp/d-programming-language.org/phobos/std/array.html
Of course it's better to have the official website directly
host an
improved format, but I don't know if that's a huge undertaking
or not,
so in the meantime
I'd rather not wait for something like it to materialize in
here because
I have real work to do and it's a productivity booster, so is
it
possible to have the vibe.d website updated to the latest
documentation?
It'll be appreciated greatly if this can be done, thanks!

Hmm. While I really like the layout, because it is so much more readable
then the dlang.org version, I wonder how I get information about members
of a class, e.g. for RedBlackTree:
http://vibed.org/temp/d-programming-language.org/phobos/std/container/RedBlackTree.html
I only get the creator functions. Funnily the link in functions to
redBlackTree leads to a 'page not found'. It also seems that DList has
no members?
Best regards,
Robert

Hmm. While I really like the layout, because it is so much more readable
then the dlang.org version, I wonder how I get information about members
of a class, e.g. for RedBlackTree:
http://vibed.org/temp/d-programming-language.org/phobos/std/container/RedBlackTree.html
I only get the creator functions. Funnily the link in functions to
redBlackTree leads to a 'page not found'. It also seems that DList has
no members?
Best regards,
Robert

Oh sorry, the problem is that I generated the docs on Windows and the
two files differ just by the case of the first character - so one was
overwritten by the other. I'll regenerate them on Linux when I have some
time.

Hmm. While I really like the layout, because it is so much more readable
then the dlang.org version, I wonder how I get information about members
of a class, e.g. for RedBlackTree:
http://vibed.org/temp/d-programming-language.org/phobos/std/container/RedBlackTree.html
I only get the creator functions. Funnily the link in functions to
redBlackTree leads to a 'page not found'. It also seems that DList has
no members?
Best regards,
Robert

Oh sorry, the problem is that I generated the docs on Windows and the
two files differ just by the case of the first character - so one was
overwritten by the other. I'll regenerate them on Linux when I have some
time.

Oh sorry, the problem is that I generated the docs on Windows and the=

two files differ just by the case of the first character - so one was=

overwritten by the other. I'll regenerate them on Linux when I have s=

ome

time.

Done.

Still doesn't look right. RedBlackTree is listed as a template, but no =
=
methods or fields are listed.
BTW, I really like this format. I think once these issues are ironed ou=
t, =
it should be moved to Phobos docs.
-Steve

Oh sorry, the problem is that I generated the docs on Windows and the
two files differ just by the case of the first character - so one was
overwritten by the other. I'll regenerate them on Linux when I have some
time.

Done.

Still doesn't look right. RedBlackTree is listed as a template, but no
methods or fields are listed.
BTW, I really like this format. I think once these issues are ironed
out, it should be moved to Phobos docs.
-Steve

Fixed.
I think it would be a good idea to put the new documentation into a kind
of half-official place next to the classical docs until they are deemed
error-free. That way the exposure would be higher, so that the remaining
bugs can be found faster.

methods or fields are listed.
BTW, I really like this format. I think once these issues are ironed=

out, it should be moved to Phobos docs.
-Steve

Fixed.

Beautiful!
Now, I need to examine how you do this, 'cause I want to do it for my =
project :)

I think it would be a good idea to put the new documentation into a ki=

nd

of half-official place next to the classical docs until they are deeme=

d

error-free. That way the exposure would be higher, so that the remaini=

ng

bugs can be found faster.

Yes, I would prefer that.
One further thing I would like to see, even if it's optional, is to see =
=
types and functions in the tree on the left.
I love that inherited members are documented! This is exactly what I ha=
ve =
been looking for for YEARS, and it looks so good/official!
One thing that will need to be addressed/considered before this is =
accepted as the standard docs is any use of 3rd party tools to generate =
=
the docs. I noticed you said you use libevent. Some purists may not li=
ke =
that...
-Steve

Oh sorry, the problem is that I generated the docs on Windows and the
two files differ just by the case of the first character - so one was
overwritten by the other. I'll regenerate them on Linux when I have some
time.

Actually, theoretically, there is a flag for CreateFile that
makes it use POSIX semantics and allow two names which only
differ in case.
--=20
Marco

Oh sorry, the problem is that I generated the docs on Windows and the
two files differ just by the case of the first character - so one was
overwritten by the other. I'll regenerate them on Linux when I have some
time.

Actually, theoretically, there is a flag for CreateFile that
makes it use POSIX semantics and allow two names which only
differ in case.

Interesting. I've never noticed that flag before. Unfortunately that
would only work in the win32 back end (as opposed to the default
libevent back end), but maybe that's actually still a viable option,
I'll look into it.