| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This was originally designed to be installed into the system aclocal
directory, but we copy it into each project's m4 directory instead.
This is to try to fix the build for [endlessm/eos-sdk#693].
|
|
|
|
| |
[endlessm/eos-sdk#693]
|
|
|
|
|
|
|
|
| |
Move all the tests for the SDK into tests/endless, move all
the demos into tests/demos, move all the smoke tests into
smoke-tests
[endlessm/eos-sdk#444]
|
| |
|
|
|
|
|
|
|
|
| |
This adds the infrastructure for autogenerating HTML documentation from a
Javascript module using NaturalDocs, and then adds documentation comments
to webhelper.js.
[endlessm/eos-sdk#302]
|
|
|
|
|
|
|
|
| |
The syntax can will hopefully stay the same for apps when this
widget gets rewritten in C. Added support for labels like the
standard button. Moved the overrides rules to a separate .inc
makefile so we can add more standard js libs if we want
[endlessm/eos-sdk#290]
|
|
|
|
|
|
|
|
| |
The autotools code for running the tests should go in the included
Makefile.am in the test/ subdirectory, so that all those test files
are run and distributed in the same place.
[endlessm/eos-sdk#290]
|
|
|
|
|
|
|
|
|
| |
These are tests for the basic functionality and a few fail cases of
webhelper, by no means exhaustive. There are a few tests that cannot
execute because I do not currently know of any way to catch exceptions
that occur inside GObject callbacks.
[endlessm/eos-sdk#290]
|
|
|
|
|
|
|
|
| |
This adds a script eos-run-test which is adapted from gjs_run_tests,
but does not try to discover the tests itself. Instead, in keeping with
Automake's test suite facilities, it takes the filename of a test to run.
[endlessm/eos-sdk#290]
|
|\
| |
| | |
Install WebHelper into GJS modules directory
|
| |
| |
| |
| |
| |
| |
| |
| | |
WebHelper is now importable using
const WebHelper = imports.webhelper;
[endlessm/eos-sdk#289]
|
|/
|
|
|
|
|
|
|
|
| |
This gets rid of a long-standing workaround and makes it easier to
start using a proper test harness for Javascript unit tests.
Unfortunately, it requires a workaround to be able to run gtkdoc-check
on the documentation, but the workaround is not too bad.
[endlessm/eos-sdk#122]
|
|\
| |
| | |
Merge Wikipedia into dev
|
| |
| |
| |
| |
| |
| |
| |
| | |
Now you should be able to import the app generator using
const EndlessWikipedia = imports.wikipedia.EndlessWikipedia;
[endlessm/eos-sdk#206]
[endlessm/eos-sdk#206]
|
|/
|
|
|
|
|
|
|
| |
EOS_PROG_GJS checks for the existence of GJS in the path;
EOS_CHECK_GJS_GIR checks that a GIR can be loaded in GJS, optionally
with a certain version number; and EOS_CHECK_GJS_GIR_API checks for
particular API being available in a GIR in GJS.
[endlessm/eos-sdk#168]
|
|\
| |
| | |
Ensure that Gtk-Doc and GIR doc are enabled for distributions
|
| |
| |
| |
| |
| |
| | |
'make dist' and 'make distcheck' do not work without calling
./configure --enable-gtk-doc --enable-gir-doc.
[endlessm/eos-sdk#86]
|
|/
|
|
| |
Warns about any non introspectable functions in the public API.
|
|
|
|
|
|
| |
Added the autotooling to get our overrides installing as well.
[endlessm/eos-sdk#70]
|
|
|
|
|
|
|
| |
g-ir-doc-tool is buggy, and doesn't build very good documentation,
but it is better than nothing. Building the JS documentation is
turned off by default and turned on for 'make distcheck'.
[endlessm/eos-sdk#18]
|
|
|
|
|
|
|
| |
Without the verbose flag, gtester just says "1 test passed" or "1
test failed", which is not very informative.
[#26]
|
|
|
|
|
|
|
| |
Build system improvement. Otherwise building docs fails on a clean
checkout.
[#26]
|
|
|
|
|
|
|
| |
After running 'make install', run test/smoke-tests/introspection.js
(and its Python counterpart) to test whether the GIR has been installed
correctly.
[#1]
|
|
|
|
|
|
|
|
| |
Run './configure --enable-gtk-doc' to turn on building documentation,
or use --disable-gtk-doc to disable it (for faster builds.) It builds
as part of the regular 'make' invocation, though you can use 'make
docs' to build only the documentation.
[#1]
|
|
|
|
|
|
|
| |
There are automated tests which run when you do 'make check', and also
smoke tests which demonstrate one piece of functionality, which can be
used as a sort of sanity check or demo.
[#1]
|
|
|
|
|
|
| |
Add infrastructure for translating the single string in the shared
library.
[#1]
|
|
Builds a dummy shared library that exports one symbol for testing,
eos_hello_sample_function().
[#1]
|