Rebuilding InfinitePIP around independent floating windows

The next day, InfinitePIP moved to an Electron implementation. The first rewrite included source selection and a floating PiP with opacity, zoom, pan and always-on-top controls. That gave the project a more direct foundation for managing desktop capture and several independent windows.

A useful example is keeping a small application panel visible while the rest of that application stays behind your main work. You can adjust the view instead of resizing the original app until its interface becomes awkward. Zoom and pan let you decide which part deserves the space on your screen.

The December 24 follow-up added a live region-crop preview and aspect-ratio locking. Previewing the crop is a big usability improvement: we can see what we're selecting before creating another floating window. The proportions can stay consistent while the view changes size.

Per-PiP management followed the same evening. Once there is more than one floating view, the main app needs to help you find, adjust and close the correct one. A list of individual PiPs makes much more sense than assuming the last-created window is always the one you want.

The project was then reorganized and its documentation updated, with additional README cleanup on December 26. Those commits describe the rewrite and interface work; they aren't a platform-by-platform release acceptance record.

This is the point in the history where the current app's shape becomes recognizable: choose a source, frame the useful area, and manage the floating result separately. The later dashboard and packaging work build on that workflow rather than changing what InfinitePIP is for.