The first is that the download directory issue *should* be fixed. Which is a shame really, as I'm a huge Zotero fan.ġ.1.7 is out now. As a programmer and wannabie scientist with a thesis to finish, I can't devote as much time per week on ZotDroid as some folks might want. In the meantime, I need to refactor the code base and add more tests to cover what we have.Īs to an iOS version - that's possibly even harder to do as Apple is even more walled off than Android! There's very little, if any, money in app development sadly. I think I'll start a 'closed beta' for these who want a say in the new features, before I put the actual releases out. Regardless, I need to think a bit more about the approach.Īll of these things are do-able but I need a better approach going ahead. I think I might take these checks out and leave it to the user. So often Android would complain, or just not save once it had downloaded. I had an awful lot of problems with the directory setting. I'll need to add a lot of support for that. I can very well imagine lots of partial or failed syncs due to network errors and all the rest. I'm hoping most of these are gone.Ībstracts, paths and download-all-the-things are easy to conceive in code, but will need significant testing, and a lot of code to make them robust. Both of these were major changes that caused a lot of problems. I had never considered groups at all, nor had I noticed the problems with the OAUTH. I think it's safe to say that ZotDroid has changed *a lot* since I first envisioned it and I need to take some time to iron out the bugs, add a bit of polish and speed things up before I add new features. Hopefully this makes browsing collections a little faster for folks. This is a minor fix that improves on the speed issue and fixes a minor webdav bug I found.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |