| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
Setting the width here can mean that the popup gets a different width
from the search box. Instead, we want it to match the search box's width
and ellipsize the label if there's not enough space.
https://phabricator.endlessm.com/T20352
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When clicking on a result from the autocomplete popup, we should select
the first index of the tree path. (The list is a flat list, so there is
always only one index.)
This prevents a warning about a missing property of
[Symbol.toPrimitive], because we were indexing this._items with the
indices array (which is not a primitive) instead of its first item.
https://phabricator.endlessm.com/T21027
|
| |
|
|
|
|
|
|
|
| |
In ES6, variables declared with "const" and "let" go into the "lexical
scope" rather than the normal scope. Therefore, they are not available as
properties on modules. GJS preserves the old behaviour with a warning,
but we should fix our code anyway.
https://phabricator.endlessm.com/T18106
|
| |\
| |
| | |
Don't enforce a minimum size for search box
|
| | |
| |
| |
| |
| |
| |
| | |
Instead allow clients of this widget to set their
own minimum and maximum sizes.
[endlessm/eos-sdk#3974]
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
When running on small screens, some auto-complete result titles do not fit in
the screen. This was most often observed in composite mode (720x480) and 800x600
resolutions.
Now, we ellipsize the cell renderer accordingly by checking the screen width,
based on the responsive system breakpoints defined by the Design team.
(Fernando and Martin).
[endlessm/eos-sdk#4016]
|
| |
|
|
|
|
| |
This way we can set the search box text without triggering the
signals for settings autocomplete entries
[endlessm/eos-sdk#3442]
|
| |
|
|
|
|
| |
We'll leave it up to the application itself what to populate the
entry with after an autocomplete item is selected
[endlessm/eos-sdk#3442]
|
| |
|
|
|
|
|
| |
If the secondary icon is displayed, it should change the mouse cursor
to a hand as well.
[endlessm/eos-sdk#2962]
|
| |
|
|
|
|
|
|
| |
This changes the mouse pointer to be a 'hand' cursor when hovering over
certain clickable UI elements: the back/forward buttons on the title
bar, and the magnifying glass icon in the search box.
[endlessm/eos-sdk#1483]
|
| |
|
|
|
|
|
|
| |
Previously we were using the entry completions default
match function which will filter words by prefix. However
we want all filtering to be done in the knowledge engine
in a smarter way so this entry completion should just match
on all results.
|
| |
|
|
|
|
| |
Some hacky css selecting is involved, but gets us a much nicer
completion drop down
[endlessm/eos-sdk#1578]
|
| |
|
|
| |
So they don't clash with gtype names in our apps
|
|
|
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.
|
