Gnomelets 🎅 - Brighten up your GNOME desktop with Gnomelets! This extension brings small, animated 2D characters to life, letting them roam freely across your screen. They walk, jump, and even balance on top of your open windows. Watch as they fall from the top of the screen, land on your active windows, and explore your desktop environment with charming pixel-art animations. 🎄 Christmas Special Edition 🎄 In the spirit of the holiday season, we have added a special guest: Santa Claus! You can now select Santa as your desktop companion to bring some festive cheer to your workflow. Features: - Custom Characters: Easily add your own pixel-art characters. - Physics-based Movement: Gnomelets obey gravity, falling naturally and landing on solid surfaces. - Window Interaction: They detect open windows and can walk along their title bars and top edges. - Pixel-Art Animations: Smooth idle, walking, jumping, and falling animations. - State Persistence: Gnomelets remember where they were even after you restart the shell or disable/enable the extension. - Multi-Monitor Support: They can travel and spawn across all your connected screens. - Smart AI Behavior: Gnomelets employ intelligent jumping mechanics, detecting edges to perform daring leaps and predicting reachable windows to climb upwards dynamically. - Top Bar Controls: A convenient menu in the top bar lets you instantly re-spawn all gnomelets or toggle their visibility on/off without opening settings. - Interactive Drag & Drop with Momentum: Pick up gnomelets with your mouse and toss them! They now support physics-based throwing—release them while moving the mouse to fling them across the screen. - Flexible Distraction-Free Modes: Enhanced 'Partial' and 'Disallow' modes to keep your focus when windows are maximized. - Dash to Dock (Ubuntu Dock) / Dash to Panel Support: Explicitly choose between Dash to Dock (Ubuntu Dock), Dash to Panel, or None for optimized performance. - Jump Power Control: Customize how high your gnomelets can jump!
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 11 | Active |
| 10 | Active |
| 9 | Inactive |
| 8 | Inactive |
| 7 | Inactive |
| 6 | Inactive |
| 5 | Inactive |
| 4 | Rejected |
| 3 | Inactive |
| 2 | Rejected |
| 1 | Rejected |
1. Move line 995-998 `extension.js` out of that if condition. 2. Better to use `destroy()` method instead of connecting signal (line 948 `extension.js`). 3. Please don't use the same property name for storing two different timeout signals in one class (line 699, 911 `extension.js`). Since those timeouts doing the same in the callback, just move them to a function. That way, you only create one timeout.
Thanks for the review. I have addressed all the reported issues in the upcoming update: Moved the cleanup logic in disable() (lines 995-998) out of the conditional block to ensure resources are always properly released. Replaced the destroy signal connection in the indicator class with a proper destroy() method override. Refactored the timer logic into _startTimer() and _stopTimer() helper functions to prevent code duplication and ensure the same property isn't used for multiple signals. Happy Holidays! 🎄 Best regards, Mauro Mauro
Thanks! and Happy Holidays!
Gnomelets