GSoC/20125/StatusReports/ZhengJiahong

Python virtual environments in Cantor

KWin's handling of game controller input is fragmented. Applications directly manage controller input, leading to inconsistencies, the inability of the system to recognize controller input for power management, and unintentionally enabling/disabling "lizard mode" in certain controllers.

In this project I'll be creating a solution to unify game controller input within KWin by capturing controller events, creating a virtual controller emulation layer, and ensuring proper routing of input to applications.

Mentors

Alexander Semke

Israel Galadima

Work report

Week 1-2

Week 3-4

Week 5-6

Week 7-8

Week 9-10

Week 11-12

Future Plans

Links

Contact

[email protected]

@yorisoft:matrix.org

GSoC Requirements

It must be easy to identify the work you have done. (i.e. the changes you made or new code.)

When someone goes to the provided URL it should be clear what work you did without requiring them to do significant additional digging.

It should be in a stable location. The URL cannot be changed after submission.

Someone else should be able to use the content at (or referenced from) the target of the link to extend your work.

If your work is 100% complete, they should be able to use it.

If your work is not 100% complete, it should be clear what's left to do.

KDE Requirements

A good status report will include:

Design documents the student created
Short video of the work, or screenshots as appropriate
Link to a list of commits (example)
Link to blog posts (on KDE Planet, at least monthly)