| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
These will eventually be paired with the sections file parser to create
a set of sections.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'ok' != 'return_value', and we never restore 'Returns:'.
At the same time, do the same fix for (out) parameters if the
return value is void, so this
void my_object_get_foo (MyObject *object, Foo *)
is turned into
function get_foo() : Foo
Returns: ....
|
| |
|
|
|
|
|
|
|
|
|
|
| |
GClosures are represented in gjs as JS functions for in
parameters, so it makes sense to use Function in place of
the boxed structure (which is also not part of the documentation)
Note that GClosures returned from C code are marshalled
as boxed types, but this is a gjs bug really, and JS code
should never touch them.
|
|
|
|
| |
They are enums after all.
|
|
|
|
|
|
| |
GValues are transparently marshalled by GJS, so you can
never use them as boxed (and they are not part of the
documentation as such).
|
|
|
|
|
|
|
|
|
|
|
| |
If a xref points to a node that was not visited, because it
was not introspectable, don't assume it has no parent. Instead,
try to fetch the parent from the node directly.
This is still wrong (the xref points nowhere because no page is
generated), but it looks less wrong.
If OTOH a xref points to a different namespace, generate the
link directly, because yelp-build is not capable of translating
it.
|
|
|
|
|
|
| |
As the comment says, it's an AST bug, the structure there cannot
be reasonably represented in gobject-introspection, and it makes
the tests for C and Python crash, so whatever.
|
|
|
|
|
|
| |
Unless they have no methods, static methods and constructors
(because then they are useless)
Fixes GLib.BookmarkFile, GLib.PatternSpec and probably others.
|
|
|
|
|
|
|
|
|
|
| |
We should only look at introspectable constructors when resolving
the default and zero args. Also, a disguised structure or one
with zero fields can't be allocated directly.
In addition, restore availability of all constructors, because
we need a page to document the default one, and because some classes
have problems with GObject construction.
|
|
|
|
|
|
| |
Support for fundamental types was just merged in gjs, so just
filter out GParamSpec subclasses (because there is only one
class in gjs)
|
|
|
|
|
| |
If a function is shadowed, omit it from the documentation, and
if a function shadows, uses the new name.
|
|
|
|
|
| |
The ByteArray class is special in gjs, it's not a normal Array,
so make sure it's flagged as such.
|
|
|
|
| |
g-ir-compiler ignores them too, and they cause a crash, so whatever.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stop pretending we have fields on unions (only methods are
supported).
Add minimal support (ie, don't crash) to nested structures,
that due to how ast works have namespace None (and the
transformers hard-depend on that). Uncovered by GLib's
GDoubleIEEE754, before I removed union fields.
For some reason, RegressTestStructE (anonymous union) has a
completely different behavior and generates a weird name,
while RegressLikeGnomeKeyringSchema (array of unnamed structs)
becomes array(gpointer).
Bah, one should have methods anyway...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add documentation for structures, fields, constants and
callbacks
- Improve the synopsis for interfaces to have prerequisites
and known implementations
- Respect gjs constraints for field writability
- Format in and out parameters for callables according to GJS
conventions
- Format property names according to the GJS API
- Show boxed constructors according to how they can be used
in the gjs API
https://bugzilla.gnome.org/show_bug.cgi?id=724735
|
|
|
|
|
| |
This prevents fields like __gtk_reserved1 from being emitted in the
documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version in our tree is a wee bit outdated. For example,
later work will introduce an utf8 encoded python source
file which our old pep8.py does not yet understand (yeah,
it really was *that* ancient)...
Updated from:
https://raw.github.com/jcrocholl/pep8/1.4.5/pep8.py
Takes 552c1f1525e37a30376790151c1ba437776682c5,
f941537d1c0a40f0906490ed160db6c79af572d3,
5a4afe2a77d0ff7d9fea13dd93c3304a6ca993de and
a17f157e19bd6792c00321c8020dca5e5a281f45 into account...
https://bugzilla.gnome.org/show_bug.cgi?id=699535
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=697615
|
|
|
|
|
|
| |
Rather than hand-rolling our own. This ensures we traverse all nodes.
https://bugzilla.gnome.org/show_bug.cgi?id=694593
|
| |
|
| |
|
|
|
|
| |
Make it use a simple recursive technique similar to format_page_name.
|
|
|
|
|
|
|
|
|
| |
The eventual model I want to have is that .parent is the "container"
of the node. In all the cases where we don't explicitly set the parent,
this is the namespace, but having this under one field name would be
a big cleanup for the docwriter.
https://bugzilla.gnome.org/show_bug.cgi?id=693876
|
| |
|
| |
|
|
|
|
|
|
| |
Clutter has thousands of keysym constants, and until we get them
all on one page, this is just tons of tiny files that are just
noise.
|
| |
|
|
|
|
|
|
| |
Introspectable languages share a non-zero set of base semantics,
so it will become easier to implement these shared semantics here,
rather than copy-paste code.
|
|
|
|
| |
Language bindings don't actually care
|
|
|
|
| |
This can happen for properties/signals.
|
| |
|
|
|
|
| |
Gjs ignores all of these when constructing function signatures.
|
|
|
|
|
|
|
|
| |
This will let us gracefully skip over parameters that aren't exposed
by specific language bindings.
It also fixes a bug in the C/Python documentation where we weren't
iterating over the right parameters.
|
|
We eventually want to stop using Mallard as a documentation language.
Rationale incoming when I convert all templates back to DocBook.
|