Jump to content

pier

Member
  • Content Count

    22
  • Joined

  • Last visited

  1. So right now the preview window of the clipboard allows you to see enough to know what's in the entry, but it's not so great for consultation. For example what I often do is that I copy bits of code that I only want to use as reference, but since reading those in clipboard preview is difficult (small text, broken lines, etc) I'm forced to paste the contents somewhere else. So my feature request would be to be able to customize the preview window (larger space, larger text) or simply make it bigger by default.
  2. pier

    Excluding Folders

    Would adding the alfred:ignore tag to a folder make Alfred ignore all the files and subfolders too?
  3. pier

    Excluding Folders

    Sorry for reviving an old thread but this is the first Google result on the matter. Would be awesome if there was a way to define a dynamic ignore. For example I'd like to ignore all node_modules folders which are created on every new JS project. AFAIK there is not really a way to do that in Spotlight either, but it would be awesome if Alfred could solve this.
  4. Thanks all for your support and the nice conversation.
  5. Um I'm not following you. We are talking about Nodekit, right? Yes I could just node whatever.js but the problem of distributing workflows that use node would still persist. On a side note. Is there a way of showing a message to the user from the workflow and inform Node is needed?
  6. How could I? AFAIK this would have to be compiled with Alfred's code.
  7. It is indeed. We used React in 2016 and this year we are moving all our new projects to Vue.
  8. Yes, that was what I was suggesting.
  9. Because @deanishe basically said "I don't like JS" and I simply insisted that Nodekit would solve the problems stated earlier about using the Node API from scripts in Alfred.
  10. Sure, but it would solve many of the issues about trying to make Alfred work with Node.
  11. You are of course technically correct, but I feel since Node and NPM entered the scene we are in a new JS renaissance that it's still trying to trying to define itself. I don't mean the language itself but the whole development process. Maybe I'm delusional, but I think (I hope) we should reach a maturity plateau in a couple of years.
  12. Hey guys I just found this: https://nodekit.io/ relevant to the discussion about Node. It's a cross platform Node replacement that uses the JS engine provided by the OS so it provides a very lightweight implementation of the Node API. The motivation page gives a bit more of insight.
  13. If your app doesn't use Node you use this https://github.com/francoislaberge/shrinkray (macOS only) JS is in a teenager phase like PHP was 15-20 years ago. Hopefully it will mature and learn from its mistakes if Web Assembly doesn't kill it...
  14. Yes I'm aware of that. I'm not suggesting Node should come bundled with Alfred by default. Workflows could define a Node dependency so that Alfred could install it for the user. As for the technical work I really can't say how intricate it would be but other projects like Electron have already solved that. But Alfred does define the workflow specifications. Hence if a workflow could say "hey I need Node", Alfred could in principle download it for the Alfred user.
  15. Thanks @deanishe It would be awesome if Alfred provided an easy to distribute workflows that use Node instead.
×