Indigrid

Posted by Mark Nevarrik
Jan 23, 2018 at 07:18 PM

shatteredmindofbob wrote:

>It’s not so much about a separate view, but a completely separate
>document. If say, I want to flesh out a completely new idea, I’d want to
>be able to quickly begin from scratch, something that isn’t connected to
>anything else.
>

I understand now that you put it that way. I didn’t see before that not having everything connected could be desirable. I will look into having different databases that are siloed from each other, like files.

>Plain text is fine for import/export, you’d just need to ability to even
>save to a .txt file, without having to rely on copying and pasting.
>

I had a great feature idea from someone where Indigrid “watches” external text files for changes and then reloads the changes under a designated node—and conversely exports any changes under that node back out to the text file. So that is coming, and could also double as an import/export. This also gives a little bit of mobility if you put those files on Dropbox.

bobmclain wrote:
shatteredmindofbob wrote:
> >> I also like the idea of antisocial, neurotic and introverted software
> >What’s to like about that kind of software? Sounds more like an art
>project…
>

Don’t forget the website also mentions pretentious software :) And it is an art project :)

“It is the function of art to renew our perception. What we are familiar with we cease to see.” — Anaïs Nin

>For Indigrid, I’d work first on making it *not* crash so frequently, and
>maybe then on a proper export (not just copy and paste).

Bob would you mind sending me the crash files generated from the crashes you get please? They are in %appdata%/indigrid/crashes

I totally get that it is a hassle—I’m worried that perhaps because of previous versions that somehow the state got bad.

Either way, I hear loud and clear now that export to a file is important. Thank you for continuing to help me out with constructive criticism.