| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
We just added new public API, so inaugurate the 0.5 unstable series.
[endlessm/eos-sdk#3071]
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds EOS_SDK_MAJOR_VERSION, EOS_SDK_MINOR_VERSION and
EOS_SDK_MICRO_VERSION as macros in eosversion.h whose values are
generated from configure with AC_SUBST, rather than in config.h using
AC_DEFINE.
They are also public API, so they get documenation and Since:
annotations.
[endlessm/eos-sdk#3071]
|
|
|
|
|
|
|
|
| |
We cannot switch eos-virtual-school to WebKit2-4.0 because of regressions,
but we already committed to using WebHelper2 to localize it. This adds a
version of WebHelper2 that is compatible with WebKit2-3.0.
[endlessm/eos-sdk#3430]
|
|
|
|
|
|
|
| |
We are about to release EOS 2.4 and we added API in this cycle, so let's
have a new stable series.
[endlessm/eos-sdk#3998]
|
|
|
|
|
|
| |
We now have a gtk supported way to add to an overlay without blocking
input. Let's stop messing with input shapes directly
[endlessm/eos-sdk#3204]
|
|
|
|
|
|
|
|
|
|
|
| |
This allows communicating with the host program through URIs of the
form webhelper://action?param=value¶m2=value2. Actions can be
defined on the WebHelper object and given a callback in Javascript.
Unfortunately we have to use a private C library to register the URI
scheme, because of https://bugs.webkit.org/show_bug.cgi?id=116672
[endlessm/eos-sdk#291]
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new Javascript module, WebHelper2. It's the WebKit2 analogue
to WebHelper. It offers a facility for calling gettext() on the contents
of DOM elements in your web page.
It accomplishes this using an extension module that's loaded into
WebKit's web process.
[endlessm/eos-sdk#291]
|
|
|
|
|
|
| |
Make sure that the necessary GIR packages are installed before building.
[endlessm/eos-sdk#291]
|
|
|
|
|
|
|
|
| |
If we detect a Jenkins environment using the environment variable
JASMINE_JUNIT_REPORTS_DIR that we set in the job's configuration, then
generate XML test reports for each Jasmine unit test.
[endlessm/eos-sdk#3172]
|
|
|
|
|
|
|
|
| |
This requires removing the $(ENDLESS_TESTS_DIRECTORY) variable, which
wasn't really necessary anyway. Subdir-objects would like you to specify
your directories directly in the rule target names.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
| |
This runs the tests during "make check" using jasmine-gjs, and outputs
results in the TAP format that Automake understands.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
| |
This test runner dates from even before eos-jasmine, and is not used
anywhere.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
| |
We've been working on development series 0.1.x, so 0.2.0 is what gets
released with OS release 2.3.0.
[endlessm/eos-sdk#2736]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a rough implementation of an "About"-like dialog for image
attribution in SDK applications. You can press the 'secret' hotkey
Shift+Ctrl+A to get a dialog with thumbnails and attribution information
for the images in the app's GResource. Clicking on the thumbnail opens
the image's original URI in the browser, if known. Clicking on the text
opens the image's license text in the browser, if known.
For this, you need to add a JSON file to the app's GResource and pass its
GResource path to the EosApplication:image-attribution-file property. The
format of this JSON file is described in the documentation for
EosApplication.
The dialog uses GtkTreeView because we didn't have GtkListBox when I
started implementing it over a year ago. This places some limitations on
the UI; the links behave weirdly and the mouse pointer doesn't change to
a hand when hovering over the links.
[endlessm/eos-sdk#2934]
|
|
|
|
|
|
|
| |
This changes the package version to 0.1 and adds versioning macros for
the 0.2 stable series.
[endlessm/eos-sdk#2736]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now provide a new m4 module eos-coverage.m4, which is installed
into the system aclocal directory. This macro provides three
new commands for SDK consumers to use:
EOS_COVERAGE_REPORT([languages]) - Enables a "coverage report".
The first argument is a space separated list of unquoted
languages to collect coverage information for. Valid values
at the moment are "c" and "js". For each language specified,
the macro will check for support for collecting coverage and
enable reporting accordingly. Raw coverage output goes in
$(abs_top_builddir)/_coverage/output/$language accordingly.
The macro then checks to see if a coverage reporter, either
genhtml, or cobertura, is available and enables them. A reporter
must be installed and available for coverage reports to be
generated.
The coverage-genhtml is enabled if lcov is installed and available.
This is generally used by developers themselves as it creates a
self-contained report.
The coverage-covertura is enabled if a program called
lcov-result-merger is installed and a python module called
lcov_cobertura are installed. lcov-result-merger can be
installed from Node Package Manager. lcov_cobertura
can be installed from PyPI.
lcov-result-merger is necessary because each test suite is run
in a separate subprocess and so there will be multiple entries
per source file in the coverage.lcov file generated by gjs.
lcov_cobertura doesn't handle that properly and so the
results need to be merged together properly.
JavaScript Coverage Details
===========================
A variable called EOS_JS_COVERAGE_FILES should be defined
containing a list of all javascript files to be considered
a "part of" the coverage report, before EOS_COVERAGE_RULES
are substituted. For example:
EOS_JS_COVERAGE_FILES = $(SRCS)
@EOS_COVERAGE_RULES@
AM_JS_LOG_FLAGS += @EOS_COVERAGE_JS_LOG_FLAGS@
C/C++ Coverage Details
======================
Certain additions also need to be made for Makefiles where
coverage reporting is enabled on a C project:
@EOS_COVERAGE_RULES@
AM_CFLAGS += @EOS_C_COVERAGE_CFLAGS@
AM_LDFLAGS += @EOS_C_COVERAGE_LDFLAGS@
If a target's CFLAGS is overridden and AM_CFLAGS is not used,
then @EOS_C_COVERAGE_CFLAGS@ must be added to its CFLAGS.
Blacklisting patterns
=====================
If a path should not appear in the coverage report, then it can
be blacklisted by adding a glob expression to
EOS_COVERAGE_BLACKLIST_PATTERNS.
Clean rules
===========
A clean-coverage target is added to the dependencies for
the clean-local target automatically by EOS_COVERAGE_RULES.
[endlessm/eos-shell#2264]
|
|
|
|
|
|
| |
Instead of our hand rolled check.
[endlessm/eos-sdk#2455]
|
|
|
|
| |
[endlessm/eos-sdk#693]
|
|
|
|
|
|
|
|
|
|
|
|
| |
The utility used in eos-english and eos-programming-app was integrated and installed as part of the SDK
CR comments addressed include:
- Integrated new facilities available on GTK
- Removed duplicate prototype declaration
- Reformatted CLEANFILES var declaration
- Used configure.ac to get @PACKAGE_VERSION@
- Added version() and usage() utilities
[endlessm/eos-sdk#335]
|
|\
| |
| | |
#417 Removed PStack from sdk
|
| |
| |
| |
| |
| |
| |
| | |
We used this for our page manager, now we can just use GtkStack
with Gtk 3.10
[endlessm/eos-sdk#417]
|
|/
|
|
|
|
|
| |
This removes all conditionally compiled parts for GTK < 3.10 and
GLib < 2.38.
[endlessm/eos-sdk#420]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of a hacky blah: blah.in cp $< $@ rule.
Also, a stamp file turns out to be necessary for building documentation if
it is included in the distribution; if an up-to-date copy of the
documentation is unpacked into the source tree during make distcheck,
then it does not get remade in the build directory because it is
up-to-date. That causes make distcheck to fail later on, because it can't
copy the documentation from the build tree into the dist tree.
[endlessm/eos-sdk#340]
|
|
|
|
|
| |
This is necessary because Jenkins' temp directory names will cause
file paths longer than 99 characters.
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
| |
Now you should be able to import the app generator using
const EndlessWikipedia = imports.wikipedia.EndlessWikipedia;
[endlessm/eos-sdk#206]
[endlessm/eos-sdk#206]
|
|
|
|
|
|
|
|
| |
resource:///com/endlessm/sdk/ is now the official GResource path for SDK
resources. Right now the GResource contains reset.css (from GTK) and
endless-widgets.css (from eos-theme).
[endlessm/eos-sdk#125]
|
|
|
|
|
|
| |
The problem was with needing the serial-tests option in 1.13
More details here
http://gnu-automake.7480.n7.nabble.com/serial-tests-option-and-backwards-compatibility-td19571.html
|
| |
|
|
|
|
|
|
| |
Our tests break on the new-style parallel test runner, which is the
default in newer versions of Automake.
[endlessm/eos-sdk#121]
|
|\
| |
| | |
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]
|
|/
|
|
|
|
| |
Replacement is at https://github.com/ptomato/pstack
(Matt & Philip)
[endlessm/eos-sdk#69]
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
|
|
|
| |
So we can compile with C99 enabled; this requires checking that the
version of the compiler supports the -std=c99 command line switch, which
holds true for both GCC and CLang.
The warnings/errors we enable through the --enable-strict-flags
configure switch need to be amended so that we don't catch C99 valid
constructs like declaration after statement and VLAs.
[endlessm/eos-sdk#49]
|
|
|
|
|
|
|
|
| |
The AC_CACHE_SAVE macro saves the state of the configure script, so that
it can be restore from a known state without having to re-run all the
checks. This should speed up the build.
[endlessm/eos-sdk#52]
|
|\
| |
| | |
Application class
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an EosApplication class. Functionality:
- present main application window when activated
- warn if more than one application window is added
Also add a stub EosWindow class that overrides GtkWindow's
"application" property to be a construct-only property.
[#4]
|
|/
|
|
|
|
|
| |
Use AM_PROG_AR, AM_PROG_CC_C_O, and -Wno-portability to avoid
warnings on Automake 1.12
[#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]
|
|
|
|
|
|
| |
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]
|