| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
popd and pushed are not implemented in all shells
https://rgeissert.blogspot.com/2013/02/a-bashism-week-pushing-and-poping.html
|
|
|
|
|
| |
Docs about FTS are somewhat thin and scattered. Add a doc
blurb about FTS explaining how things are put together.
|
|
|
|
|
|
|
|
|
|
|
| |
Duplicate/adapt the script existing at docs/website/build.py
in order to build HTML/markdown output for our command line
tools.
Since we use the xmlto CLI tool and asciibook->docbook->html
conversions to get style-free HTML documents, and it was not
previously a build dependency, make this an optional runtime
dependency while we cannot bump dependencies.
|
|
|
|
|
|
| |
Explain more in depth the relation between dataobject/informationelement,
taking inspiration from the original Nepomuk documentation in wording
and illustrations.
|
|
|
|
|
|
| |
Instead of including them as images, inline and theme them like
we do with other SVGs, this makes them look better on dark themes,
other than being a non-descript grey.
|
|
|
|
|
|
|
|
|
| |
Since we have files in the sources dir and generated files
in the build dir, we may want to generate documentation that
inline files from both locations.
Allow adding an additional lookup path for the file, so both
can be tried.
|
|
|
|
|
|
| |
Our helper script to substitute and inline doc sections and
images may choke if multiple {{ }} blocks are found in the
same line. Make it handle this situation in the regexp used.
|
| |
|
|
|
|
| |
It was left unpushed in my tree, and silently not included.
|
|
|
|
|
|
| |
Make the background of some images transparent, and add some
CSS to ensure nodes, edges and arrows get proper colors on both
light and dark themes.
|
|
|
|
|
| |
Explain somewhat better what tracker is, does, and what possible
advantages there could be in using it.
|
|
|
|
|
|
|
|
|
|
| |
The flatpak CLI parsing for additional policies changes at some point
so that it is not possible to specify multiple values in a single call.
Doing that results in the ';' being escaped, and the full string to be
interpreted as a single value.
In order to add multiple values, --add-policy can be called multiple
times, recommend that in our manpage for the task.
|
|
|
|
| |
Explain this a bit better, add some diagrams, etc.
|
|\
| |
| |
| |
| | |
website: Update IRC details
See merge request https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/578
|
| | |
|
| |
| |
| |
| |
| |
| | |
The version is already expressed in gi-docgen output, plus it's now
appended in the completely wrong place... making the website output
look ugly.
|
| |
| |
| |
| |
| |
| | |
This is bitrotting already, and we will not want to go back
to that. Presumably noone else would, so we can simply drop
this.
|
| |
| |
| |
| |
| |
| | |
Same rationale than devhelp, we want to add ontology-related
search terms there. Generate the JSON files separately, in order
to merge them at the same last stage.
|
| |
| |
| |
| |
| |
| | |
Use embedded SVG for the few diagrams we have at the tutorial,
like everywhere else in docs now. This should also work with
dark modes and whatnot.
|
| |
| |
| |
| |
| | |
In order to move to embedded SVGs for images, we have to be able
to embed them first.
|
| |
| |
| |
| | |
In the annotations about nrl:notify properties.
|
| |
| |
| |
| |
| | |
Add some separation between columns, and a hover effect on rows,
to increase legibility.
|
| |
| |
| |
| | |
Otherwise, they show in multiple lines.
|
| |
| |
| |
| |
| |
| | |
Highlight how do the various ontology classes relate to other classes.
Just like with the class diagrams, make things links so the documentation
can be navigated.
|
| |
| |
| |
| |
| | |
More in line with gi-docgen, generate SVGs for our class hierarchies,
and embed them in the docs.
|
| |
| |
| |
| |
| |
| | |
It is not much useful to e.g. list every defined resource in
the rdfs:Resource documentation. Avoid these kinda obvious
pre-defined instances.
|
| |
| |
| |
| |
| | |
Avoid too much nesting of sections, so the navigation sidebar is able
to show the classes and additional properties.
|
| |
| |
| |
| |
| | |
This document has some embedded code examples, these should be
embedded into the final markdown document.
|
| |
| |
| |
| |
| | |
Rescue this nasty little hack from commit c5414ed4da15, and make it
go through the generated documentation files at the moment.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update it to the gi-docgen syntax, fix links, flesh out
docs some more, and make documents generally make a better
use of the navigation sidebar.
The several subsections describing ontologies have been
merge into a single document.
|
| |
| |
| |
| | |
Fix the images for our small property annotations.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Move away from hotdoc, and port the documentation infrastructure
to use gi-docgen. We still do fixup devhelp2 files in order to
include ontology items as search terms, and we still do prefer
to ship the pre-generated documentation in the tarball, in order
to avoid a host of dependencies like graphviz for the people
building from tarballs.
It is not the first time that porting to gi-docgen was attempted,
this is partially based on work by Daniele Nicolodi <daniele@grinta.net>.
|
|
|
|
|
|
|
|
| |
These rules pretty much define the triples that can be extrapolated
from a simpler data set. We have some strong reliance on RDFS
entailment, so document to what extent.
Closes: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/255
|
|
|
|
|
| |
And kinda deprecate the --show-graphs option that did output TriG.
We now are able to output TTL, TriG, and JSON-LD.
|
|
|
|
|
|
| |
None of the situations here look like potential bugs, just cases where
the compiler can't verify that the variable will be initialized before
it's used.
|
|
|
|
|
|
|
|
|
| |
Separate ontology parsing so that we can provide separate locations for
.ontology and .description files, so that we can avoid doubly parsing the
base ontology just for the sake of parsing the description files.
This avoids redefinition warnings by the ontology docgen tool while
generating the docs for the base ontology.
|
|
|
|
| |
Fixes a compiler warning.
|
|
|
|
|
|
| |
Drop all the places left where we do specify things for Vala,
and rename the targets that had that name because of vala code
presence.
|
|
|
|
|
|
|
|
|
| |
Remove the direct soup dependency by using TrackerHttpClient, that deals
with soup itself. This also means the remote connection objects can move
to the main library code, instead of being built as standalone modules.
In consequence, the older remote modules are no longer built, and their
loading infrastructure removed.
|
| |
|
|
|
|
|
|
|
| |
Paraphrase and complete some of the security considerations brought
up at the various SPARQL reference documents.
Fixes: https://gitlab.gnome.org/GNOME/tracker/-/issues/349
|
| |
|
| |
|
|
|
|
| |
This is missing in introspection annotations.
|
|
|
|
|
| |
This is something hotdoc can do for us, there is no need for an
script here.
|
|
|
|
|
| |
Rationalize why we only support the last stable, and everything
else is deemed to crash and burn.
|
|
|
|
|
|
| |
Besides current status, that tells about missing files and whatnot,
seems a good idea to advise that before telling to follow/restart/debug
daemons.
|
|
|
|
|
|
|
| |
We should use asciidoc's `a2x` driver instead of running xsltproc
ourselves. asciidoc 10 ships its stylesheets in a private directory.
Fixes: https://gitlab.gnome.org/GNOME/tracker/-/issues/347
|
|
|
|
|
|
|
| |
SELECTs may have 2000 columns, which we effectively halve with SPARQL
queries doubling the number of columns. Still, 1000 is an acceptable
default limit, and the change is unlikely to have side effects, so
document this new behavior.
|