81–90 of 264 posts
What exactly are the limitations on the free trial? All I am seeing is a green "Free Trial" banner in the bottom left. Is that it?
Earlier quoted context omitted.
You either make it look beautiful in one place, or make it look like ass in three places. Or, option C: You use Electron, like Slack.
I keep waiting for Slack to realize that they're a big enough company now that they can afford to make native apps that look and work better than the Electron version. I'd much rather have a real native app than a webpage inside some minimal window chrome. Different strokes for different folks I guess.
I happily use a github repo for taking my 'programmer notes'. Advantages: 1. Goes well with my programming workflow: Change/Commit/Push 2. Allows me to use my preferred editor 3. No need to worry about backups: Git push and you're done 4. Accessible from anywhere, even if you don't have your computer Is there anything that Quiver would offer that I wouldnt already have with a github repo?
Earlier quoted context omitted.
Can you explain why? Curious as this differs from most people I've seen.
For me: If I have a copy of the software I have it forever. With the app store I only have it as long as Apple permits. Using an older version of OS X can create issues as well, if the developer decides not to support it. If for some reason they remove it from the store I have to hope the developers make it available outside that channel. It's certainly happened with iOS apps. I'm open to being proven wrong though.
I've reviewed your request, but as much I would like to restore the item for you,
I won't be able to download "Aperture" to your account because the amount of time
that has passed since this purchase was made prohibits us from restoring it.
I really enjoyed starting this up out of the box. I love that I can export and that I can write in latex. I'm curious if I can set this up as a notebook for scientific simulations including plots etc.
Me too. The simplicity seems very refreshing. I've been keeping all of my main notes as separate Markdown documents for a long time. This will be a big help. I've been looking for an Evernote replacement that was more ahem concise. I've been using Evernote to help plan experiments and track papers, but it can't seem to get out of it's way... particularly when trying to share a notebook with collaborators. Honestly, t…
It's particularly nice in that if you are already in vim; ww will open the wiki index.
https://github.com/vimwiki/vimwiki
I've also been doing some note taking with :set filetype=journal in use with junegunn's nice syntax.
Earlier quoted context omitted.
Can you explain why? Curious as this differs from most people I've seen.
For me: If I have a copy of the software I have it forever. With the app store I only have it as long as Apple permits. Using an older version of OS X can create issues as well, if the developer decides not to support it. If for some reason they remove it from the store I have to hope the developers make it available outside that channel. It's certainly happened with iOS apps. I'm open to being proven wrong though.
Here's Quiver's: https://github.com/HappenApps/Quiver/wiki/Quiver-Data-Format
It's . . . really good. Like, _really_ good.
I particularly like that they keep the metadata and the content of the note separate. This is the same thing Camlistore does, and it's nice for version control because making changes to the metadata (adding new tags or whatever) doesn't show up as a content change.
Speaking of version control, Quiver's thoughts on this are interesting:
"Since Quiver stores all the data in plain JSON files, it’s easy to put the whole library (or a specific notebook) under version control. This is another way to collaborate with your team."
Leaving version control up to the user isn't the worst, but it does mean that it won't be straightforward to put an "undo" in the GUI (if the GUI already has undo somehow I'd like to hear how they do it).
I'm also not sure whether it would be better to version the whole notebook or individual qvnotes. I have more thoughts on this (starting from a slightly different angle of how it relates to wikis) here: http://housejeffries.com/page/4.
EDIT: Something just occurred to me. If HappenApps wanted to make a machine readable schema for qvnotebook and qvnote they could use JSON Schema for the JSON part. What would they use for the directory part? Is there such a thing as a schema for directories? (e.g. this directory must contain a `content.json` file, a `meta.json` file, etc.)
I happily use a github repo for taking my 'programmer notes'. Advantages: 1. Goes well with my programming workflow: Change/Commit/Push 2. Allows me to use my preferred editor 3. No need to worry about backups: Git push and you're done 4. Accessible from anywhere, even if you don't have your computer Is there anything that Quiver would offer that I wouldnt already have with a github repo?