u/driftwood_studio

Flutter multi-window support is actively being developed, but slowly. I'm not aware of any imminent indication that it's going to get moved to production-ready. Someday. Not today. Not soon.

My desktop application desperately needs this, but not just "another widow." The application is a document editor, so I basically need shared state across windows: the ability for app to know if a file is open in any existing window, ability to drag/drop content from one window to another, ability to move a document tab from window A to window B, etc.

So if I just needed another window for additional separate content, I'd go ahead and implement it using existing packages in pub.dev... but the issue is that these effectively boot a second (independent) flutter engine into a second rendering canvas (window), where each window is a silo with an extremely primitive "messaging" capability via the hostOS between windows. It's basically "boot a second copy of your application into a second window" not a single app controlling two windows.

My question: has anyone who's implemented using the existing packages had to deal with significant integration between "instances" in those windows? How did that go?

Alternatively, is anyone able to point me to details I missed as to plans/timelines for current multi-window support work being declared production ready and merged into flutter core?

[Note: sorry if this is a duplicate. I thought I'd posted it earlier today, but it appears nowhere in my post history -- some post error I didn't notice before closing the window maybe? Not sure.]

Edit: if it's not clear what I'm talking about with "single window implementation", there's a 20 second movie in the first "about this app" feature item on the beta signup page (https://fractaloutliner.app). Note that you should mostly ignore everything else. The beta signups and app availability are technically live, but but this is literally the first public mention of it I've made anywhere. The beta isn't really "public" yet.

Looking for comments on how people handle the management of large sets of video files related to projects, particularly projects that use private GitHub as the main repo.

There's a limit of 100gb on individual files in GitHub (so far as I know). I'm creating help and tutorial and marketing videos that often push at that restriction pretty hard.

Context: one-person "team". Generally clients I work for have essentially infinite resources with regard to repos, etc, but this is an individual project so I'm just now running into a problem I've always been able to ignore as "someone else's problem" that clients take care of.

Concern: Since I have raw footage, then edit and trim out to tighten, then export and then use that export to do titles and effects, export that... I end up with several versions of each. Checking in to a repo (even LFS) will keep every version if I revise or "do over" later. File count and total storage concerns.

Is Git LFS (Large File Storage) the obvious solution here? Does that work out well in people's experience?

Or am I better off keeping the various raw/trimmed/edited/titled versions of things local and handling backup myself?