I was wondering whether inkscape has autosave, of not I would be willing to work on it, (under a mentor) in upcoming winter break, since I feel autosave is a highly useful feature for vector editors, because we tend to forget to his ctrl+s so often :(
+1 for the addition of auto-save. -- Riccardo Bernardini Tel : +39-0432-55-8271 skype : bernardini.riccardo LinkedIn : https://www.linkedin.com/in/riccardobernardini
________________________________________ Da: Aditya Sher <adityasher2000@...400...> Inviato: lunedì 3 dicembre 2018 16:58 A: inkscape-devel Oggetto: [Inkscape-devel] Autosave for inkscape
I was wondering whether inkscape has autosave, of not I would be willing to work on it, (under a mentor) in upcoming winter break, since I feel autosave is a highly useful feature for vector editors, because we tend to forget to his ctrl+s so often :(
check out menu->Edit->Preferences->Input Output->Autosave
-- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
Autosave is going to be enabled by default in Inkscape 1.0, so new users shouldn't have to battle with lost data anymore.
Maren
Am 03.12.18 um 17:16 schrieb alvinpenner:
check out menu->Edit->Preferences->Input Output->Autosave
-- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Bryce
On Mon, Dec 03, 2018 at 05:58:13PM +0100, Maren Hachmann wrote:
Autosave is going to be enabled by default in Inkscape 1.0, so new users shouldn't have to battle with lost data anymore.
Maren
Am 03.12.18 um 17:16 schrieb alvinpenner:
check out menu->Edit->Preferences->Input Output->Autosave
-- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, Dec 3, 2018 at 6:21 PM Bryce Harrington <bryce@...961...> wrote:
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Bryce
Hi!
Yes, the testing would be very welcome. And being an avid user of that feature I have some additional ideas how to improve it. For example having a widget to select directory where autosaves would land would be something I'd appreciate a lot. I put my autosaves on a different location than provided default. On a different hard drive even.
The second thing that falls on my mind is making directories named by dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
Cheers, Vladimir
Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape?
| Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
| This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? i don't know about others, but "the cloud" is not my cup of tea. having files of any kind in storage that is not close by in a physical state, that lounge about on "someone else's server" makes me nervous. what happens if the internet goes down . . . . again (it's happened twice)? what happens if you lose electrical power and you have no internet for days, weeks, months? i really don't see the point of allowing someone else to have that kind of control of my intellectual property. i may seem old school and archaic, but the attitude of image makers today is what has devalued what we produce with these "free" tools.
think about what recently happened with the request for assistance to take inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
but back to the main point of integrating git revisioning with inkscape. i too began naming files in a dated folder using year-month-date-file name. as a "university" trained artist (i was a photographer for 12 years and have worked in broadcast and print [magazines and newspapers] before returning to school), i learned to ask, "what if i did this instead". when you work in analog, you must start over; when you work in digital, you do a "file save as", add a letter or number or whatever your naming convention is and save to your chosen folder. all of your versions are side by side on *your *hard drive on *your *computer and you can back it up to whatever media you choose and you don't have to be concerned about not having direct access to your images.
that said, my time is up. i thank you for yours.
good luck resolving the auto save question. i think it's a wonderful idea. whether or not you devels institute it as default or not.
cheers
On Tue, Dec 4, 2018 at 2:01 PM Chris Tooley <euxneks@...400...> wrote:
Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am 06.12.18 um 03:14 schrieb Dwain Alford:
| Regarding specifically:
The second thing that falls on my mind is making directories named by dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...| This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? i don't know about others, but "the cloud" is not my cup of tea.
- I think there has been a misunderstanding. Local git repositories work great for this kind of thing. I have my website code locally, in version control. This remark about git was not about where you store your data, but how you can do versioning efficiently, with using little disk space, and a searchable history.
Auto-save exists, and it works. The only thing that changed was that it is now enabled by default, if you install Inkscape freshly, or start a new preferences file.
In my personal view, the feature is not a replacement for version control, but a safety net in case of crashes or if I make changes to my file that end up being really bad within one session, and I need to go back to a previous version. This is due to it saving at timed intervals, which don't relate to changes in the document.
It could be turned into version control, but there are other ways to do that that already exist, are more efficient, and can be used more purposefully (i.e. not save at timed intervals, but save when a certain step has been made in your drawing, and also add a comment that lets you see right away what you changed).
I do understand though, that this way of version control is intimidating, and can seem (and be!) overkill. It all depends on what one feels comfortable with, and how important it is to oneself to keep intermediate versions of a file etc.
Maren
having files of any kind in storage that is not close by in a physical state, that lounge about on "someone else's server" makes me nervous. what happens if the internet goes down . . . . again (it's happened twice)? what happens if you lose electrical power and you have no internet for days, weeks, months? i really don't see the point of allowing someone else to have that kind of control of my intellectual property. i may seem old school and archaic, but the attitude of image makers today is what has devalued what we produce with these "free" tools.
think about what recently happened with the request for assistance to take inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
but back to the main point of integrating git revisioning with inkscape. i too began naming files in a dated folder using year-month-date-file name. as a "university" trained artist (i was a photographer for 12 years and have worked in broadcast and print [magazines and newspapers] before returning to school), i learned to ask, "what if i did this instead". when you work in analog, you must start over; when you work in digital, you do a "file save as", add a letter or number or whatever your naming convention is and save to your chosen folder. all of your versions are side by side on *your *hard drive on *your *computer and you can back it up to whatever media you choose and you don't have to be concerned about not having direct access to your images.
that said, my time is up. i thank you for yours.
good luck resolving the auto save question. i think it's a wonderful idea. whether or not you devels institute it as default or not.
cheers
On Tue, Dec 4, 2018 at 2:01 PM Chris Tooley <euxneks@...400... mailto:euxneks@...400...> wrote:
Regarding specifically: The second thing that falls on my mind is making directories named by dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file... This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
thanks for the git repository information update. i didn't realize there was a version that a user can install locally. i think i may have to look into this and determine if it's overkill or not for my purposes. i appreciate all who responded to my comments. i appreciate even more the instructional kindness of the replies.
dwain
On Wed, Dec 5, 2018 at 8:36 PM maren via Inkscape-devel < inkscape-devel@lists.sourceforge.net> wrote:
Am 06.12.18 um 03:14 schrieb Dwain Alford:
| Regarding specifically:
The second thing that falls on my mind is making directories named by dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...| This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with
inkscape?
i don't know about others, but "the cloud" is not my cup of tea.
- I think there has been a misunderstanding. Local git repositories work
great for this kind of thing. I have my website code locally, in version control. This remark about git was not about where you store your data, but how you can do versioning efficiently, with using little disk space, and a searchable history.
Auto-save exists, and it works. The only thing that changed was that it is now enabled by default, if you install Inkscape freshly, or start a new preferences file.
In my personal view, the feature is not a replacement for version control, but a safety net in case of crashes or if I make changes to my file that end up being really bad within one session, and I need to go back to a previous version. This is due to it saving at timed intervals, which don't relate to changes in the document.
It could be turned into version control, but there are other ways to do that that already exist, are more efficient, and can be used more purposefully (i.e. not save at timed intervals, but save when a certain step has been made in your drawing, and also add a comment that lets you see right away what you changed).
I do understand though, that this way of version control is intimidating, and can seem (and be!) overkill. It all depends on what one feels comfortable with, and how important it is to oneself to keep intermediate versions of a file etc.
Maren
having files of any kind in storage that is not close by in a physical state, that lounge about on "someone else's server" makes me nervous. what happens if the internet goes down . . . . again (it's happened twice)? what happens if you lose electrical power and you have no internet for days, weeks, months? i really don't see the point of allowing someone else to have that kind of control of my intellectual property. i may seem old school and archaic, but the attitude of image makers today is what has devalued what we produce with these "free" tools.
think about what recently happened with the request for assistance to take inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
but back to the main point of integrating git revisioning with inkscape. i too began naming files in a dated folder using year-month-date-file name. as a "university" trained artist (i was a photographer for 12 years and have worked in broadcast and print [magazines and newspapers] before returning to school), i learned to ask, "what if i did this instead". when you work in analog, you must start over; when you work in digital, you do a "file save as", add a letter or number or whatever your naming convention is and save to your chosen folder. all of your versions are side by side on *your *hard drive on *your *computer and you can back it up to whatever media you choose and you don't have to be concerned about not having direct access to your images.
that said, my time is up. i thank you for yours.
good luck resolving the auto save question. i think it's a wonderful idea. whether or not you devels institute it as default or not.
cheers
On Tue, Dec 4, 2018 at 2:01 PM Chris Tooley <euxneks@...400... mailto:euxneks@...400...> wrote:
Regarding specifically: The second thing that falls on my mind is making directories named by dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even"/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg".
At times I did crave for being able to go back in time with finding some WIP versions of a file... This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Wed, Dec 05, 2018 at 08:14:38PM -0600, Dwain Alford wrote:
| Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
| This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape?
i don't know about others, but "the cloud" is not my cup of tea. having files of any kind in storage that is not close by in a physical state, that lounge about on "someone else's server" makes me nervous.
As Maren already pointed out, git by itself is not a cloud technology. At it's heart it's just version control.
git is quite powerful, and would provide a far more sophisticated way to manage change history for a document beyond a simple linear history that date-based saves provide. However, the greater flexibility means it may introduce complexity, potentially being a bit overkill.
That said, I agree it would make an excellent future project for someone to undertake experimentally. There are almost certainly some interesting use cases for it. Chris or others interested in this concept, if you'd like, please add it to our projects page in wiki:
http://wiki.inkscape.org/wiki/index.php/Projects
think about what recently happened with the request for assistance to take inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
Fwiw, I am certain none of us here would ever allow such a thing to happen.
Bryce
On Wed, 2018-12-05 at 20:16 -0800, Bryce Harrington wrote:
think about what recently happened with the request for assistance to take inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
Fwiw, I am certain none of us here would ever allow such a thing to happen.
If anyone's been tracking the work the Software Freedom Conservancy have been doing on compliance with Tesla motor company, you'll see we have an organisation that is keen and persistent in ensuring licensing compliance.
I don't know how those guys keep doing all that they do with so few people. But I like it.
Best Regards, Martin Owens
Hello Bryce!
git is quite powerful, and would provide a far more sophisticated way to
manage change history for a document beyond a simple linear history that date-based saves provide. However, the greater flexibility means it may introduce complexity, potentially being a bit overkill.
I imagine it would be something that could be "hiding in the back" where a user can take full advantage of it if they want, but for the most part would only keep a continuous running log of changes between each save and tags if the user wants.
That said, I agree it would make an excellent future project for someone to undertake experimentally. There are almost certainly some interesting use cases for it. Chris or others interested in this concept, if you'd like, please add it to our projects page in wiki:
I do not have an account on the project wiki. I suspect I might only use it for this one entry but I do use Inkscape regularly and if I can contribute on the wiki in other ways too I'd be happy to have an account.
Chris
Am 06.12.18 um 19:28 schrieb Chris Tooley:
Hello Bryce!
git is quite powerful, and would provide a far more sophisticated way to manage change history for a document beyond a simple linear history that date-based saves provide. However, the greater flexibility means it may introduce complexity, potentially being a bit overkill.I imagine it would be something that could be "hiding in the back" where a user can take full advantage of it if they want, but for the most part would only keep a continuous running log of changes between each save and tags if the user wants.
That said, I agree it would make an excellent future project for someone to undertake experimentally. There are almost certainly some interesting use cases for it. Chris or others interested in this concept, if you'd like, please add it to our projects page in wiki: http://wiki.inkscape.org/wiki/index.php/ProjectsI do not have an account on the project wiki. I suspect I might only use it for this one entry but I do use Inkscape regularly and if I can contribute on the wiki in other ways too I'd be happy to have an account.
Chris
What user name would you like for your account? There's always something to do ;-)
Maren
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Branched this off to its own email thread
That said, I agree it would make an excellent future project for someone
to undertake experimentally. There are almost certainly some interesting use cases for it. Chris or others interested in this concept, if you'd like, please add it to our projects page in wiki:
Maren gave me a wiki account (Thanks Maren!), and I've added a git project suggestion: http://wiki.inkscape.org/wiki/index.php/Projects#Git_Integration
I think git integration would be a pretty cool thing. If we think of inkscape as a "vector editor" in the same way as VSCode is a "Code Editor", git is a natural addition.
We can look at code editors like vscode's built in git integration to get an idea of what it could be like - though some might think that's too "technical" for graphical designers, I think versioning can be naturally translated conceptually for most people. Or, for example, we could have the history represented as a path with dots along it, branching as needed, which the user can select and "view".
The main problem I see with this right now is portability - how is the git history maintained with the file if you send it to someone, or shared on a computer?
Anyway, might be a fun project for GSoC or otherwise.
-Chris
Regarding :
think about what recently happened with the request for assistance to take
inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
You will be happy to know that the license which Inkscape is provided under prevents this from happening. A company cannot legally release a proprietary version of Inkscape. Period.
The worst they could do is use their own proprietary code in Inkscape internally within their own company, but as soon as they want to sell it or distribute it to the pu lic, they MUST provide the source code for it, and it must be provided under the same GPL as Inkscape proper. They would be legally liable for damages to the Inkscape project should they fail to comply with the GPL.
This effectively protects the work of everyone who contributed to make Inkscape free for everyone, so the only thing that could kill it is if everyone loses interest in developing Inkscape... forever. :)
This is a very unlikely scenario, so I wouldn't lose sleep over it. ;)
Hope it helps! -C
but back to the main point of integrating git revisioning with inkscape. i too began naming files in a dated folder using year-month-date-file name. as a "university" trained artist (i was a photographer for 12 years and have worked in broadcast and print [magazines and newspapers] before returning to school), i learned to ask, "what if i did this instead". when you work in analog, you must start over; when you work in digital, you do a "file save as", add a letter or number or whatever your naming convention is and save to your chosen folder. all of your versions are side by side on *your *hard drive on *your *computer and you can back it up to whatever media you choose and you don't have to be concerned about not having direct access to your images.
that said, my time is up. i thank you for yours.
good luck resolving the auto save question. i think it's a wonderful idea. whether or not you devels institute it as default or not.
cheers
On Tue, Dec 4, 2018 at 2:01 PM Chris Tooley <euxneks@...400...> wrote:
Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
thanks for the additional information that fill in gaps regarding my understanding of the gpl license. yes, this helps tremendously.
dwain
On Thu, Dec 6, 2018 at 7:38 AM C R <cajhne@...400...> wrote:
Regarding :
think about what recently happened with the request for assistance to take
inkscape and produce a proprietary software program based on the open source code produced by the programmers that have dedicated their lives to produce and continue to make better software that is freely given. i saw the possibility of losing inkscape and the years of hard, dedicated work in a flash.
You will be happy to know that the license which Inkscape is provided under prevents this from happening. A company cannot legally release a proprietary version of Inkscape. Period.
The worst they could do is use their own proprietary code in Inkscape internally within their own company, but as soon as they want to sell it or distribute it to the pu lic, they MUST provide the source code for it, and it must be provided under the same GPL as Inkscape proper. They would be legally liable for damages to the Inkscape project should they fail to comply with the GPL.
This effectively protects the work of everyone who contributed to make Inkscape free for everyone, so the only thing that could kill it is if everyone loses interest in developing Inkscape... forever. :)
This is a very unlikely scenario, so I wouldn't lose sleep over it. ;)
Hope it helps! -C
but back to the main point of integrating git revisioning with inkscape. i too began naming files in a dated folder using year-month-date-file name. as a "university" trained artist (i was a photographer for 12 years and have worked in broadcast and print [magazines and newspapers] before returning to school), i learned to ask, "what if i did this instead". when you work in analog, you must start over; when you work in digital, you do a "file save as", add a letter or number or whatever your naming convention is and save to your chosen folder. all of your versions are side by side on *your *hard drive on *your *computer and you can back it up to whatever media you choose and you don't have to be concerned about not having direct access to your images.
that said, my time is up. i thank you for yours.
good luck resolving the auto save question. i think it's a wonderful idea. whether or not you devels institute it as default or not.
cheers
On Tue, Dec 4, 2018 at 2:01 PM Chris Tooley <euxneks@...400...> wrote:
Regarding specifically:
The second thing that falls on my mind is making directories named by
dates. For example: 04-12-2018, 05-12-2018 etc. Or maybe even "/home/$USER/selected_directory/$YEAR/$MONTH/$DATE/filename*.svg". At times I did crave for being able to go back in time with finding some WIP versions of a file...
This sounds like the perfect reason to use a versioning tool like git. Perhaps a future project is integrating git revisioning with inkscape? _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thank you for the help everyone. Yes I will surely enable it and report bugs as I can thank you very much, it will definitely save me from a lot of frustration, I will surely contribute back by reporting bugs.
On Mon, Dec 3, 2018, 10:51 PM Bryce Harrington <bryce@...961... wrote:
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Bryce
On Mon, Dec 03, 2018 at 05:58:13PM +0100, Maren Hachmann wrote:
Autosave is going to be enabled by default in Inkscape 1.0, so new users shouldn't have to battle with lost data anymore.
Maren
Am 03.12.18 um 17:16 schrieb alvinpenner:
check out menu->Edit->Preferences->Input Output->Autosave
-- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am Montag, 3. Dezember 2018, 18:19:15 CET schrieb Bryce Harrington:
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Please, if something like that gets enabled by default, make sure to tell us users so we can turn it off. At least I make heavy use of editing files, exporting to PDF and then closing without saving. Autosave would destroy my work on a regular basis.
Bryce
Tobias
[...]
Considering that Auto saving would be an ongoing feature, I would make it a visible button or indication in the interface. Something that you could click on to turn on or off and one who's icon could show how much time there is until the next autosave in a sort of small indicator countdown.
Obvious defaults in the settings interface, etc etc. for which to have for new documents.
Best Regards, Martin Owens
On Thu, 2018-12-06 at 19:57 +0100, Tobias Ellinghaus wrote:
Am Montag, 3. Dezember 2018, 18:19:15 CET schrieb Bryce Harrington:
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Please, if something like that gets enabled by default, make sure to tell us users so we can turn it off. At least I make heavy use of editing files, exporting to PDF and then closing without saving. Autosave would destroy my work on a regular basis.
Bryce
Tobias
[...] _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 6 Dec 2018, 19:58 Tobias Ellinghaus <houz@...173...> wrote:
Am Montag, 3. Dezember 2018, 18:19:15 CET schrieb Bryce Harrington:
Aditya, perhaps a great use of your time over the break would be to enable this feature and test it heavily looking for bugs or idiosyncracies, and send patches to make it more robust?
Maren, are there reasons why it's not been enabled by default in the master trunk? If so, those might be key things to focus testing/bugfixing work on. This will be an important feature for a lot of people and they'll be glad it's going to be available in 1.0.
Please, if something like that gets enabled by default, make sure to tell us users so we can turn it off. At least I make heavy use of editing files, exporting to PDF and then closing without saving. Autosave would destroy my work on a regular basis.
How do you mean that? Autosave isn't like automatically hitting "Save" button.
Autosaves are saved to a different location and it all happens without overwriting or anything similar. They are just precaution measure of you want to go "back in time" and find where you made a mistake.
Vladimir
Bryce
Tobias
[...]_______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (12)
-
unknown＠example.com -
Aditya Sher -
alvinpenner -
Bryce Harrington -
C R -
Chris Tooley -
Dwain Alford -
maren -
Maren Hachmann -
Riccardo Bernardini -
Tobias Ellinghaus -
Vladimir Savic