Jump to content

twinpeaks

Member
  • Posts

    171
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by twinpeaks

  1. Can anyone explain me why sending messages in this workflow has so many if-else statements?

     

    I wrote workflow that displays all contacts from Adium in Alfred and allows to send message, but my sending is in two lines and seems to work but maybe I don't know something (well, I know nothing about applescript despite using it in this...).

     

    If it works for you, it works. Your well skilled in the coding area so I have faith your method works just fine. If you don't mind, for the rest of us who can't code... do you mind posting it here or in another thread or anywhere you want - I'm happy to be a guinea pig.

  2. I didn't offer much, this workflow is simply amazing though. I haven’t messaged you with any problems because so far it is smooth sailing.

     

    Now that I think of it, an easy way to change your "working folder directory" if you decide to move locations later... most won't use it and reverting just calls for clearing out related cache etc... but only thing I can think of... really trivial. Thanks again for sharing. Use it all the time, handy as heck.

  3. All great points made here and I'm also glad that Andrew got in the conversation to let us know that when an official list goes up, in whatever form it may be, it will be censored. Not to say that in a bad way, it is completely necessary and understandable from their perspective and If I were them I would do the same.

     

    However, for the rest of us, if we want access to workflows that anyone and everyone is willing to share, and then filter and inspect the content/usefulness of workflows ourselves, we will need a community style system. I think Alfred has enough users that once a basic framework is setup and people can contribute their time and/or talents to maintaining it we won't have any problems. Yes bandwidth is a major concern, but that is why sites like Github are so valuable.

     

    If Github can power homebrew, I think it can power an Alfred workflow repository, just as people stepped up to maintain and even develop Homebrew the same will happen for whatever system gets setup to manage Alfred workflows. It's all a matter of time, once an individual with foresight steps forward and lays out the basic framework, there will be plenty of good minds willing to volunteer their time supporting a project they believe in... right now we just need a chief willing to forge the way as I think we can all agree this is an idea most Alfred users and workflow developers will get behind.

     

    I'll be honest and say that person is not me. I do not have the required coding knowledge to anticipate and resolve the sort of obstacles a Github based workflow repository will generate. If it comes to dedicating my time to help test, or do tedious no-code related work I will happily give my time.

     

    All in all, I am glad to see this discussion taking place with good people offering good ideas. Luckily this forum exists and the Alfred team is not censoring any cooperation amongst it's users so let's take advantage of what we've been given and for the time being remember that there will be a slew of more volunteers willing to dedicate whatever they can when they are given access to Alfred 2.

    Progressive Downloader Integration Plug-in
    Progressive Downloader Integration Plug-in
  4. Still down?

    Yes, just visit the site and you can tell, along with the script not working or the wonderful addition for alfpt by Robhor.

     

    If this link: http://alfredrepo.tom-hunt.co.uk - doesn't return anything... it's down. I really do not think it is coming online again so we just have to have patience or buy some hosting or use github...

     

    Might be a good idea to start a list of our own of every "known" workflow out there along with developer info if available.

  5. Well we had a pretty solid combo with Alfpt workflow by Tom Hunt and Rob Horvath's Repo workflow. Now that Tom has taken down the repository we see the problems with having one person host the repository.

     

    I do not think the Alfred team, at this point, has the time to put up a repo from what I have gathered from comments around here.

     

    Github repo is the way to go but there needs to be a couple smart and reliable members to keep it up running smoothly... Something will come up hopefully.

  6. Hi All,

     

     

    I see that the Info panel on workflows how has an Update button.

    How does that work?? Anything we can do to lonk to new versions or will this be something pointing to a future repository on alfredapp.com itself?

     

     

              Corentin

     

    If I am not mistaken, the update button has been there for a while and it just "updates" the information fields if you actually change some of the details... don't think it has anything to do with actually updating the workflow to a new version off the net etc...

  7. We know. When v2 is released I am sure the Alfred team will contemplate if they want to have an "official" repo but most likely they will just have a site where people post/send them workflows.

     

    We are VERY lucky to have Tom's site. Let's not forget that. Robhor's extension just makes using Alfpt that much easier imo. Both are necessary... we could just have no repo? That would suck...

     

    Tom's main site is up so hopefully the repo part will be up soon. Goes to show how quickly it all can be pulled.

  8. No problem, glad I could help. I didn’t read the disclaimer on the Jono Icons. Really not free for personal use and projects involving no profit? I do realize there are tons of licenses that I don't pay too much attention to if the person posts links to download on their site. Good looking out to be safe though. Personally, I am sticking with the Jono.

  9. I agree jordic. It's only possible because of Tom's vision but robhor's workflow is much easier and quicker. They work great together.

     

    Unfortunately the repo is down right now, as of this post so neither one works... I am sure when there is a stable v2.0 there will be an official repo.

     

    If possible, Tom, can you give us permission/instructions to mirror your repo so we have backups online all the time in case of server failure? Such as what is occurring now? Anyway we can help?

  10. 2 part post with the disclaimer that I can't code and only converted the already working scripts in v1 to work with v2.
     - Basic features "missing" in the working Applescript implementations include (although I am sure easily fixed by those who understand basic applescript):
     
    1) Here are two scripts/v1 extensions I found on veritrope.com that when executed grab all tabs of the frontmost Safari or Chrome window -> prompt you for filename and directory to save to. I have converted them to v2 workflows but all credit goes to original developers.
     
      - 1) No way to make the scripts prepend the date to the filename 
      - 2) No way to avoid Finder prompt for filename and save location. Fixed location set in script with notification that tabs were saved successfully or not would be great.
             - It would be nice if the workflow behaved with a file prompt, as it is now, asking for name and location holding a modifier and no file prompt without modifier.
     
     
    Info is organized well and here is an example of what it looks like:
     
    URL List from Safari Tabs | Monday, February 11, 2013 12:56:31 PM
    
    
    Share your Workflows - Alfred App Community Forum
    http://www.alfredforum.com/forum/3-share-your-workflows/
    
    
    App specific CPU usage limiter [work in progress] - Share your Workflows - Alfred App Community Forum
    
    

     

     

     
    Link to v2 workflow converted from v1 alfred extension and script - works in v2 with no mods except I have to call via osascript, not AS directly:
     
    Code for Safari Version on the web and v1 extension:
     
    Code for Chrome Version which also has v1 alfredextension already made: 
     
    # -----------------------------------------------------------------------------
     
    Markdown tab links to file:
     
    These two scripts need to be implemented in Alfred. They work by themselves but since I can't code or anything of the sort can't figure out how to implement them with Alfred:
     
    I grabbed these from bretterpstra.com's Markdown Service Tools pack so all credit to him for the scripts. They are written in ruby and seem to work as system services but I was hoping that maybe someone here who could code and had an interest in such a modification could use these scripts and make a workflow out of them. 
     
    The scripts do all the hard parts of grabbing the tab info and pasting that info as markdown reference links. I was just thinking that it would be useful to be able to call the scripts from a hotkey or keyword and have a list automatically 
     
    Code pasted from the .rb files:
     
    Actual .rb files zipped up:
     
    The ruby scripts work like I said but I don't have the skill to make them work with Alfred.
     
    Grab the original services and info about them from which I extracted scripts above here:
     
  11. Very nice! I really like it. would it be possible to add a hotkey wire/option to make it open the file after creation? For instance holding "fn" opens the file after creation... That would be splendid. Obviously it's not done but what a great start. Always on the cutting edge you two!

  12. Andrew still has stuff in plans. You guys need to constantly remember, this is a beta. Features are still going in, and additional features are still on the books for future releases. We can't get EVERYTHING for v2, otherwise, it would never be released. :)

     

    Hehe, I know David. The goal now is to get v2 out there for public consumption and new features will be added regularly. I know Andrew is an overly dedicated developer, which is why we love Alfred, so new features are always going to be in the works. I was just pointing out that this workflow is a good example of why that feature is highly anticipated. 

  13. Look forward to this! Here is a workflow which does much less than your workflow idea but I simply took a v1 script and made it into a workflow for v2. All credit are given in the file to original developer http://johnfraney.ca - Phyllstein already posted a much more advanced "Touch" workflow, and...

     

    This is nothing compared to what David and Pedro are thinking of... but, if you want a workflow that works by writing a file to your frontmost finder window file and then opens it in default editor in 3 steps check it out:

     

    1) enter keyword

    2) entering filename and extension

    3) pressing enter and have it open in default editor of the extension.

     

    http://d.pr/f/sPkT

     

    All credit to johnfraney.ca who made the original script for v1. Again, it is not what Pedro and David have planned, not even close as flexible or useful but simple so I thought I'd post it.

    Not trying to steal any thunder... really, I didn't even make this.

  14. Instead of using the Tags icon. Here are a couple options.

     

    1) Tag icons by Jono, preview below and grab zip of both here if you like: http://www.iconaholic.com./downloads.html#tagging

        I also uploaded here so it might be easier: http://d.pr/f/JI1U

    big-tag-icons.jpg

     

    2) Openmeta logos hosted on the google openmeta repository. Made by indev.ca which are here: http://openmeta.googlecode.com/files/OpenMetaLogos.zip or http://d.pr/f/y57m

     

     

    I definitely prefer option 1 but both are better than the tags icon imo. I have been using the Jono tag icons since my scope filter for Alfred v1 and it looks nice.

  15. Sweet! I knew after you had made the kill workflow you were going to do a top processes one. Now that they work in tandem it's even better. This workflow is a prime example of how and why workflows should be able to directly integrate with eachother instead of resorting to copy > applescript calling other workflow with argument > paste in order to work. Anyhow, nicely implemented and the switch from top to kill is not all that painful. Excellent workflow! Thanks for sharing.

×
×
  • Create New...