The most API of Apache Arrow Ruby are generated
>> automatically by GObject Introspection support. We can reuse
>> GTK-Doc style documentation in Apache Arrow C for Apache
>> Arrow Ruby.
>>
>> We may be able to use
>> https://github.com/ruby-gnome2/yard-gobject-intros
We can reuse
> GTK-Doc style documentation in Apache Arrow C for Apache
> Arrow Ruby.
>
> We may be able to use
> https://github.com/ruby-gnome2/yard-gobject-introspection
> for Apache Arrow Ruby. It's not completed yet but we can
> improve it. (I'm one of the develope
in Apache Arrow C for Apache
Arrow Ruby.
We may be able to use
https://github.com/ruby-gnome2/yard-gobject-introspection
for Apache Arrow Ruby. It's not completed yet but we can
improve it. (I'm one of the developers of it.)
Thanks,
--
kou
In <1526586273.3156930.1375962952.57744..
+1 on setting up a top-level documentation project. I think that
establishing an information hierarchy to help people understand all
the layers of the project is more important than the choice of the
documentation tool -- for example, if we started with Sphinx and
decided to move later to something
Hello,
I can second that we should move the documentation to a central one. As a C++
and Python contributor at the same time it always hard to think of where you
should document a specific piece. We have a very small C++ documentation and a
bit larger Python one. For some features it would thou
Hi,
In the following PR discussion it was mentioned that we currently lack a
central documentation system for cross-language topics:
https://github.com/apache/arrow/pull/1575#issuecomment-364062240
Sphinx looks like a reasonable contender for that purpose. For that who
don't know it, Sphinx is
