| Commit message (Collapse) | Author | Age |
|
|
|
| |
[endlessm/eos-sdk#693]
|
|
|
|
|
| |
Wasn't getting used in any apps so we are taking it out
[endlessm/eos-sdk#985]
|
|
|
|
|
| |
Wasn't getting used in any apps so we are taking it out
[endlessm/eos-sdk#985]
|
|
|
|
|
| |
Was not getting used in any apps so we are taking it out
[endlessm/eos-sdk#985]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the visible-child and visible-child-name properties of GtkStack
in lieu of visible-page and visible-page-name. Use the
transition-duration, transition-type and name properties of GtkStack
instead of proxying in page manager with properties of that same name.
The page manger becomes nothing more than a stack with custom child
properties for use in EosWindow, and becomes a lot simpler.
This breaks the page manager api and will require changes in the
apps as well
[endlessm/eos-sdk#985]
|
|
|
|
|
|
|
|
|
|
| |
This has been totally unused in all our applications and has been
having sizing problem with height for width and width for height
request.
We had grand plans for this, but since its unclear if there's a
future in which this widget is used think it makes sense to remove
[endlessm/eos-sdk#985]
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users should not have be forced to call show all on the toplevel.
Calling show on all the widgets they create should be enough to
make things show on screen. Which means we need to call show on our
internals ourselves.
Added a test for this. Calls show on the window so will actually
make something pop on screen for a second. But so do other test we
have so I think thats OK
[endlessm/eos-sdk#535]
|
|
|
|
|
|
| |
Added a publicly available calculated font size property. This allows Endless applications to perform actions based on the calculated font size of an EosWindow. In particular, the WebHelper application now uses the property to update the 'default-font-size' property of a WebSettings object.
[endlessm/eos-sdk#484]
|
|
|
|
|
|
|
|
| |
Just to make sure nothing blows up when you try subclassing in
javascript. Fixed up some spacing problems in our test Makefile
and tweaked it to allow for js tests of the sdk C code.
[endlessm/eos-sdk#481]
|
|
|
|
|
|
|
|
|
|
| |
forall cannot be overridden in gjs. There's an upstream bug here
https://bugzilla.gnome.org/show_bug.cgi?id=701567
but that does not look like it will be fixed soon. So for now
added a small c class that take care of GtkContainers add, remove
and forall methods. This makes it possible to write generic containers
in gjs. See docs for an example
[endlessm/eos-sdk#481]
|
|
|
|
|
|
|
|
| |
Also update submodules on autogen.sh
[endlessm/eos-sdk#509]
[endlessm/eos-sdk#509]
|
|
|
|
| |
[endlessm/eos-sdk#444]
|
| |
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
| |
Added configurable properties to EosWindow to allow turning on/off scaling, setting a custom base font, and setting a custom base resolution. EosWindow now has a base font-size that allows children widgets to scale font-size via using em. Also added font rescaling tests to both the automated test and smoke test.
[endlessm/eos-sdk#398]
|
|\
| |
| | |
#191 EosWindow's maximum size is the screen size
|
| |
| |
| |
| |
| |
| | |
test/smoke-tests/large-content.js shows the warnings in action
[endlessm/eos-sdk#191]
|
| |
| |
| |
| |
| |
| | |
All unit test files must import things relative to $(top_srcdir).
[endlessm/eos-sdk#154]
|
|/
|
|
|
|
|
|
|
| |
This implements the 'init' subcommand of the application manifest tool,
which creates a new manifest in the current directory.
[endlessm/eos-sdk#154]
[endlessm/eos-sdk#154]
|
|
|
|
|
| |
Simpler and has a nicer memory layout. Needed glib 2.38 to do this.
[endlessm/eos-sdk#421]
|
|
|
|
|
|
|
| |
We used this for our page manager, now we can just use GtkStack
with Gtk 3.10
[endlessm/eos-sdk#417]
|
|
|
|
|
|
|
|
| |
Playing with XDG_CONFIG_HOME in the previous commit showed that one
test failed if it was a relative path. Luckily that is a bug in the
test and not in the code.
[endlessm/eos-sdk#357]
|
|
|
|
|
|
|
|
|
| |
This works around the race condition in GIO
(https://bugzilla.gnome.org/show_bug.cgi?id=719455) while having the
added benefit of not cluttering one's own config directory with a bunch
of files every time the tests are run.
[endlessm/eos-sdk#357]
|
|
|
|
| |
This reverts commit a8848c6c4461ef25211c9dea6e5c65029c6f91da.
|
|
|
|
|
|
|
| |
The three test programs that fail intermittently must be disabled
until after the Echo release.
[endlessm/eos-sdk#410]
|
|
|
|
|
|
| |
ArticleModel now has an extra required construct parameter: "source".
[endlessm/eos-sdk#388]
|
|
|
|
|
| |
The current GJS search paths were inadvertently running the tests from
the installed JS modules, so that was causing Jenkins to fail.
|
|
|
|
|
|
|
| |
For good code hygiene, add tests for the models. After the refactoring,
they are less linked together, so easier to test.
[endlessm/eos-sdk#367]
|
|
|
|
|
|
|
| |
The Posix module is not available yet in our current version of GJS,
so there is no way to get a real PID in the Javascript tests. Fake it
with a random number (GLib.random_int(), uniformly distributed between
0..2^32-1)
|
|
|
|
|
|
| |
In order to prevent collisions between configuration directories, the
test applications get unique IDs from not just g_get_real_time(), but
also getpid()
|
|
|
|
|
|
|
|
|
| |
This test does not apply anymore; previously we set the size of an
EosWindow explicitly to be the screen size, but now we just call
gtk_window_maximize(). A window manager is free to ignore this call, so
we cannot reliably test for it -- e.g. in Jenkins' xvfb environment.
[endlessm/eos-sdk#337]
|
|
|
|
|
|
|
| |
The test that checks that EosApplication fails when the user config dir
is not writable, is now disabled if UID == 0 or EUID == 0.
[endlessm/eos-sdk#334]
|
|
|
|
|
|
|
|
| |
When running the tests, we want them to pick up the local copies of
Endless-0.typelib and libendless-0.so instead of the installed copies.
The tests now also run properly when there are no installed copies.
[endlessm/eos-sdk#321]
|
|
|
|
|
|
|
| |
Running tests with the same application ID causes DBus collisions.
Apparently this did not cause problems until now.
[endlessm/eos-sdk#303]
|
|
|
|
|
|
|
|
|
|
| |
During application startup, ensure that the config directory
($HOME/.config/com.example.application-id) exists and is writable.
Add API for accessing the directory:
- eos_application_get_config_dir()
- EosApplication:config-dir
[endlessm/eos-sdk#303]
|
|
|
|
|
|
|
| |
In case the name of the web action is URIencoded, make sure to URIdecode
it before looking it up in the dictionary of defined web actions.
[endlessm/eos-sdk#310]
|
|
|
|
|
|
|
|
|
| |
- Replace _webActions with define_web_action() method and another
define_web_actions() method for the Endless.js overrides file
- Replace _translationFunction with set_translation_function() and
get_translation_function()
[endlessm/eos-sdk#310]
|
|
|
|
|
|
|
| |
Clean up the code and make sure that it can be used as an example without
introducing any bad practices.
[endlessm/eos-sdk#310]
|
|
|
|
| |
[endlessm/eos-sdk#1015]
|
|
|
|
|
|
| |
This allows testing the FlexyGrid widget in a scrollable widget.
[endlessm/eos-sdk#1015]
|
|
|
|
|
|
| |
Begin by testing the basic accessors and construction.
[endlessm/eos-sdk#1015]
|
|
|
|
| |
[endlessm/eos-sdk#1015]
|
|\
| |
| | |
Unit tests for WebHelper
|
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the translation was such that it did a dummy translation,
italicizing the text to be translated. Now it looks for a translationFunction
property on the app object, and calls that on the text.
[endlessm/eos-sdk#290]
|
| |
| |
| |
| |
| |
| |
| |
| | |
Also, since the functions will likely be translated into C in the
future, give_them_underscored_names insteadOfCamelCase, in order to
avoid API changes.
[endlessm/eos-sdk#290]
|
| |
| |
| |
| |
| |
| |
| | |
The webhelper tests should be in their own directory, mirroring the
source directory structure.
[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]
|
|\ \
| |/
|/| |
#299 Gtk and clutter tests for framerate
|