Thank you for your interest in this little project. As you can see this project has a couple of opening/unaddressed issues, outdated releases, not-much-updated README, yet I'm still here, replying issues but no concrete progress on this project. All these have reasons. I'd like to explain a little bit and talk about the future of this toy.
A couple of reasons why I don't actively develop on this project:
Due to work reason, I (unfortunately) have to switch to Windows as my major workstation. MacOS (and hence Alfred) was gradually fading out of my day to day workflow.
I can't say developing an Alfred plugin is a quite readily progress though it's still okay, given the values (efficiency, productivity etc.) it brings. The development involves weird testing and packing process and is quite easy to forget after weeks. I did try to pick up this project during my spare time, when only a few issues emerged but it needed a lot of Googling. so it never succeeded.
This project depends on a Python2 library here. One of the painful experiences in Python2 is that str is quite different from that in Py3... The author of the library is not willing to upgrade to Python3 for compatibility reason (see issue: https://github.com/deanishe/alfred-workflow/issues/97). Adding this to point 2? No thanks.
The plan:
So I neither don't plan to totally abandon this project, nor start to add new features/fix issues. I'll wait for at least the library version bump before I can swallow the "fine" experience of point 2.
In the meantime, I believe the release, though it's pretty old, still works since the library tried its best to be compatible. So unless you have specific needs, you can still use the release. And if you do have new feature needs, as any other open source projects do, you can always fork and implement your own.
Sorry if this brings inconvenience to you. I'll come back when the lib is upgraded.
Hi,
Thank you for your interest in this little project. As you can see this project has a couple of opening/unaddressed issues, outdated releases, not-much-updated README, yet I'm still here, replying issues but no concrete progress on this project. All these have reasons. I'd like to explain a little bit and talk about the future of this toy.
A couple of reasons why I don't actively develop on this project:
Due to work reason, I (unfortunately) have to switch to Windows as my major workstation. MacOS (and hence Alfred) was gradually fading out of my day to day workflow.
I can't say developing an Alfred plugin is a quite readily progress though it's still okay, given the values (efficiency, productivity etc.) it brings. The development involves weird testing and packing process and is quite easy to forget after weeks. I did try to pick up this project during my spare time, when only a few issues emerged but it needed a lot of Googling. so it never succeeded.
This project depends on a Python2 library here. One of the painful experiences in Python2 is that
str
is quite different from that in Py3... The author of the library is not willing to upgrade to Python3 for compatibility reason (see issue: https://github.com/deanishe/alfred-workflow/issues/97). Adding this to point 2? No thanks.The plan:
So I neither don't plan to totally abandon this project, nor start to add new features/fix issues. I'll wait for at least the library version bump before I can swallow the "fine" experience of point 2.
In the meantime, I believe the release, though it's pretty old, still works since the library tried its best to be compatible. So unless you have specific needs, you can still use the release. And if you do have new feature needs, as any other open source projects do, you can always fork and implement your own.
Sorry if this brings inconvenience to you. I'll come back when the lib is upgraded.
And thank you for your support.