Add “Save to Local” Button to Prevent Losing Work

[morningstarxcdcode]

Title:
Add “Save to Local” Button to Prevent Losing Work

Description:
Hey everyone! 👋

So, after seeing that people were worried about possibly losing their work because saving to Google Drive isn’t super reliable in AI Studio, I wanted to help out. I looked through the code and realized that the app itself doesn’t control Drive stuff—that’s handled somewhere else. Since I couldn’t fix Google Drive, I decided to make it way easier (and safer) to save your own progress!

Here’s what I changed for each applet:

• Maps Applet:
  Added a “Save to Local” button you can click whenever. It saves the map’s location and its caption into a small text file—so you can always keep a copy on your computer and not stress about losing your spot.

• Spatial Applet:
  There’s a new “Save to Local” button up top. When you click it, it grabs literally everything in your session—images, boxes, lines, whatever—and saves it as a JSON file. So you’ve got a full backup and can pick up where you left off even if something breaks.

• Video Applet:
  I added the same kind of button next to “Generate.” It saves all your session info (video link, all timecodes, your notes, etc.) into a JSON file, so your video work is safe.

I know it doesn’t fix Google Drive itself, but at least now you won’t lose your progress—even if Drive lets you down. Hope this makes things feel way safer and takes some stress off. If there’s anything else I can do to help with saving or backing up, just let me know!

Thanks for checking it out!

Let me know if you want it even more informal, but this keeps it helpful, positive, and clear with a good “young dev” vibe.

for this issues :

#32

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @morningstarxcdcode, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses user concerns about data loss by implementing a 'Save to Local' feature across the Maps, Spatial, and Video applets. This allows users to download their current session's progress directly to their local machine, providing a reliable backup mechanism independent of cloud storage solutions like Google Drive.

Highlights

• Maps Applet - Local Saving: Added a 'Save to Local' button to the Maps Applet. Clicking this button saves the current map's location (iframe source) and its caption into a plain text file (map-data.txt) for local download.
• Spatial Applet - Local Saving: Integrated a 'Save to Local' button into the Spatial Applet's top bar. This button triggers a function that collects the entire session state, including the image source, 2D/3D bounding boxes, points, lines, and detection type, and saves it as a JSON file (spatial-data.json) for local download.
• Video Applet - Local Saving: Introduced a 'Save to Local' button next to the 'Generate' button in the Video Applet. This functionality captures the current video URL, timecode list, selected modes, custom prompts, and chart details, then saves this comprehensive session data as a JSON file (video-data.json) for local download.
• New Utility Hooks: For the Spatial Applet, a new useSaveState hook was created in spatial/src/hooks.tsx to encapsulate the logic for gathering and saving the applet's state, promoting reusability and cleaner component code.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a "Save to Local" feature across the maps, spatial, and video applets to prevent data loss. The implementation is functional, and this review suggests improvements to the code's robustness, maintainability, and performance. Specifically, it addresses a potential runtime error in the maps applet and highlights opportunities to reduce code duplication and apply React optimizations like useCallback.