• Updated changelog, release notes, home page, and version.
• Tagged as v0.2.0.

• Added some basic info about layouts to minx.core.wm doc string.
• Updated hooks-list.wiki with info about new hooks.
• Fixed a bug in layman.receptive_layout(): have to add layout returned by receptive_layout_hook to layouts list.
• In layman.find(), added ability to search for layouts based on their names. (Noticed we needed this ability when writing sample code to illustrate layouts usage.)
• Removed unnecessary warnings from minxlib::window, which were simply cluttering the log.
• Other minor edits elsewhere.

• Moved focus change event handlers from minx.core.xevents to minx.layout.base.
• Removed reparent notification handler from minx.core.xevents in favour of handling the event entirely from minx.layout.base.

This should pretty much all the code that's needed for the 0.2.0 release. Now to tackle the documentation... check-in: 4dc459e610 user: manuv tags: dev1.x

• Added support for end-user hook to create layouts before managing existing windows and entering event loop.

• Made the display and root_windows members of the minx.core.wm class public (i.e., removed leading underscore) so that they can be accessed by the init_hook.

• Removed unnecessary layout creation in wm.start() because the default layout logic in the layman.receptive_layout() method takes care of this already.

• Forgotten to register exception translators for protocol errors.
• Add exception handler for generic protocol errors in minx.core.wm event loop.

Got the idea for this from a cursory perusal of the code for xbindkeys. And now (at long last) key bindings work flawlessly! Getting close to the 0.2.0 release... check-in: 17ccc163e4 user: manuv tags: dev1.x

• Since we often need to meddle with a window's geometry, changed minxlib::window::geometry() so it returns a list rather than (an immutable) tuple.
• Fixed a bug in minx.layout.full.configure_request() that was offsetting window placement within the layout window.

However, target window still gets the key press event (e.g., a terminal window types 'd' when M4-D is pressed). Also, it doesn't work for all windows (e.g., xmessage doesn't respond). So there's still some work to be done here... check-in: bfb7417666 user: manuv tags: dev1.x

But at least now we have some basic infrastructure for a separate layouts directory/subpackage. check-in: 0a84c4d950 user: manuv tags: dev1.x

Next steps:

• Code clean-up and documentation.
• Bug fix: killing a window doesn't focus another.
• Bug fix: some key bindings are not recognized when a window has focus.
• Extract and abstract layout functionality currently in wm and xevents.
• Remove hard-coded border adjustments when resizing windows to fit layout.
• Add support for multiple screens and Xinerama.
• End-user hooks for creating custom layouts before launching window manager.
• Layout windows need to be transparent/invisible.
• Documentation for all of this (design notes, HOWTO's, etc.).

That's when we'll be ready to hit 0.2.0. check-in: ab72e115ad user: manuv tags: dev1.x

Eventually, should implement layouts so that killing them doesn't take down the window manager. check-in: 0d21ae6035 user: manuv tags: dev1.x

Also: various minor edits. check-in: fa47a47a48 user: manuv tags: dev1.x

Also some minor fixes to:

• minxlib/factory.hh: figured out Boost iterator adaptor weirdness in factory_map::iterator::dereference().
• minxlib/exception.cc: corrected a stale comment.

• Minx doesn't have to maintain internal mappings of which windows a layout is managing, their respective geometries, etc. Instead, we can simply query the X server for this info when we need it.

• It is much easier to implement layout nesting (again because the X server already provides the necessary infrastructure for creating and managing hierarchies of windows).

• Because layouts are simply top-level windows, entire arrangements of tiled windows can be easily layered and moved around. That is, instead of a single floating layer, we can have multiple layers.

• Moving windows between layouts is a simple matter of reparenting the window. X will generate appropriate events, which Minx can handle to update any internal state (which is already minimal).

• If Xinerama is available, moving windows and entire layouts across screens should be fairly straightforward to implement (useful, for example, for laptop un/docking).

Seriously, what's not to like?

Now, having touted the numerous benefits and basic soundness (genius, anyone?) of the layouts-as-windows idea, a few words about this check-in:

It begins the long and winding road leading to the grand vision described above. At this stage, of course, little of any real use is available. minxlib provides an API for creating new windows and the main window manager object uses it to create a black, top-level window the same size as the root window.

That's pretty much it; no window management, tiling, multiple screen support, etc., just yet. In fact, the layout window is just another window that Minx manages. Killing it, hilariously enough, nukes the window manager. check-in: df1a814742 user: manuv tags: dev1.x

• Added an Asymptote program to generate the Minx logo.
• Updated makefile in wiki/img to generate logo.
• Added the logo itself to version control.

This commit also adds the updated API documentation for the stuff that changed. check-in: 8ea4412bae user: mvnathan tags: rel1.x

TODO:

• Check for and use WM_DELETE_WINDOW protocol if supported.
• Add Doxygen comments for new code.

This check-in marks the release of version 0.1.6. check-in: defde8c2a2 user: mvnathan tags: rel1.x, v0.1.6

• Updated news section of home page, release notes, and changelog for version 0.1.6.
• Bumped up version number to 0.1.6.

• Fixed minxlib::keymap so its Doxygen documentation will be generated.
• Added link to minxlib::keymap documentation on Doxygen main page.
• Added _minxlib to grp_* labels for minxlib::event and minxlib::exception. Fixed reference in minxlib::display to use new label.
• Added table showing mapping between minxlib and Xlib names for minxlib::protocol_error::failed_request_reason enum.

• Added a FAQ about key bindings.
• Added default key bindings to the hooks list.

For example, if Num Lock is configured as Mod2, all key events will reported with Mod2 set in case Num Lock is on. Thus, simple F1 presses will be reported and interpreted as Mod2 + F1. If there's no such key binding, Minx will ignore it; if there is such a key binding, Minx will end up executing the wrong function!

This commit solves the problem described above. check-in: 7a3edcd1c4 user: mvnathan tags: dev1.x

• Moved focus cycling code from xevents to wm.
• Removed hard-coded F1 for focus cycling.

TODO: Document minx.core.wm.focus_next() and focus_prev(). check-in: 4aac700f62 user: mvnathan tags: dev1.x

NOTE: Code is in sore need of documentation; many functions have none and, even worse, some of it is downright wrong! check-in: afb577d64d user: mvnathan tags: dev1.x

• Updated changelog and release notes for version 0.1.5.
• Updated home page for version 0.1.5.
• Bumped up version number to 0.1.5.

Tagging the release as v0.1.5. check-in: 45c8645a94 user: mvnathan tags: rel1.x, v0.1.5

Otherwise, end-user code will fail if it doesn't check for the existence of these keys in the dictionary returned by the properties() method or fails to handle the resulting KeyError.

The problem became apparent when launching an XFCE Terminal, which creates hidden top-level windows without the above properties. The end-user manage_hook then bombs out when it examines the properties map for these hidden windows. check-in: bca46583e9 user: mvnathan tags: dev1.x

• Added HOWTO for hooks and a page documenting currently supported hooks.
• Updated home page to include links to above documentation.

• Added minxlib::window::properties() to return WM_NAME, WM_ICON_NAME, and WM_CLASS window properties via an STL map (which gets converted to a Python dict when passed back to Minx's Python core).
• Souped up the documentation of some of the stuff in the minxlib/window module.
• Added a converter in minxlib/python.hh to convert STL maps to Python dicts.
• Updated TODO list for version 0.1.5. Now, only documentation tasks remain for the release...

• Added ability to send arbitrary number of arguments to minx.core.hooks.hooks.trigger().
• Added logging to and updated documentation in minx.core.hooks module.
• Updated TODO list.

• Added support for manage_hook to minx.core.xevents so that newly created windows are filtered through the manage_hook.
• Updated documentation in minx.core.hooks module.
• Updated TODO list for version 0.1.5.

The code seems to work fine. It needs to be documented (especially, minx.core.hooks). check-in: c8b873c392 user: mvnathan tags: dev1.x

• Updated changelog, release notes, and home page for version 0.1.4.
• Bumped up version number to 0.1.4 and tagging as v0.1.4.

Looks like we're ready now to release 0.1.4... check-in: 598d484968 user: mvnathan tags: dev1.x

Code still needs to be properly documented before we can release 0.1.4. check-in: 7849be1f8d user: mvnathan tags: dev1.x

Code needs to be refactored and documented. check-in: 4cfdf7dc3c user: mvnathan tags: dev1.x

Next step: make minx.core.wm actually manage the returned list of windows before it goes into its event loop. check-in: ea3a1fb457 user: manuv tags: dev1.x

• Added wiki/logging.wiki and updated home page to point to it.
• Updated version 0.1.3 TODO list.

• Added a filter to the Minx logging configuration to remove the "minx." prefix from logger names and to remove the line numbers and function names from log records generated by the minxlib module.
• Minor fixes to logging statements in minxlib::window.

This solves both these bugs that were introduced with the switch to window border updates via focus handlers:

• [Focus reverts to root]
• [Terminal Window Border Flashes on Focus Changes]

• Updated wiki/milestones.wiki to reflect Minx's ability to already work across multiple screens and a new sequence of patches in the 0.1.x series.
• Updated wiki/todo.wiki to show steps for getting to version 0.1.2.

• Added new API docs to release branch.
• Added missing images for Doxygen-generated pages.

Should now be ready to release 0.1.1. check-in: c016b10619 user: mvnathan tags: dev1.x

• Added focus_in and focus_out events to minxlib's event hierarchy.
• Reworked focus-related border color change so that the minx.core.window module does it via handlers for the above events.

NOTE: This mostly works. But there's a problem every now and then when a window is destroyed and, in between the resulting unmap and destroy notifications, is a focus_out event that causes a BadWindow X_ChangeWindowAttributes protocol error when the focus_out handler tries to set the border color of the window (which has been destroyed) to the inactive border color.

To fix this, we need a minxlib.change_window_attributes protocol error that the event loop can ignore. That should be coming up in the next check-in (or thereabouts)... check-in: 1b644ead0b user: mvnathan tags: dev1.x

• Added several relevant X event handlers to minx.core.window. This architectural change will eventually allow focus border color changes to be handled by minx.core.window, thus, ensuring that we don't end up with one module (viz., minx.core.xevents) that becomes a do-all monstrosity.
• Removed top-level window tracking from minx.core.wm. This is now done in minx.core.window.
• Made sure that minx.core.hooks.append() doesn't create duplicate entries in the list of hooks for some key.

• Added reference to minxlib::version to Doxygen's main page.
• Made release steps in wiki/process.wiki more accurate.
• Minor fixes to home page.

• Disabled header file generation; don't really need these as end-users should, firstly, be concerned mostly with Minx's Python core and not care much about minxlib.

Secondly, only the headers are documented. Generating HTML for the code would only make sense if we wanted people to look at the implementations of different classes and functions. Minx's API docs are only for its public interfaces. If someone is interested in seeing how things are implemented, they can just look at the code in an editor (if syntax highlighting is desired, which is pretty much the only point of having Doxygen generate HTML for the source and header files).

• Changed @code block in the minx.core.wm.wm class's doc string to a @verbatim block. Doxygen links minx.core.wm inside the code block to a non-existent file. While the verbatim block lacks the prettiness of syntax highlighting, at least it isn't pointing off to nowhere.

Note: Using a % sign does not suppress Doxygen's automatic link generation inside @code blocks. The [317806fcf7|previous check-in] made that mistake (didn't test it; just checked it in:).

• Added changelog and release notes for version 0.1.0.
• Updated home page with a spot of news about upcoming release.

• Merged from dev1.x to rel1.x in preparation for release of version 0.1.0.
• Updated home.wiki, faq.wiki, and copyright.wiki to use rel1.x instead of ckout for links to embedded doc pages.

• Disabled the JavaScript-based search engine for the Doxygen-generated API documentation. Don't want to check-in all that stuff into the release branch.
• Changed the Doxygen header to use a relative path to get back to the Minx home page. Should be one less conflict when merging from dev1.x to rel1.x.
• Updated embedded doc paths in some of the wiki pages to use ckout rather than tip. These will have to replaced with rel1.x when releasing (i.e., always conflict when merging from dev to rel branch).

• Moved top-level COPYRIGHT file to an embedded wiki page.
• Updated all the sources to reflect above move.
• Added link to copyright page on Minx's home page.
• Updated TODO list to indicate what needs to happen on the Doxygen front at this time (viz., making the API docs look like the other Fossil pages).