So, here's an update for ya: Somehow or another the entire contents of my Inbox (not Inbox folder itself but everything under it including my entire speedbox structure) 'got' deleted. Pretty sure my assistant isn't daft enough to pull that dumdum and you can bet your a$$ it wasnt' me. Further insult to injury is that due to the constant F9 syncing she synced past the daily backups limit so can't recover from there. I did manage to find it in a daily two days back (not sure why it was two but the previous day didn't have it*) but those two days held a LOT of changes and I'm finding it very difficult to isolate the changes in each file. What I need is a way to merge the files and sus out duplicates.
So far my direction has been to export both files to mlo xml and open them in Beyond Compare. At first glance this seems like it should be easy enough but the files are don't automatically align correctly (I guess due to the sheer volume of changes i.e moves/deletes) and trying to manually align the start points of blocks is proving not just time consuming but quite difficult as there are what appear to be duplications of lines or even whole xml nodes throughout the file making figuring out the actual block starts to align on a hair-pulling experience. Please please please someone tell me there's a merge tool that does this. Or at least a deduplication tool that will find exact matches... I can merge both files wholesale if there's a way to sus out the thousands of duplicates that will arise after. So, MLO's 1990's sync logic strikes again. For something with so much raw power and flexibility, how can there still be so many holes in it's foundational basic underpinnings? Even as they announce a $25 price tag on the mobile apps (and still a license for each platform separately) to accompany a $60 desktop app but yet can't assure it won't eat data nor have the tools/facilities to repair such aggrievement when it happens is asinine. I (and I'm sure many others) are glad to see MLO-A v2 is out and I know they are still working on it and adding features but it's been said and here is more proof: the team cannot work on just one platform at a time. MLO-A development cannot be to the detriment of the desktop or even the iToy branch. Development on all three must happen in parallel. Now that android has been refreshed to "match" the i branch they should be focusing on fixing bugs and missing foundations across the entire platform instead of wasting dev cycles with the cosmetic refresh they want to call MLO 5. Andrey, I hope you're listening. Releasing MLO 5 and forcing users to pay an upgrade even as 4 is still full of holes will alienate a large core of your usership. The cosmetics of 5 will not motivate anyone to upgrade and frankly I think it's proven out that from mlo-a that halting dev and bug fixes on a branch to favor a new major release did not garner you a lot of goodwill. I'm urging you to consider this factor heavily. You need the core users to evangelize and talk highly about MLO. Everywhere you go on the interwebz that MLO is discussed, it's rarely if ever a glowing review. It's always a tempered discussion of (I'm paraphrasing here:) "I tried it, I hated it, but I went back because it's the only thing so powerful. But it's clunky and cluttered and has it's issues but if you need that power you'll have to learn to deal with it." THAT my friend is NOT glowing endorsement. That's a statement of pure compromise at best and a statement of defeat and surrender at worst. This is NOT how MLO should be discussed. This is NOT how mlo should be experienced. This is NOT how you want to be known. Now someone dear g-d please, tell me an easier way to merge/dedupe my .ml files!! * From the sync logs I can see exactly date and time that the deletes happened, but unfortunately can't tell which side initiated the deletes nor how the deletes came to pass - ie was it the delete key or as a result of the conflict resolution dialog - so can't tell if one of us is responsible or if it was HAL that screwed up or just a glitch in The Matrix On Sunday, August 30, 2015 at 6:35:10 PM UTC-4, Joel Azaria wrote: > > Thanks Dwight, Christoph. > > I ended up sharing one branch to a separate file which her machine then > syncs that file as well. With the F9 syncing it kind of has a 90's feel to > it - like I'm constantly saving a wordperfect document. It works in so far > as it functions and syncs but it's more than just a *little* cumbersome, > esp. for the year 2015. > > There are ways I could suggest to fix this but it seems the real way > forward is for cloud sync to support syncing branches (which it presently > does not.) To be an actual solution however it also has to adopt > push-based syncing (as soon as there's a change, it should be queued to > push) and a more intelligent automatic record merge /conflict resolution. > > This is an area that requires some solid attention and doesn't seem to be > getting any. Either MLO is an end to end system or it's just a bunch of > loosely related but in-cohesive parts. > Cloud sync was pitched as a solver of problems. So far it doesn't appear > to have done much of that and MLO will not truly be an end to end system > until it does. > > > Thanks for your advice guys. Let's see how this works in practice over > the next few weeks.. > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/528fc8d2-3736-4e5f-abd7-222b1c43f447%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
