| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Webhelper is now in its own repository:
https://github.com/endlessm/webhelper
https://phabricator.endlessm.com/T16203
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
[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]
|
|
|
|
|
|
| |
test/smoke-tests/large-content.js shows the warnings in action
[endlessm/eos-sdk#191]
|
|
|
|
|
|
|
| |
We used this for our page manager, now we can just use GtkStack
with Gtk 3.10
[endlessm/eos-sdk#417]
|
|\
| |
| | |
Unit tests for WebHelper
|
| |
| |
| |
| |
| |
| |
| | |
The webhelper tests should be in their own directory, mirroring the
source directory structure.
[endlessm/eos-sdk#290]
|
|\ \
| |/
|/| |
#299 Gtk and clutter tests for framerate
|
| |
| |
| |
| |
| |
| |
| | |
Not the greatest code, command line parsing could be better, but these
are smoke tests. README with some instructions
[endlessm/eos-sdk#299]
|
|/
|
|
|
|
|
|
| |
WebHelper is now importable using
const WebHelper = imports.webhelper;
[endlessm/eos-sdk#289]
|
|
|
|
|
|
|
|
|
|
|
| |
Add a highlight and shadow, on the bottom of the top bar; two pixels
go over the top bar, and two pixels go over the app content.
Added a smoke test with a button that turns red on press, in order to
test that the two pixels on top of the app content do not catch input
events.
[endlessm/eos-sdk#197]
|
|\
| |
| | |
#146 Layout of `EosActionMenu`
|
| |
| |
| |
| | |
[endlessm/eos-sdk#146]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#146]
|
|/
|
|
| |
[endlessm/eos-sdk#108]
|
|\
| |
| | |
#113 Convenience library for HTML/GTK communication
|
| |
| |
| |
| |
| |
| | |
/usr/share/gjs-1.0/ (or elsewhere in GJS's search path)
[endlessm/eos-sdk#113]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#113]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#113]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#113]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#113]
|
| |
| |
| |
| |
| |
| | |
a WebView with GTK+ functionality.
[endlessm/eos-sdk#113]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#104]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#104]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#104]
|
| |
| |
| |
| |
| |
| | |
available.
[endlessm/eos-sdk#104]
|
| |
| |
| |
| |
| |
| | |
an application, including changes to CSS.
[endlessm/eos-sdk#79]
|
| |
| |
| |
| |
| |
| | |
developer, as that will be deprecated in the future.
[endlessm/eos-sdk#79]
|
| |
| |
| |
| |
| |
| | |
linked to a EosActionButton in the menu. Added example code in action-buttons.js
[endlessm/eos-sdk#79]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#102]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#97]
|
| |
| |
| |
| |
| | |
Modified EosTopbar to remove a handful of assertion failures when adding left/center topbar widgets.
[endlessm/eos-sdk#97]
|
| |
| |
| |
| |
| | |
Work in progress. Topbars do not appear when using Endless theme.
[endlessm/eos-sdk#97]
|
| |
| |
| |
| |
| |
| |
| | |
Modified EosPageManager, EosTopbar and EosWindow to have support for the two new topbars.
app-window.js includes some tests for these two widgets.
[endlessm/eos-sdk#97]
|
| |
| |
| |
| |
| |
| | |
When background URI is changes for the currently visible page, it will
switch backgrounds without a transition animation.
[endlessm/eos-sdk#88]
|
|/
|
|
|
|
| |
Background is drawn in an internal widget so using the border width
would prevent it from drawing full screen.
[endlessm/eos-sdk#88]
|