| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
| |
This requires some restructuring because the SVG image and the label
need to have different CSS. I ported the CompositeButton class from the
photo app, in order to have the button transfer its prelight/active
state flags to its children.
[endlessm/eos-sdk#504]
|
|\
| |
| | |
Crop category pixbufs from bottom left
|
| |
| |
| |
| |
| |
| |
| | |
Instead of the top left which we were doing until now, crop the
pixbufs from the bottom left.
[endlessm/eos-sdk#487]
|
|/
|
|
|
|
| |
Increase font sizes of category description and article list titles.
[endlessm/eos-sdk#506]
|
|\
| |
| | |
Article list titles should be in normal case
|
| |
| |
| |
| |
| |
| | |
Previously, they were upper case.
[endlessm/eos-sdk#500]
|
|/
|
|
|
|
|
|
| |
Also, remove the now unused asset, and as long as we are renaming the
constant, call it a RESOURCE_PATH instead of a URI, because that's what
it is.
[endlessm/eos-sdk#502]
|
|
|
|
|
| |
It did not extend vertically or all the way to the left of the screen
[endlessm/eos-sdk#458]
|
|
|
|
|
|
| |
Updated the Wikipedia CSS for domain-specific Wikipedia apps to automatically resize fonts using em.
[endlessm/eos-sdk#468]
|
|
|
|
|
|
|
| |
Per Dalio's request. Hard coded to 40px pixels so not very adaptable. Tried to
imitate the specs on basecamp. This button was supposed to appear on the left
of page and not centered in the open space there.
[endlessm/eos-sdk#427]
|
|
|
|
|
|
|
|
| |
Another one. This one for gtk 3.10. With the new Gtk version,
overriding get_preferred_width to handle overlong titles
can mess up the height allocation when labels wrap. Specifying
width for height management for the button fixed this
[endlessm/eos-sdk#376]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this the size request of the title category button is set
based on the toplevels allocation. This broke when EosWindow's size
request was fixed.
Having some sort of container or bind constraint that allocated things
based on percentages is the eventual solution here. For now I used
a column homogeneous grid where each column was a percentage of the
allocation. A little gross, but works fine, and our wiki apps handle
resizing much better than they did before now
[endlessm/eos-sdk#376]
[endlessm/eos-sdk#376]
|
|
|
|
|
|
|
|
| |
No longer set the arrow images opacity, which seemed to be the
root a visual bug. The overlay also means the arrow will always
appear in the right of the category button and not be cut off
even if the label is overlong
[endlessm/eos-sdk#407]
|
|
|
|
|
|
| |
Subclass button, so we don't need our own event boxes and event
handling
[endlessm/eos-sdk#407]
|
|
|
|
|
|
|
| |
This widget was used on the category page. Without the call to
$dispose there's a large memory leak each time the category page
is displayed on screen.
[endlessm/eos-sdk#408]
|
|\
| |
| | |
Domain specific apps no longer must specify links
|
| |
| |
| |
| |
| |
| |
| |
| | |
Refactored the process of settings which articles should be linked
such that, if no linked articles JSON is specified, the view will
behave as if hide_links were set to true
[endlessm/eos-sdk#402]
|
| |
| |
| |
| |
| |
| | |
For our category buttons, otherwise the context and all associated
resources are never freed
[endlessm/eos-sdk#403]
|
|/
|
|
| |
This reverts commit e7dc5aa70b27f3251ef82ce91d05dea770a0e7ac.
|
|
|
|
|
|
|
| |
This reverts part of commit [ddcbb17]. It is a workaround for a GJS bug
and should itself be reverted later.
[endlessm/eos-sdk#399]
|
|
|
|
|
|
|
|
|
|
| |
- Fonts are changed to be 150px and 48px for ODROID's 1920x1080
resolution
- Word-wrapping widths are set to approximately reproduce the deck
[endlessm/eos-sdk#394]
[endlessm/eos-sdk#394]
|
|
|
|
| |
[endlessm/eos-sdk#394]
|
|
|
|
|
|
|
|
| |
Before we were loading them every time size_allocate was called,
even if the widget was not even realized. Now just check during
draw if the pixbuf needs to be reloaded. Also draw the pixbuf
directly with cairo which cuts down on widget hierarchy.
[endlessm/eos-sdk#349]
|
|
|
|
|
|
| |
Also, call the query parameter appname instead of app_name
[endlessm/eos-sdk#386]
|
|
|
|
|
|
|
|
| |
Previously we were not interecepting requests to /wiki/[title] in
wikipedia webview, which meant that when we refresh to online, all
links would not work.
[endlessm/eos-sdk#386]
|
|
|
|
|
|
|
| |
Previously we were loading articles in domain specific apps by title.
Now, we are loading by Id, which is the suffix of the url.
[endlessm/eos-sdk#386]
|
|\
| |
| | |
Issues/383
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need to pass the 'source' parameter to NodeJS to indicate the
source database that an article comes from. This should later be
replaced by indicating this information in the database name.
[endlessm/eos-sdk#383]
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the URI scheme starts with 'browser-', then show the corresponding
URI without 'browser-' in the system default browser. e.g. shows
browser-http://google.com as http://google.com in the system browser.
[endlessm/eos-sdk#383]
|
| |
| |
| |
| |
| |
| |
| | |
This is because the NodeJS server and the database don't know about the
WikiHow artice 'cocinar-arroz'; it is stored as 'Cómo Cocinar Arroz'.
[endlessm/eos-sdk#380]
|
|/
|
|
|
|
| |
Make requests to 127.0.0.1:3000/v1 instead of 127.0.0.1:3000.
[endlessm/eos-wikipedia-offline#145]
|
|\
| |
| | |
#377 WikiWebView now takes personality and app_name
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, we only had one database so the wiki web view
did not have to pass its app name and personality to node
js API. Now that each app has its own database, this
needs to happen
[endlessm/eos-sdk#377]
[endlessm/eos-sdk#377]
[endlessm/eos-sdk#377]
[endlessm/eos-sdk#377]
|
|/
|
|
|
|
| |
To load a list of articles matching search query
[endlessm/eos-sdk#373]
|
|
|
|
|
|
| |
The widget has been removed but an import remained
[endlessm/eos-sdk#348]
|
|
|
|
|
|
|
|
|
| |
Moved all the transition code to the view, because it made
making the scroll up calls we need easier. Also think thats the
right place for the scroll logic to live. Took some nice code
from :tomato:'s spike to use signals on back button presses in the
view.
[endlessm/eos-sdk#348]
|
|
|
|
|
|
|
| |
For good code hygiene, let's make sure we document all new and changed
APIs.
[endlessm/eos-sdk#367]
|
|
|
|
|
|
|
|
|
| |
Reorganizes the various models, presenters, and views, so that the wiki
apps work unchanged with the new JSON export format. Also refactors so
that there is less linkage between models, presenters, and views, so
further updates will hopefully be less extensive.
[endlessm/eos-sdk#367]
|
|
|
|
|
|
|
| |
Minor refactoring, because this._domain_wiki_model and
this._domain_wiki_view are a lot of unnecessary typing.
[endlessm/eos-sdk#367]
|
|\
| |
| | |
wikipedia: Use Lato fonts
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fonts are changed according to the conversion table. It turns out that
what we thought was the "Benton Sans correction" does not only apply to
Benton Sans - I think it is due to GTK's lack of baseline alignment,
something that has been rectified in GTK 3.10.
[endlessm/eos-sdk#361]
|