![]() ![]() (This should happen exactly once, upon initial sync with api2.) This approach does have the aforementioned drawback of potentially obliterating changes made by other clients (as we can't sync using the modify stamp via api2 - the value still exists, but it's solely for sorting now). (Perhaps I shouldn't be so concerned about this, since the end result of my alternative approach below would essentially mimic the behavior of api1.)Īn alternative approach would be compare remote entries using the version and syncnum whenever these values exist in the local syncservice metadata but fall back to the modify timestamp when these values are absent. This would mean that any updates we send would overwrite what is on the server, as opposed to merging changes made by other clients. I'd like to hear others' feedback, but it seems to me that once api2 is introduced, we might want to be able to do one final sync using v1 to make sure we're 'clean', because prior to that, we won't have version/syncnum numbers to work with. To clarify my statement regarding migration: Yes, it's true that the two apis can co-exist, but without a migration path, the initial sync using api2 could be problematic. Reply to this email directly or view it on GitHub: In the meantime, I've got 3.2.6 and the required SDKs installed, and I've confirmed that nv is building cleanly for me, so I should be good-to-go. ![]() If I run into any design questions, I'll post them to this issue. I haven't researched enough to see whether we'll need to support a migration path, etc. I'll start pouring over the docs tomorrow and will create a branch on my fork to start working on this.Īs scrod has noted, this essentially entails a complete update to simplenote's v2 api. Just to update: scrod contacted me w/ the same info he gave to adec. Good luck and give me a shout if I can assist in any way. So when you upload a note, simplenote may return you a different (updated) version with your changes merged in if it had been updated elsewhere too.Īs it sounds like you're a seasoned Objective C developer you're like to get to something robust in a shorter timescale than me. However, there is a fair chunk of reengineering required around note saving as the v2 api supports merging. And I'd be curious to know if Tag Sync & Tag Management need to be developed hand-in-hand.įrom my investigations the v1 & v2 APIs can be used interchangeably, so migration isn't an issue. In the meantime I'm interested to hear if anyone thinks differently on this. I'll add my thoughts on tag management over at Issue 6. Inline-tagging already exists and I find it lacking. Syncing would remove the necessity of a hacked-together inline tagging system and/or the duplicated-effort of tagging in two programs. So, to sum up, I've contradicted half of my original request. It's also already a feature!įurthermore, as it stands now, invoking the tag field via a command isn't all that different from an inline keystroke, especially since there's a quick way to return to where you were typing, a quick tab. While a plain-text, inline tagging system (such as outlined by brief) is attractive, it doesn't accomplish any of the reasons to have a tagging feature in the first place. ![]() batch manipulation (tagging, retagging, exporting).visual clarity (separates tags from the text/title).This begs the question, why have a tag feature at all? I came up with three reasons: While waiting for sync I've been foregoing both NV's and SN's tag-features and using a plain-text, inline tagging system. You should only need to tag once (and I'd prefer to do it in NV). It's a duplicated effort to tag something in NV then again in SN or vice-versa. Notational Velocity's strength, note-filtering, is diminished when only a few notes contain most of the content in the database.I've thought tagging through more thoroughly and it boils down to two issues: tag sync and tag management. To make good use of NV, try to maintain one detail/fact/item per note. Reveal a note's content by using the up/down arrow keys to select it. To view or edit an existing note, type one or more words contained in its body or title. Edit the note as needed in the bottom pane. To create a new note, just type its title and press return. Correspondingly, selecting a note places its title in the search area (De-selecting the note restores the search terms). This selects the note and consequently displays it. If a note's title starts with the search term(s), that title will be "auto-completed". Likewise, if a search reveals nothing, one need simply press return to create a note with the appropriate title. I.e., in the process of entering the title for a new note, related notes appear below, letting users file information there if they choose. The same area is used both for creating notes and searching. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |