| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
Nothing is using this. (The last users were eos-programming, stuck on an
old runtime; and eos-typing, defunct.)
As long as I'm removing SearchBox, may as well remove this too.
https://phabricator.endlessm.com/T20353
|
|
|
|
|
|
|
|
|
| |
This was used nowhere except in eos-knowledge-lib. We are going to make
many eos-knowledge-lib specific changes to it, so it's going to be
forked into there. After nothing uses it, it doesn't make sense to keep
it here given that we intend to slowly move away from using eos-sdk.
https://phabricator.endlessm.com/T20353
|
|
|
|
|
|
| |
Unbreaks distcheck — and Jenkins.
https://phabricator.endlessm.com/T15612
|
|
|
|
|
|
|
|
|
| |
As agreed with the design team, all apps should include a generic
home button at the top left corner of the app window. Therefore, we
add a new generic button in the sdk to be used in all the different
apps for consistency.
[endlessm/eos-sdk#4030]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
This reverts commit 5b2cc64e43d16d0ac54fd2def0c5a821bb7391ea.
|
|
|
|
|
|
|
| |
This class could potentially be used by other pseudo-WebApps
in our system, so it makes sense to stick it in the SDK.
Provides functionality for cleanly injecting custom CSS and
JS into a webview.
|
|
|
|
|
|
|
|
|
|
| |
TopBarNavButton can be used for browser-style back and forward
buttons in the title bar of a window.
TopBarNavButton currently uses CSS and rounded corners. 5-sided
button will be added later when assets are available.
[endlessm/eos-sdk#1294]
|
|
|
|
|
|
|
|
|
| |
We reuse this same search box functionality in a
number of our apps so makes sense to stick it in the SDK.
Creates a search box that has autocompletion and provides
signals for when a search is triggered and when an
autocompletion entry is selected. Has its own default
styling which can be overridden.
|
|
|
|
|
|
|
|
| |
The Endless api now includes 2 methods for connection testing, one synchronous, and one
asynchronous. Both of these methods work by work ensuring that there is a network available,
and pinging the specified host if so.
[endlessm/eos-sdk#1383]
|
|
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]
|