Skip to content

Commit

Permalink
Update readme.
Browse files Browse the repository at this point in the history
  • Loading branch information
madewokherd committed Mar 4, 2024
1 parent 74f5e96 commit e289bc2
Showing 1 changed file with 1 addition and 15 deletions.
16 changes: 1 addition & 15 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Wayland has not been tested yet, but it probably does not work.

## Windows

Windows is supported using UI Automation. Sometimes it is slow to respond to UI updates.
Windows is supported using Win32 and MSAA. Sometimes it is slow to respond to UI updates.

# Setup

Expand Down Expand Up @@ -102,20 +102,6 @@ The language works based on pattern-matching. In this example we are searching f

All of these conditions are monitored, and if any of them changes (for example, a menu opens, making the combo box no longer "interactable"), the declarations inside no longer apply.

# TODO list

* Rewrite the AT-SPI2 code using Tmds.Dbus.Protocol, which will solve a limitation on the number of match rules one can have on DBus.
* Allow for watching X11 state, which is useful for detecting window decorations, and objects invisible to AT-SPI2 (due to bugs).
* Add late evaluation and function declarations to GUDL, as the limitations are unweildy.
* Add "include" directive to GUDL so that toolkit and application specific behaviors, and user settings, can be organized better.
* Fill out support for some Linux desktops and their builtin applications.
* Create an AT-SPI2 bridge for Win32/MSAA/UIAutomation, which will be a separate project, and use that from Xalia. This can be shared with Wine and will solve some difficulties with MSAA an UIAutomation. It's also necessary if we want Xalia to work correctly with applications running in Wine.
* Fill out support for the Windows desktop and its builtin applications.
* Add support for the ISimpleDOM interfaces (web browsers).
* Develop a GUI for starting/stopping Xalia, configuring controls, and configuring startup behavior. This will require an RPC service.
* Fully document GUDL.
* Provide a window showing button prompts for the currently available actions. This would be a separate program making use of an RPC service.

# Debugging Environment Variables

`XALIA_DEBUG` can be set to a GUDL boolean expression selecting some elements, for which Xalia will output debugging information. For example, `XALIA_DEBUG=is_root` will output declarations on the root element. Currently, any properties used must be referenced inside `main.gudl` for this to work.
Expand Down

0 comments on commit e289bc2

Please sign in to comment.