| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Drop the section that talked about main and how to update
local checkouts - its been 2 years, people should have gotten
around to it by now. Add some general git hints instead.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Remove the mention of GNU (since that has not been case
for a long time, effectively), state that GTK is hosted
by the GNOME project, and point to GNOME as a place
for donations.
|
| | |
|
| |
|
|
|
|
|
| |
Updated Release notes links from https://developer.gnome.org/gtkX/unstable/YYYY.html
to https://developer.gnome.org/gtkX/stable/YYYY.html in the README.md file in the root
folder.
Closes #4001
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Use a trailing slash, otherwise we end up on an out of date mirror.
Fixes: #3483
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To build a better world sometimes means having to tear the old one down.
-- Alexander Pierce, "Captain America: The Winter Soldier"
ATK served us well for nearly 20 years, but the world has changed, and
GTK has changed with it. Now ATK is mostly a hindrance towards improving
the accessibility stack:
- it maps to a very specific implementation, AT-SPI, which is Linux and
Unix specific
- it requires implementing the same functionality in three different
layers of the stack: AT-SPI, ATK, and GTK
- only GTK uses it; every other Linux and Unix toolkit and application
talks to AT-SPI directly, including assistive technologies
Sadly, we cannot incrementally port GTK to a new accessibility stack;
since ATK insulates us entirely from the underlying implementation, we
cannot replace it piecemeal. Instead, we're going to remove everything
and then incrementally build on a clean slate:
- add an "accessible" interface, implemented by GTK objects directly,
which describe the accessible role and state changes for every UI
element
- add an "assistive technology context" to proxy a native accessibility
API, and assign it to every widget
- implement the AT context depending on the platform
For more information, see: https://gitlab.gnome.org/GNOME/gtk/-/issues/2833
|
| | |
|
| |
|
|
| |
Hopefully people will read it.
|
| |
|
|
|
|
| |
The README file still links to the old web page about mailing lists; the
link is now a 404 after the website redesign, and we don't use mailing
lists any more, in favour of Discourse.
|
| |
|
|
| |
We are dropping the plus.
|
| | |
|
| |
|
| |
Useful for exposing the documentation early.
|
| |
|
|
|
| |
We have a whole document for that, and it's up to date with regards to
the GitLab workflow.
|
| |
|
|
| |
We use GitLab issues, now.
|
| |
|
|
| |
Like all cool kids are doing, these days.
|
| | |
|
| |
|
|
| |
From the README file.
|
| |
|
|
|
| |
The separate `mesonconf` and `mesontest` binaries have been deprecated,
in favour of `meson` sub-commands.
|
|
|
Let's bring it into this century, and drop outdated information.
|
