-
Notifications
You must be signed in to change notification settings - Fork 432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto save #1028
Comments
You will need to add this in the main window and call at a regular interval the save project function You will need to use a QTimer: After that you need to add a settings for that. And after run:
This will generate the Python from the UI Next add the settings to the list of the settings: After add the link the settings edit to the setting pages: After that in the main windows you can access to the general settings via _self.settings |
Not really fond of a periodic "auto save" feature. I would prefer that GNS3 saves after key action like stopping nodes, before closing GNS3 etc. |
Other question should we drop the save and always save after each stop and redump the .gns3 at each topology modification. Like vSphere. For a desktop app the save is common, but for a web app generally it's auto save (See Google Docs). And if we start to have multiple users connected to the same topology the save as you will could be tricky. By the way we already know that if you don't save after adding a device you will have orphan files in your project. |
i regret the autosave of GNS3-legacy. Often, my students forget to save project before crash. When they reload project, they have an empty topology. |
What should trigger the save, a request on any server? A periodic save (e.g. every minute)? |
As GNS3-legacy ? we choose the periodicity.....? |
I propose that the .gns3 is save at each action that modify the topology. For the config perhaps we can do that differently. When we detect that the NVRAM of IOU and dynamips has change (It's the only case where we have to extract the config) and when it's change we extract the new config. It's possible on Linux with pyinotify. If we have that we have the same behavior of qemu based appliance. |
"modify the topology" does it include also move object on lab ? or just add/remove ? Save at each action does it be heavy if there are a lot of object ? |
I doubt that a .gns3 could be huge since it's contain only meta data about the position of stuff. |
We don't need an "auto save" feature because the new 2.0 will save as it goes. |
A user want to contribute that
https://gns3.com/discussions/gns3-auto-save
The text was updated successfully, but these errors were encountered: