Currently regardless of whether skippy is ran on daemon mode or not, all calculations and windows states tracking are only done during skippy activation. To enhanced features such as #36, skippy has to run as daemon, and track windows states continually.
This is a major task involving modifying the main event loop, which currently handles X events ONLY when skippy is activated. Code centred around layout calculation, current client windows tracking, updating and rendering need to be refactored also. Finally CPU overhead need to be evaluated.
Currently regardless of whether skippy is ran on daemon mode or not, all calculations and windows states tracking are only done during skippy activation. To enhanced features such as #36, skippy has to run as daemon, and track windows states continually.
This is a major task involving modifying the main event loop, which currently handles X events ONLY when skippy is activated. Code centred around layout calculation, current client windows tracking, updating and rendering need to be refactored also. Finally CPU overhead need to be evaluated.