Jump to content

andreas.w

Member
  • Posts

    33
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by andreas.w

  1. I just released version 2.0.4 with a bug fix for an issue that would occur if you had at least one collection in Raindrop.io that did not have an icon manually set for it, so if you happened to turn into this problem you should now be able to have everything working by downloading the updated version here: https://github.com/westerlind/alfred-raindrop-search/releases
  2. I made another small update. Version 2.0.2 adds the ability to directly open Raindrop.io's permanent copy of a bookmark by holding shift and pressing enter while a bookmark is selected in the list. This feature requires a Raindrop.io Pro subscription to work Now I will probably be more quiet for a while, if there are not a bunch of bugs showing up or something like that
  3. @xurc I looked a little more at this, thinking that it would really be quite strange if there isn't a better method for Alfred workflows to send their traffic through a proxy, and it turned out that there is a much simpler way to do it! You can just go to the Alfred preferences, and to Advanced, and enable "Use macOS http proxy settings for scripts". This just isn't enable by default, and I had totally missed it's existence because of it.
  4. Hi @xurc During the development of this I sent all requests to Raindrop.io through a proxy to be able to easier see whats going on with the requests and fix issues that way, so I know that it can work with a proxy (at least the one I used, but that's for development, not really to be used as an actual proxy) The trick I did to get that proxy to work was to use the fact that Go applications by default looks for the environment variable https_proxy (and http_proxy, but that's not relevant here as all traffic is https). You can manually specify this environment variable before calling the raindrop_alfred application, and it will then send traffic through that proxy. For example, if you look at the workflow in Alfred, and double click the green object up in the left corner that specify "r" at the top (for which key you use to access it), you can change this line: ./raindrop_alfred search --query="{query}" to this: https_proxy=127.0.0.1:1080 ./raindrop_alfred search --query="{query}" That will change that part of the workflow to send traffic through the proxy, but for it to work everywhere, you will have to do the same in all other places where ./raindrop_alfred is called around the workflow (most of the object's that either say Script Filter or Run Script at the buttom). The other green object with "ra" at the top has a bunch of AppleScript in it, and it calls ./raindrop_alfred in several places. For this possible fix to work there, I would suggest to copy all the AppleScript in there, put it in a text editor, use the find and replace-feature to replace all instances of "./raindrop_alfred" with "https_proxy=127.0.0.1:1080 ./raindrop_alfred", and then copy it all and paste in Alfred again. I'm sure that there is probably a way to set the https_proxy environment variable globally for your whole system in a way that Alfred and in turn this workflow manages to pick it up too, and than it should just work, but I haven't tried to do that, and I know that scripts that are run in a workflow do not pick up environment variables that I have set in my zsh or bash configuration for example, so it is possible that this is quite hard to do. Maybe someone else here knows how to do that? In the mean time the solution above might do the trick. I might possibly implement support for this eventually too, but no promises on that.
  5. Hi @xurc I just added the ability to show more information if the authentication fails, so try downloading version 2.0.1 and see if it might help to at least point out where the issue is. Download at GitHub
  6. Just released version 2.0! This is something that I realized maybe a year ago that I wanted to do eventually, to rewrite all the PHP and Python (which is almost all of what this workflow used to be) in a way that will make it work without external dependencies when Apple stops providing PHP and Python with the OS (which has been know for a while that they will eventually stop doing) With macOS 12 Monterey, which will be released possibly as soon as the coming week (but more likely next month), PHP will be gone, which means that this workflow would not function if you did not manually install PHP yourself, and while I did some changes in version 1.7 recently to make the workflow function with a version of PHP that you have installed yourself, I do really not like the idea of requiring PHP to be manually installed for my workflow to function, and it is also just a matter of time before Python goes away as well. Likely next year. So I have rewritten everything that was written in PHP and Python in Go instead. Which means that almost everything is entirely rewritten (there is just a bit of AppleScript that has only changed a little) Go is a compiled programming language, and it does not require any runtime to be installed to function once the code is compiled. This means that the workflow is not dependent on Apple to provide support for something like PHP or Python in macOS anymore, and Go also has the added benefit of being faster than a scripting language like PHP. Version 2.0 does not really look or behave as different as the version bump might indicate, but almost everything has changed underneath to make this a better workflow. Rewritten in Go, so no dependency on PHP or Python anymore. This is important, as Apple is removing PHP from macOS 12 Monterey, and will also remove Python from macOS in the future. It's faster! Running the backend of the workflow as a compiled binary (Go) instead of a script (PHP) makes it faster, and it is also compiled as a universal binary, so it's running natively on both Apple Silicon and Intel Macs, but there are also some other changes that helps to make it faster and you will probably notice the difference if you used the old version before. Less risk for unexpected behavior that leads to bugs, both because it can't behave different depending on which PHP or Python version you have anymore, but also because it now for example uses more reliable ways to keep track of information while navigating through the different parts of the workflow. Adding bookmarks from Firefox is now more reliable, and if things still occasionally go wrong, the workflow is better at communication that in a useful way. (I switched from Safari to Firefox myself, so it got some more attention than before) Ability to add a bookmark by copying the address, rather than getting it from the currently active browser window. To use this feature for adding a bookmark from an unsupported browser (or somewhere else), just copy the address and go to the bookmark adding feature of this workflow. It will just work, without you having to do anything more than that! Get it from GitHub!
  7. There is currently no way of doing that, but it's a very good suggestion, and I'm working on a solution for it. Stay tuned!
  8. There is now a new version of this Workflow, v1.7! The most important change here is that support for macOS Monterey is added. Apple removed PHP from Monterey (which has been preinstalled since Mac OS X 10.0 in 2001), so some changes had to be made to adopt to that, and you will also need to install PHP yourself for it to work in Monterey, which I recommend that you follow PHP's own instructions for if you have not already installed it. There is also quite a few more potential problems that are fixed with this update, so if you where having problems with this workflow before, please try again with this update and hopefully it will work better. There are also some new features! Bookmarks that you have marked as favourites in Raindrop will now be indicated, and will also by default be listed on top of results, and you can also now browse your Unsorted bookmarks the same way as you can browse other collections. Download from Packal or GitHub!
  9. Thanks @mark_h for reporting your issue, and thanks @deanishe for helping with solving it! I have now also released version 1.6.1 that doesn't have this issue anymore, so hopefully your problems, @xurc and @Davide would also be fixed if you upgrade to this latest version. Please get back if that still doesn't help for you. Sorry for letting that problem get into the previous release.
  10. Exactly! I can look at this problem, @AV8RDude, if you get the error message that you'll find in the debugger, as @deanishe said. You could send the log messages you see in the debugger in a private message to me if you don't want to post it for everyone to see. First open the debugger, as in the linked instructions, then make sure to do the same thing you did when the problem occurred, and then copy and send the log messages you see in the debugger. I also think I would need the same thing from you, @xurc, to be able to find out what's going wrong in your case.
  11. There is now a new version available! The most visible change for most people will be that the icon is now updated to reflect Raindrop.io's change of logo. Other than that, there is now support for the NAVER Whale browser (as requested by @memote), and there is a bug fix for the authentication mechanism that fixes issues that some users where experiencing. @Davide & @xurc, could you try the new version and see if the problem you had might possibly be fixed with this update?
  12. @Davide & @xurc If you cloned the git repository and didn't make sure to also get the submodule that it includes, you would end up with something like what you are describing. Could that be it? If that's the reason you can fix it by going to the Raindrop.io workflow directory (right click the workflow in Alfred to find it) in the terminal and run these two commands there: git submodule init git submodule update It is supposed to work without doing anything like that if it is installed by downloading and double clicking the .alfredworkflow file.
  13. Hi @Davide & @xurc I'm trying to understand exactly what goes wrong for you. I guess thet you first open Alfred and type r anyway Then I'm a bit unsure what happens. The expected behaviour is that: 1. If you just typ r, you will get a list from Alfred with suggestions based on that one letter, with the Raindrop default options somewhere in that list. 2. If you type r<space>, and nothing more, you will get options to either open Raindrop.io in a browser or to browse your bookmarks directly inside Alfred 3. If you type r<space>search query, you will search your Raindrop bookmarks for that search query, and you should get a list with bookmarks in a second or two. What I am unsure of is if the fallback list you mention is the expected behaviour in (1) or (2) above, or if you are doing (3) and still get a fallback list, and in that case I wonder what alternatives you get in that fallback list so I can figure out what list this is and how this happened, so I can find a fix for it.
  14. Hi @memote I'll try to add support for Naver Whale in the next version (which i'm working on now), and as it seems to be Chromium based it will likely not be a problem.
  15. Hi @tsieling! Could you try to start with searching for a bookmark instead of starting with saving? It looks like there might be a problem with the authentication process if you try to save the first time you use the workflow instead of trying to search. I will look into fixing this too, but try that for now and see if it works.
  16. @deanishe Thanks for the link to that thread! It all seams to be a mess really. - The Catalina Beta release notes said at some point that all the scripting languages will be removed eventually, but there where nothing that indicated that in the actual OS - Big Sur Beta does not say anything about that in the release notes (not that I could find anyway), and all scripting languages are still there - PHP's and Python 2's version info in Big Sur says that they will be removed in a future version (which they didn't do in Catalina) - Python 3 wasn't even there before Big Sur, so it was added right now, and does not say anything about being deprecated, so it would look like that would stay then I guess? Seems to me like Apple might have changed there minds to not actually remove all scripting languages anyway, but only some of them that in their minds doesn't fit in a desktop OS for some reason, which would be PHP and maybe something else, and then of course Python 2 that is more obvious to remove as it is end of life now, and seems to rather finally be on it's way to be replaced by Python 3 even in macOS. (You still get Python 2 when you run the python command without any version number in the command though, in Big Sur Beta 1)
  17. I installed macOS Big Sur Developer Beta 1 on a secondary partition to try it out, and one unexpected thing I found out by doing that is that PHP is now marked with information that it will be removed in a future version of macOS. When I run "php --version" in Big Sur Dev Beta 1 I get: WARNING: PHP is not recommended PHP is included in macOS for compatibility with legacy software. Future versions of macOS will not include PHP. PHP 7.3.17-(to be removed in future macOS) (cli) (built: Jun 6 2020 07:41:43) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.17, Copyright (c) 1998-2018 Zend Technologies Running the same command in Catalina gives me the following (so the message above is new in Big Sur) PHP 7.3.11 (cli) (built: Apr 17 2020 19:14:14) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.11, Copyright (c) 1998-2018 Zend Technologies I guess that there is some official information about this from Apple somewhere too that I could not find, but having this disclaimer in the version information in the actual software seems official enough to me though. I thought this might be interesting for you all to know about, as many Alfred Workflows are using PHP. We will obviously be able to install PHP ourselves manually even after it isn't included out of the box anymore, which itself could take years (and I guess it could be included in Alfred itself to minimize the impact when it is actually removed), but it might be a good idea to not create new workflows in PHP anymore, and maybe think about rewriting existing ones in, for example, Python instead. (I will probably rewrite my Raindrop.io workflow in Python at som point because of this)
  18. New version again! v1.5 with quite a few changes. Primarily, you can now set the title to whatever you want and add tags when you create a new bookmark, and you also get tags in the search results so you can view or search bookmarks with that tag. More info and details in the changelog in the first post Get it here: https://www.packal.org/workflow/search-raindropio I can't really think of anything that I miss in this workflow anymore now, so there probably won't be as frequent updates anymore going forward.
  19. I found and fixed a bug that would make the bookmark adding feature fail in many cases, so update to version 1.4.1 if that didn't work for you previously.
  20. Version 1.4 is now available, and it now shows collections in the search results, and you can select them to browse or search their content. Before you have started to type a search query, you also now have the option to browse your collections instead of starting with a search. Get the new version here: http://www.packal.org/workflow/search-raindropio Thanks I started to put out the releases on GitHub too, which I didn't do at first, as that is needed to make it downloadable from Pacmax. Pacmax is rather slow at updating it's information from GitHub, so the new version will probably not be visible there until a few hours from now, but it is downloadable from Packal and GitHub right now.
  21. Version 1.3 is now available with support for adding bookmarks form the currently active browser. See the info in the first post for more about how this works, and get the new version at Packal: https://www.packal.org/workflow/search-raindropio
  22. Sorry, I think I misunderstood you. I was writing in the last posts, before your question, about the new feature coming any day now (and available on the github dev-version already) that makes it possible to add new bookmarks, and that feature does let you search for collections to add the new bookmark to. You can't search for collections and list the bookmarks in them. At least not at the moment. I had not even thought of that until right now, but It is not a bad idea I might add it later, but no promises about that right now.
  23. I really like Firefox too. I used it for many years as my primary browser, and would probably still do that if I didn't just happen to like Safari even more in recent years. But anyway, I really do want to support it together with all the other browsers, and because of the information that deanishe provided in an earlier comment here, and his great Firefox integration workflow, I have been able to make that work, and am testing and making the final touches on a version of this workflow that can add new bookmarks to Raindrop from all relevant browsers, including Firefox. I will probably release it within a week or so, but if you want to try it out now, as it is at the moment, you can find the current development version on Github: https://github.com/westerlind/alfred-raindrop-search Not really all that much information there about adding bookmarks yet, but the feature is there and works And just to make that clear, Firefox is already supported for searching and opening bookmarks. The part that was tricky to do in Firefox was adding bookmarks from it.
×
×
  • Create New...