| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
Our JS tests require a session bus, but on Jenkins builder we won't have
it. Run them with a test session bus.
The run-with-dbus script is borrowed from GJS and simplified a bit.
[endlessm/eos-sdk#291]
|
|
|
|
|
|
|
|
|
| |
This exposes the function set by webhelper.set_ngettext() to the client-
side Javascript as a ngettext() function, defined on the global window
object. This allows apps to translate messages that need to be separated
into singular and plural, just like the C ngettext() function.
[endlessm/eos-sdk#291]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This exposes the function set by webhelper.set_gettext() to the client-
side Javascript as a gettext() function, defined on the global window
object. This allows apps to translate messages that are generated
at runtime, not just messages in static HTML.
Some often-used JavaScriptCore operations can be turned into separate
functions, which we can put in a separate source file. This is in
anticipation of the next commit where we will define another function
property of the global object.
[endlessm/eos-sdk#291]
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|\
| |
| | |
Generate XML reports when running on Jenkins
|
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
|/
|
|
| |
Or the test will fail when trying to open the GTK display.
|
|
|
|
|
|
|
| |
Jasmine has its own timeout timer on each spec, so we don't need to set
one up ourselves.
[endlessm/eos-sdk#3171]
|
|
|
|
|
|
|
| |
This is vulnerable to being overwritten. Instead, define it in the top
level Makefile and append to it in the included Makefile.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
| |
Having these tiny included Makefiles is confusing and vulnerable to
mistakenly overwriting variables.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
| |
EosFlexyGrid is deprecated, so we don't want a demo of it in our tests.
[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 somehow escaped Sam's big switcheroo last year.
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
| |
This test runner dates from even before eos-jasmine, and is not used
anywhere.
[endlessm/eos-sdk#3054]
|
|
|
|
| |
[endlessm/eos-sdk#3054]
|
|
|
|
|
|
|
|
| |
This removes the code that was copied from the LGPL eos-theme repository
and replaces it with a different simple spinner animation, adapted from
the MIT-licensed http://projects.lukehaas.me/css-loaders/
[endlessm/eos-sdk#2948]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
| |
UniqueAppFixture is a more appropriate name for the fixture since it is
not only used to test config directories. Add a macro to make the test
adding code more convenient.
[endlessm/eos-sdk#2934]
|
|\
| |
| | |
Update eos-jasmine submodule
|
| |
| |
| |
| |
| |
| | |
Fixes some already-fixed bugs.
[endlessm/eos-sdk#2499]
|
|/
|
|
|
|
|
|
|
|
| |
Previously, if you created an Endless.TopbarNavButton with no_show_all
set to TRUE, and subsequently called show() on it, it would not become
visible, because the child widgets were still not shown. By showing them
at construct time, we solve this problem because they immediately become
visible when the TopbarNavButton widget itself is shown.
[endlessm/eos-sdk#2495]
|
|
|
|
|
|
|
|
|
|
|
|
| |
When calling app.quit(), the hold count on the application is ignored,
which causes undefined behavior when the application's window still
thinks it has a hold on the application and control is returned
to the MainLoop. This patch changes the way that applications are
quit in testWebActions by calling destroy() on the application's window,
which decrements the hold count on the application and implicitly causes
the application to close.
[endlessm/eos-sdk#1881]
|
|
|
|
| |
This reverts commit 1f4a83a10d03856ce95dcf3a160f725685a6f8b6.
|
|
|
|
|
|
|
| |
This merits more investigation, but for now we just disable them. More
info to follow on issue.
[endlessm/eos-sdk#1675]
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
[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]
|