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@...1796...t> 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