wolph

Percentages were already somewhat supported but not in the way you're currently using them. Currently they're only part of ratios (i.e. parts per million)
 
I've created a new version that supports pretty much all of this but it ignores the $ sign since there's no currency support yet.

That's indeed interesting information, thanks
 
I suppose that would have to be included somewhere as well but I'm not sure what would be the best location. I don't think the entry_points would be a great fit.
 
Personally I would recommend the usage of MANIFEST.in alone and simply ignore package_data. They largely overlap in functionality and I would argue that the MANIFEST.in system is easier to interpret as it doesn't offer any mapping/rewrite options.
 
As for a better tutorial, chapter 15 of my book covers the usage of MANIFEST.in but I'm not sure if it's that much clearer... I'll send you the paragraph soon so you can judge for yourself
   
Looks like a very nice starting point      
Ideally Alfred would support the entry points natively which would even make it possible to do a pip install -e workflow for development purposes. That would break backward compatibility however so I don't think that should be the first or only option.
 
What I would like to propose is a setuptools build command which generates the entire workflow including the Alfred XML from the setup.py file.
 
To ease development I think it should also contain a alfred_install or alfred_develop command to symlink the package so Alfred sees the workflow straight away.
 
The added benefit of the setuptools entry points approach is that it would allow for a plugin manager to easily detect all Alfred plugins and show a list of available entry_points. That would allow for easy documentation as well since everything will be automatically generated
 
 
 
The single strongest argument I can think of to go for a smart utility is consistency. A single silly mistake in a workflow can break everything which is especially annoying for inexperienced developers.
Not having to worry about packaging, uploading and the writing of a plist file at least removes that part of the equation.
 
Everything is open for discussion of course, as long as it makes it things easier for developers  
 
 
That could be interesting, and generally easier to write than setup.py files
 
 
Ok, I'll edit the start post

What I personally do (and which will probably work for deanishe as well) is have a computer connected to the TV which has Airserver installed. Airserver is a full Airplay server for both video and audio (even lossless) so it works perfectly for iphones and even macbooks.
With that you can keep the current setup and speakers and only requires you to buy Airserver but beyond that it gives you all the needed options.

Alfred unit converter is a really fast smart calculator for Alfred with support for unit conversions to make it a bit comparable to the Google Calculator and Wolfram Alpha.
If new units and/or other names for units should be added please let me know by creating an issue at:https://github.com/WoLpH/alfred-converter/issues
Example queries
 
Downloadable from Packal: http://www.packal.org/workflow/unit-converter
1m in cm # Just a simple conversion 2^30 byte # Using powers before conversion 5' # Converting units with special characters 20" # Like above 5 * cos(pi + 2) # Executing mathematical functions 5 * pi + 2 mm in m # Mathematical constants with unit conversion 1 * cos(pi/2) - sin(pi^2) # More advanced mathematical expressions ln(e^10) # Testing the ln(x) alias of log _e(x) log(e^10) # The normal log method 5+3^2" in mm # Testing math with unit conversion 1 + 2 / 3 * 4) mm^2 in cm^2 # Unbalanced paranthesis with unit conversion ((1 + 2 / 3 * 4) mm^2 in cm^2 # Unbalanced paranthesis the other way inf - inf # Not actually possible, but we backtrack to "inf" The list of units and conversions was downloaded from:http://w3.energistics.org/uom/poscUnits22.xml It returns results within 50 milliseconds making it fast enough to use the results instead of the standard alfred calculator. It supports more too
 
Note: the parser automatically works when you start with a number or a ".". For all other cases (functions for example) it's best to just use "=". For example: "=ln(e^5)"
 
   

That indeed seems like a better idea, having all of the passwords in my lastpass stored as plain text doesn't sound like a good idea. Kind of beats the purpose of using lastpass

Is there any reason that the "lpvm.rb" file is not on Github? When it comes to lastpass I'm a bit careful of course

Yay, thank you Andrew.  You have probably mentioned this elsewhere, but what's your rough timeline for the 2.6 release?

Very interesting. Do you have some convenient way for users of your workflow to spin up a background worker? Or is this applicable to your own, non-shared workflows?
 

Not a bad workaround at all; just wish we didn't have to resort to that.
 

Same question as I asked Florian: do you have some way for this background worker to be created when a random user uses your workflow, or is that workflow something internal to you (where you can guarantee that the worker is running)?

Yeah... it's nice to have accuracy but sometimes it's a bit much
Right now it rounds to 6 decimal places so things like 4^.5 work without a problem but it doesn't lose precision for calculations like: (25/4)^.5

Alfred unit converter is a really fast smart calculator for Alfred with support for unit conversions to make it a bit comparable to the Google Calculator and Wolfram Alpha.
If new units and/or other names for units should be added please let me know by creating an issue at:https://github.com/WoLpH/alfred-converter/issues
Example queries
 
Downloadable from Packal: http://www.packal.org/workflow/unit-converter
1m in cm # Just a simple conversion 2^30 byte # Using powers before conversion 5' # Converting units with special characters 20" # Like above 5 * cos(pi + 2) # Executing mathematical functions 5 * pi + 2 mm in m # Mathematical constants with unit conversion 1 * cos(pi/2) - sin(pi^2) # More advanced mathematical expressions ln(e^10) # Testing the ln(x) alias of log _e(x) log(e^10) # The normal log method 5+3^2" in mm # Testing math with unit conversion 1 + 2 / 3 * 4) mm^2 in cm^2 # Unbalanced paranthesis with unit conversion ((1 + 2 / 3 * 4) mm^2 in cm^2 # Unbalanced paranthesis the other way inf - inf # Not actually possible, but we backtrack to "inf" The list of units and conversions was downloaded from:http://w3.energistics.org/uom/poscUnits22.xml It returns results within 50 milliseconds making it fast enough to use the results instead of the standard alfred calculator. It supports more too
 
Note: the parser automatically works when you start with a number or a ".". For all other cases (functions for example) it's best to just use "=". For example: "=ln(e^5)"