Age | Commit message (Collapse) | Author |
|
The fontpack documentation says that when a glyph isn't found, all available fonts are checked in priority order. However, the implementation didn't actually do this.
Now there is a separate priority mapping for loaded fonts so they can be quickly scanned for any missing glyphs in the right order.
"iosevka-body" was prioritized higher because it provides a number of UI icons.
|
|
D-Bus command line tools can be called to make method calls to reveal
a file's location in the file manager.
|
|
|
|
The inline downloads UI finally has some interactivity: left-clicking on a finished download opens it in the default viewer app, and right-clicking shows a context menu with relevant actions.
|
|
TODO: This is font-dependent, so should actually use visual alignment...
|
|
Don't try to show a document while a long download is progressing, especially if we don't have any way to present the document format.
|
|
|
|
Saving this as the last point of progress. This direction is too complicated: Media needs to be a lot more sophisticated to allow dynamic and interactive media at the level of FontPacks. (A bit like Player handles audio playback.)
This will be reverted. FontPack management will happen using an another method.
|
|
Media still needs more work to get rid of redundancies and make lookups faster.
FontPacks are manipulated as Media items (not unlike images) so they can be previewed on page, and installed via a click.
FontPack management is not trivial as it includes such details as versioning and whether individual packs are enabled or disabled.
|
|
The built-in fonts are loaded via FontPack, and the font table is now constructed dynamically based on available fonts.
A full set of variants (style, size) are prepared for each font, but some of the data gets allocated lazily when needed.
GmRun needed a larger allocation for fonts, so now all the fields are combined into a single bit field.
TODO: Glyph scaling, vertical offsets, and symbol lookup are still not fully working.
|
|
Only process mouse wheel events on the root over which the mouse is currently.
|
|
The distinction between measure_Text and advance_Text was not very clear. Now there are only measure_Text functions that return both the bounds and the cursor position advancement, and the appropriate metrics are used by the caller.
|
|
|
|
The seven segment digits are coming from a different font.
|
|
"about:feeds", inline downloads, and media player UI didn't have translations.
|
|
|
|
The greenish-yellow was a bit off-putting.
|