my experience with ios app store reviews told me that Apple rules are idiotic, the review experience is poorly managed and they don't give a fuck about keeping developers happy now that iphones are massively successful (very different than when they were trying to court developers back in 2005ish.). I do not want to support Apple's policies on the app store and do not want to ever end up having a system that's as restricted as IOS (although if that happens I'd jump ship back to Linux so I guess my non app store purchases would become useless anyway)
PARENT REVIEWS QUIVER APP SOFTWARE
I can't backup a specific version of the software that I like (I've seen before software become overly bloated in future versions forcing me to keep using an older version) an app on the app store can be pulled out at any moment. Everyone pretty much covered it but basically I have multiple reasons why: Or to put it more generally, Undo works in Quiver pretty much the same way you'd expect it to work in any editor that can reload files that change on disk the undo history simply doesn't concern itself with undoing changes made outside of the app, and in most cases reloading the file from disk throws away undo history. I was able to get it to reload content without realizing it changed (by editing the note, then closing it in Quiver before it detected the change and reopening) and this didn't throw away the undo history, which seems like just a fairly simple bug. If you have a note open and you make an external change, the app will at some point notice the change and ask you if you want to reload if you say yes, it reloads from disk and throws away the undo history. The GUI does have an Undo, and it works exactly as you expect: it reverts changes made in the GUI app. > 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). From there it can be transformed into directory with FUSE for modification by standard tools (or for export purposes if the user wants to move away from our note type). Perhaps the right answer _is_ to put the whole note in a single JSON file. Losing this to make things easier on the user is no small deal. A JSON file has a both a single Unicode and byte representation, not so for directories. Directories are higher level than JSON files - we don't always have tools that can work with them. From the user's perspective this is simpler, they can now use normal tools to work on resources without having to manually extract and then reinsert the resource.īut from an overall perspective (which is probably more important), I think you're right that this is more complicated. Whether this adds to the complication of the project depends on your perspective. tiff file using normal command line tools.
The advantage of using a directory for your format is that it's easy to use preexisting tools on the contents of a note. this directory must contain a `content.json` file, a `meta.json` file, etc.) What would they use for the directory part? Is there such a thing as a schema for directories? (e.g. If HappenApps wanted to make a machine readable schema for qvnotebook and qvnote they could use JSON Schema for the JSON part. I have more thoughts on this (starting from a slightly different angle of how it relates to wikis) here. I'm also not sure whether it would be better to version the whole notebook or individual qvnotes. 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). This is another way to collaborate with your team." "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. Speaking of version control, Quiver's thoughts on this are interesting: 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. I particularly like that they keep the metadata and the content of the note separate. The more I read about different applications, the more I think you can't understand them unless you look at the underlying data format.
0 kommentar(er)
