Fix Flutter Dependencies & UI Visibility (macOS)

[NandaSBinod]

Summary

This PR updates and fixes Flutter dependencies for the macOS version of the app, resolving issues that previously prevented the UI from rendering. It supersedes #65, which attempted a similar fix but is now outdated. While the UI is now visible, core functionality remains broken.

Changes

• Updated Flutter dependencies to resolve macOS build issues
• Fixed UI rendering (previously, the app did not display any UI) by linking my fork of navigation_rail with necessary fixes

Next Steps

The core functionality is still broken and will be addressed in a follow-up PR.

[techno-disaster]

Can you make a PR of the navigation rail library as well?

PS: We should move that to the org at some point. I'll try to do it later!

[NandaSBinod]

Done! Should I go ahead and push the functionality fixes? Newer versions of ccextractor use two hyphens in command line arguments like --autoprogram, which is causing the app to crash when processing video files.

[techno-disaster]

Done! Should I go ahead and push the functionality fixes? Newer versions of ccextractor use two hyphens in command line arguments like --autoprogram, which is causing the app to crash when processing video files.

Can you link the navigation rail PR? Also the ccx binary changes make sense, just make sure it's also compatible with older versions

[NandaSBinod]

techno-disaster/navigation_rail#4

I was thinking of updating the included binary ./ccextractorwinfull.exe to ensure compatibility across Windows, macOS, and Linux. Would you like me to dynamically detect the CCExtractor version and use the appropriate parameters based on that?

[techno-disaster]

dynamically detect the CCExtractor version

yep that makes the most sense. merged the nav rail PR

[techno-disaster]

superseeded by #68 and we should use the flutter nav rail instead of the forked package. maybe someone from here or @hrideshmg can take it over. thank you!