| Commit message (Collapse) | Author | Age |
... | |
|/
|
|
|
|
|
| |
The pointer may be on empty space while still within the bounds of the
FlexyGrid widget.
[endlessm/eos-shell#1887]
|
|\
| |
| | |
#517 Increase font size of category button to match spec
|
| |
| |
| |
| | |
[endlessm/eos-sdk#517]
|
|\ \
| |/
|/| |
#535 show internal widgets
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
EosWindow manages the page background transition and relies on a
stack internally to transition. The stack was not properly
flipping between its child widgets before show_all was called in
user code. This is because stack's set_visible_child method won't
work unless the children are actually visible. Calling show our
stacks children fixes the problem.
[endlessm/eos-sdk#535]
|
|\ \
| | |
| | | |
#538 Always reserve space for arrow on article list
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When setting a flag on a child widget in composite button, we were
accidentally clearing all other flags on the child widget. So on
mouse press on a category button, when both ACTIVE and PRELIGHT flags
are set, we would clear the PRELIGHT flag when setting ACTIVE. So our
arrow button would disappear during mouse press
[endlessm/eos-sdk#537]
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This keeps the content from jumping on article list mouseover. Used
the same opacity trick we use for the category button arrow. Did this
in js instead of css, and the image file was set in js and I wanted
to be consistent. But could also be done in css with state flags
[endlessm/eos-sdk#537]
|
|\ \
| |/
|/| |
#519 Fix position of "other categories" button
|
| |
| |
| |
| |
| |
| |
| |
| | |
Design specified this should be 1/32 of the screen width away from
the left hand side. We don't have a great way to set percentage
margins, so just did this at 1080x1920 for now. So 1920/32=60 pixels
from the left
[endlessm/eos-sdk#519]
|
|\ \
| |/
|/| |
#484 Add publicly available font size property
|
|/
|
|
|
|
| |
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]
|
|\
| |
| | |
First round of dev vm preparation scripts
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| |
| |
| | |
per task
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| |
| |
| |
| | |
[endlessm/eos-sdk#1620]
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
bit higher. Still needs work
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Temp fix for gjs mem leak
|
| | |
| | |
| | |
| | |
| | |
| | | |
Wiki apps allocate pixbufs each time they draws at a new size.
Memory will skyrocket unless will demand spidermonkey does some
garbage collection
|
|/ /
| |
| |
| |
| | |
Otherwise we never properly initialize that gobject which can lead to
all sorts of problems
|
|\ \
| | |
| | | |
Issues/505
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The category "go" arrow should never overlap the label text, so this
moves it out of its overlay and puts it in the same layer as the label.
The label now uses baseline alignment, and we can get rid of the hacky
extra padding in the CSS.
Currently, the innards of the category button look like this:
+---------------------------------------+
| Grid, hexpand: TRUE, halign: FILL |
| +------------------+ +--------------+ |
| | Label | | Arrow button | |
| | halign: START | | halign: END | |
| | valign: BASELINE | | valign: END | |
| +------------------+ +--------------+ |
+---------------------------------------+
The arrow button does not have valign BASELINE, because that would
align it so it was even with the first line of the label if the label
was wrapped over two lines:
(GOOD) (BAD)
HISTORY HISTORY >
& POLITICS > & POLITICS
Also, I have removed the "width-chars" property of the label, because,
as in the programming app in a commit which I cannot now find, when the
label wraps, the width-chars property makes it request a very odd size.
[endlessm/eos-sdk#505]
|
| | |
| | |
| | |
| | |
| | |
| | | |
This allows the arrow fade-in and fade-out to be specified in the CSS.
[endlessm/eos-sdk#505]
|
| | |
| | |
| | |
| | |
| | |
| | | |
Replace the old PNG asset with an SVG asset.
[endlessm/eos-sdk#505]
|
|\| |
| | |
| | | |
Issues/504
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The shadow was being cut off because it extended beyond the image;
take some padding out of the button's general padding and add it
specifically to the image widget. Make sure the hit area is still
correct.
[endlessm/eos-sdk#504]
|
| | |
| | |
| | |
| | |
| | |
| | | |
For better code organization and cleaner CSS; add style classes.
[endlessm/eos-sdk#504]
|