Jump to content

Tyler Eich

Member
  • Posts

    628
  • Joined

  • Last visited

  • Days Won

    22

Reputation Activity

  1. Like
    Tyler Eich reacted to rice.shawn in Packal: Workflow and Theme Repository   
    I'm happy to announce that after months of development, I'm ready to make a new workflow and theme repository available to the public as an open beta: Packal. Workflows and themes are taggable and searchable. You can add in the icons, screenshots, long descriptions, and brief ones. There are many different ways to find whatever you need there. Since this is an initial announcement, there isn't much content there yet, except for the workflows and themes that a few kind testers uploaded.
     
    Themes are stored as a simple application URL, which means there are no files to download, but, instead, they import directly into Alfred2. Workflows are scanned for viruses after they are submitted but before they are made available publicly. Workflow authors can easily update their workflows just by editing the page and replacing the workflow file there.
     
    What is even better is that Packal has its own updater for workflows. So, you have the option to update any workflows that you have downloaded from Packal.
     
    I think that these are exciting developments for Alfred, and this sort of repository is what many people have been waiting for since these forums were created.
     
    One great advantage for distributing your workflows via Packal is that you do not need to maintain your own download links for your workflows anymore, so you won't need to worry about download limits on sharing services. Another advantage is that it will receive more visibility as it is a place where people can look for workflows and themes without having to page through the impressive number of posts in these forums.
     
    So, please, head over to Packal, browse what's there, and, very importantly, submit your own workflows and themes.
     
    --Shawn
  2. Like
    Tyler Eich reacted to RodgerWW in Replace spaces with dashes in file name   
    Try this in your script for creating the file:
    file=$(echo "{query}.md" | tr " " "-") touch $( date '+%Y-%m-%d-' )"$file" SPACES still unchecked.
  3. Like
    Tyler Eich reacted to smerickson in Feature Request: Workflow "Variables" or "Settings"   
    Workflows are awesome!  I've made a number of workflows for myself recently.  I'd like to be able to share my workflows with other members of my team.  The main challenge to doing that is that many of my workflows are user-specific or account-specific or require some kind of settings value.  I would love for each user to be able to type in their own username or account name as a "variable" item in the workflow configuration screen.
     
    My dream is that there would be a new type of "Workflow Input" called "Variable" or "Setting".  You could give it a name and then there would be a simple text box to let a novice user type in a value for the variable/setting.  I could then connect these input variables to my more complicated/generic scripts and have those scripts use the user-defined variables.  I imagine these would be available to my scripts the same way that the "{query}" variable can be used.
     
    Just to clarify, these variables are not things that the user would type into the Alfred search box.  They are more like "settings" or "preferences" for my workflow.  They would be set up by users in the workflow configuration screen.  The values only needs to be configured once.
     
    Thanks for considering.
  4. Like
    Tyler Eich got a reaction from leefur in The Minimalist: Flat UI colors   
    These themes look great! Great work!
     
    One note: the serif font used for the subtitle is out of place. Perhaps a sans-serif font (like Helvetica) would be better?
  5. Like
    Tyler Eich reacted to JoeyUrge in Can Alfred do this like in LaunchBar...?   
    If I am understanding what you want to do, wouldn't command + tab work for your needs?
  6. Like
    Tyler Eich got a reaction from Alan He in Colors—convert color formats & access the OS X color panel   
    Colors v2.0.0
     
    Get it from Packal (Recommended)
     
    Quick Summary:
    This workflow can process and convert all CSS color formats and several Objective-C formats, namely NSColor (calibrated and device) and UIColor. It also provides an interface to the OS X color panel for easier color manipulations.
     
    It's written in native code (i.e. it's really fast).
     
    Quick Preview:

    You can find a full description on Packal.
     
    Direct download • source code on Github
  7. Like
    Tyler Eich reacted to Excalibur in Option to hide icons in results   
    Hello,
     
    I am just discovering all possibilities of Alfred but one thing I would really like seems to be missing: an option to hide the icons from the search results. What I am talking about are the icons in the "magnifying glass" in the picture below. I am sure that many people would find this an unuseful feature but it seems like a simple feature that I (and maybe others) would very much enjoy..
     

  8. Like
    Tyler Eich reacted to Vero in File selection hotkey   
    If you're on a non-English keyboard, you may want to change the hotkey to something easier for you. You'll find the hotkey in the preferences under Features > File Search > Actions, at the bottom of the panel. Swap it for anything that suits you and doesn't clash with your existing hotkeys
  9. Like
    Tyler Eich got a reaction from crs1138 in Change default Amazon and eBay countries   
    Under Alfred Preferences > General > Where Are You:, try changing the country to 'United Kingdom'
  10. Like
    Tyler Eich got a reaction from rice.shawn in Colors Beta   
    Colors 2.0 is currently in the works. Improvements include:
    Speed (written in Objective-C; near-instantaneous results) Full support for NSColor and UIColor Better preview images (uses a different, higher-contrast transparency background) ⌘C will copy the result's text Opacity slider in the OS X color panel Hotkey for revealing the OS X color panel Download • View on Github
     
    Looking for the stable release? Check out the main Colors thread
     
    You can run the beta parallel to the stable release; it uses a different BundleID (until v2.0 is stable, at least). Beta testing is strictly voluntary, with no obligation to myself or the beta tester.

    I'm mainly trying to stabilize the code (e.g. removing bugs, fixing performance issues, etc.), but feature requests are welcome!

    Here are some images of the workflow in action:



    And the workflow editor:


    Cheers, and many thanks for your help
  11. Like
    Tyler Eich got a reaction from twinpeaks in Colors Beta   
    @twinpeaks @Florian Thanks guys! I'm happy you liked v1.
    In true Alfred spirit, I want this rewrite to greatly improve the existing workflow. Though bug fixes and polish are the focus, feature requests are always welcome
  12. Like
    Tyler Eich got a reaction from thec13 in Colors Beta   
    Colors 2.0 is currently in the works. Improvements include:
    Speed (written in Objective-C; near-instantaneous results) Full support for NSColor and UIColor Better preview images (uses a different, higher-contrast transparency background) ⌘C will copy the result's text Opacity slider in the OS X color panel Hotkey for revealing the OS X color panel Download • View on Github
     
    Looking for the stable release? Check out the main Colors thread
     
    You can run the beta parallel to the stable release; it uses a different BundleID (until v2.0 is stable, at least). Beta testing is strictly voluntary, with no obligation to myself or the beta tester.

    I'm mainly trying to stabilize the code (e.g. removing bugs, fixing performance issues, etc.), but feature requests are welcome!

    Here are some images of the workflow in action:



    And the workflow editor:


    Cheers, and many thanks for your help
  13. Like
    Tyler Eich reacted to jdfwarrior in Recommendations for Sharing Workflows   
    Recommendations for Sharing Workflows
     
    The forums have really been running well and you guys (and gals) have been creating some amazing workflows so far. I wanted to throw out a few suggestions though to make sure things stay organized, are easy to read, and easy to find.
     
    This will be an evolving document. Check back for questions regarding questions on posting your workflows. If you have a question that isn't answered within the contents of this thread, feel free to contact any of the moderators (Myself, Andrew, or Vero). 
     
    Post Titles
    Be specific. Don't be overly descriptive about every little feature the workflow provides. Titles are best kept to the workflow name, and potentially a few words on the overall gist of what it does.
     
    Tags
    Be sure to set topic tags for your workflow post. This will make it easier for users searching on the forums to find your post/workflow easily based off of a few key words.
     
    Dependencies
    Please include a listing of all dependencies for your workflow. This will hopefully alleviate potential problems that users run into from attempting to run an installed workflow without an installed package being present. Examples of this would be Ruby gems or Python modules or even Python versions that are required for using the workflow. If a specific application is required for your workflow to function, be sure to include a link to that applications website, or a link to it in the App Store as well. Also include, if necessary, required versions of OS X.
     
    System Modifications
    If your workflow creates or modifies any supporting files that would alter the users environment, this should be noted. This will make it known up front that your workflow modifies system file X to achieve its functionality. Also, if the user uninstalls the workflow, how to remove these files or restore the originals.
     
    Screenshots
    They aren't required, but providing a screenshot or two for your workflow helps provide users with a good idea of what it is they are about to download. Descriptions help, but many users are wanting to pop in, get a quick visual, and download.
     
    Posting
    When sharing a new workflow, please be sure to create your own thread for it. By posting it in another workflows thread, your workflow may never reach the masses. Create your own thread so that it stands out and everyone will be able to find it easily. This helps remove confusion on which workflow to download if there are multiple workflows, or modified workflows posted within the same thread. It also helps ensure that the develop that spent their time and put in the hard work to create the workflow get credit for their work. Posting a patch/update/fix/modified version of a workflow in another authors thread may steal attention from their original work. So let's try to be considerate.
     
    Sharing Multiple Workflows
    Try to limit a new thread to a single workflow. The reason for this follows the situation mentioned above. Unless you have an abnormally long title, users casually browsing the forums may not realize how many workflows are available in the post, or what they are. Creating a separate post for workflows also creates an individual area for you to provide support or answer questions for that workflow alone.
     
    Modifying Existing Workflows
    Most developers are very open to feature requests for their published workflows. So before modifying someone else's workflows, check with the developer and see if they would add the feature first. If the requested feature is something that the developer doesn't plan on adding, of course you could add the feature yourself. If you think it's a feature that others would also find greatly useful and you decide that you would like to share your modified version, please be respectful of the original developer give them a heads up before hand. Also, be courteous and give credit to the original author and/or a link back to their original thread so that they receive some credit for their work. Nobody enjoys having their work stolen.
     
    Updating You Workflows
    When sharing an update to an already posted workflow, rather than creating another post in the existing thread, update the initial post to include desired information and updated download links (if necessary). This makes it easier for users to find the most up to date version of your workflows, along with information what is included in the update. You could also modify the thread title to indicate the date that the workflow was last updated.
     
     
    Notice: I'm also going to try to monitor this thread and keep it clean. If you post suggestions for other things to be added to the document, if they are merged in, I will probably remove your original post. Questions will also be treated the same way. If answers are later added into the original post, I may remove the original question. This will hopefully keep it so that all documentation remains in the original post so someone doesn't potentially have to search through several pages of questions for find a simple answer.
  14. Like
    Tyler Eich reacted to Florian in Better notifications   
    Hey Alfred Team,
     
    since mavericks release, the notifications have gained in complexity and I believe Alfred could take advantage of that. I believe that if the "Post Notification" output of a workflow were to take an XML as an input instead of a query, we could achieve something good.
    Here are my ideas for new functionalities but feel free to add more in the comments.
     
     
    1 - The notification image display should ressemble more iTunes notifications: alfred's icon in small, workflow icon as main, and tertiary image optional.

     
    2 - Notifications should allow clicking for actions (both main action when clicking on the notif itself and secondary action when clicking on a button): open a file with path, show file in finder with path, pop alfred back up with search, remove file (for cancelling a download for example), open an app...

     
    3 - like I was saying, to accomplish that I believe an XML input would be appropriate. I haven't thought of an ideal way to point to the next action (when clicking, see 2.) but this is I believe overall relevant:
    <item> <title> Here my title </title> <subtitle> And there a detailed subtitle </subtitle> <image> /path/to/optional/image.jpg </image> <main_action arg=""> path/to/script/to/run </main_action> <secondary_action arg="" button_text="Skip"> path/to/script/to/run </secondary_action> </item> 4 - In case of multiple notifications, some RSS notifiers have thought that putting some delay between notifications allows for better readability and gives time for the user to click if needed. In the case of XML notifications (see point 3.) we could imagine that several notifications of equal importance might need to be displayed (file1.txt, file2.txt downloaded, each could allow for action (like deleting) thus some time between both notification is relevant) but also some notification might be hierarchical ("process started", "process finished") in which case delay is not relevant. I propose:
    <items delay="no"> <item> <title> process started </title> </item> <item> <title> process finished </title> </item> </items> or
    <items delay="yes"> <item> <title> file1.txt downloaded </title> </item> <item> <title> file2.txt downloaded </title> </item> </items> That's all for now. I do believe all that is doable within a script that would run at the end of a workflow instead of a notification output, so if anyone else than Andrew wants to give it a try, there's some good to be done
     
    Cheers all
  15. Like
    Tyler Eich reacted to Florian in Colors Beta   
    Ah ah ! Don't get me wrong, I love beta testing. What I was asking was about the new version itself, not from beta testing.
     
    And yeah you're right, v1.0 was indeed awesome.
  16. Like
    Tyler Eich reacted to twinpeaks in Colors Beta   
    @Florian, straight to the point while still confusing! What is to be gained from the workflow or gained from beta testing? Either way, I needed the laugh.
    - You gain a better workflow, maybe someone who can provide feedback and fixes on your workflows along with some good karma. 
     
    @ Tyler Eich - I think you blew everyone away with colors 1.0, I am glad to see your challenging yourself and not resting on your laurels so to speak. +1 for sharing the results of your hard work with us and even allowing open participation for sought after features, those which you haven't found a use case for at least. This workflow takes the cake for number of "connectors," even the guts are aesthetically pleasing. Again, thank you for keeping us leeches in your thoughts and I'll attempt to give some feedback if anything appears out of order, both appearance wise and functionality.
  17. Like
    Tyler Eich got a reaction from twinpeaks in Colors Beta   
    Colors 2.0 is currently in the works. Improvements include:
    Speed (written in Objective-C; near-instantaneous results) Full support for NSColor and UIColor Better preview images (uses a different, higher-contrast transparency background) ⌘C will copy the result's text Opacity slider in the OS X color panel Hotkey for revealing the OS X color panel Download • View on Github
     
    Looking for the stable release? Check out the main Colors thread
     
    You can run the beta parallel to the stable release; it uses a different BundleID (until v2.0 is stable, at least). Beta testing is strictly voluntary, with no obligation to myself or the beta tester.

    I'm mainly trying to stabilize the code (e.g. removing bugs, fixing performance issues, etc.), but feature requests are welcome!

    Here are some images of the workflow in action:



    And the workflow editor:


    Cheers, and many thanks for your help
  18. Like
    Tyler Eich got a reaction from vdesabou in Colors Beta   
    Colors 2.0 is currently in the works. Improvements include:
    Speed (written in Objective-C; near-instantaneous results) Full support for NSColor and UIColor Better preview images (uses a different, higher-contrast transparency background) ⌘C will copy the result's text Opacity slider in the OS X color panel Hotkey for revealing the OS X color panel Download • View on Github
     
    Looking for the stable release? Check out the main Colors thread
     
    You can run the beta parallel to the stable release; it uses a different BundleID (until v2.0 is stable, at least). Beta testing is strictly voluntary, with no obligation to myself or the beta tester.

    I'm mainly trying to stabilize the code (e.g. removing bugs, fixing performance issues, etc.), but feature requests are welcome!

    Here are some images of the workflow in action:



    And the workflow editor:


    Cheers, and many thanks for your help
  19. Like
    Tyler Eich got a reaction from ebarrere in How to pass arguments to script filter result   
    The only argument a script filter will accept is {query}. That said, a lot can be done with {query}.
     
    For example, in my Colors v1.41 workflow, I use the script filter to parse {query}. So, given the input rgb26,12,31, rgb triggers the RGB script filter; the code in that script filter separates each channel by splitting the {query} (26,12,31) at every comma. From this, I can generate a preview image and convert the color to other formats.
     
    Summary: use string manipulations in your code to parse {query} into separate arguments
  20. Like
    Tyler Eich reacted to getthething in Clean your RAM with Alfred   
    Very thorough. Much appreciated. Thank you. 
  21. Like
    Tyler Eich reacted to Florian in Option to first char strip single quote from fallback results   
    Hey Alfred team,
    whenever I'm looking for a file with my dear Alfred, the query starts with a single quote, of course. But if this file doesn't exist on my computer, I'm going to want to look for it on the internet, right? But then the fallback searches will all take this query as it is, meaning with a single quote as first character, which is of no use for my purpose. Of course I could edit manually every single fallback result, but I believe many of us could benefit from a simple option to ignore first char if it is a single quote for fallback results.
    Cheers.

  22. Like
    Tyler Eich reacted to redzep in Store images in Alfred's clipboard history, allow images in clipboard snippets   
    Yes, a glaring omission in an otherwise brilliant program. Would love image selections and screen captures as well. 
     
    +1 !
  23. Like
    Tyler Eich reacted to HusseinMorsy in Store images in Alfred's clipboard history, allow images in clipboard snippets   
    I was a launchbar user for years and switched to Alfred  (Mega License) because of the great new features. 
    But Please Please Please add image or rich content support to cliboard and snippets. The would be really great !!!
  24. Like
    Tyler Eich got a reaction from daehn in Store images in Alfred's clipboard history, allow images in clipboard snippets   
    It would be really cool if Alfred had an option for storing images in Clipboard History. Plain text is easy to search and light on resources, but limiting if you rely on images (e.g. graphic designer).
     
    When using snippets and/or workflow clipboard objects, {clipboard} should be able to inject images stored in the Clipboard.
     
    This would obviously increase Alfred's memory usage; if implemented, it should definitely be optional. Maybe even separate settings that set limits on how big a stored image can be (just like the current implementation for text clipping size).
     
    Cheers
  25. Like
    Tyler Eich reacted to vrtcl1dvoshun in Add a version field for workflows   
    Need the ability to add a version field to keep track of workflow changes and prevent updates from wiping out user customizations.
     
    If not, then I suggest developers at least add their app's version to its name as follows: "My Alfred Workflow (2.3)" which would remain consistent with the way Apple denotes different app versions. The version number should show up in both the filename of the workflow and in the name that is seen in Alfred's workflow preference pane.
×
×
  • Create New...