Other ENVs to add as resources about alfred-bundler

[deanishe]

How does that AlfredBundler::load_env nodejs double colon stuff work? (bash is not my strong point).

[shawnrice]

Turns out the Google's Shell coding style recommends prefixing library functions with LIBRARYNAME::.

Regular bash functions, thus, can have colons in them (who knew?). So, to avoid naming conflicts, I'm removing the older __ prefixes and adding AlfredBundler:: as the prefix. Although, according to the coding standards, that should probably be something like alfred_bundler, but I'm trying to keep some consistency through all of the bundlers.

See AlfredBundler.sh for a partly re-written version of the bash bundler backend that has the library prefixes. Bonus: it now handles all of the icon color conversion calculations natively. Floating point math in bash! Woot.

[shawnrice]

Oh, here's a more direct answer:

We'd create a function called AlfredBundler::load_env that could take a few predefined environments that we've created, and that would (1) install the environment (which would take forever) and (2) return the path to the main binary.

[shawnrice]

While I'm still not too sure how I feel about this, I still think that we'd have to compile stand-alone binaries in order to keep these from the rest of the system (and because we can't assume that the user will have the correct dev tools to compile a sandboxed version).

Here are two tools that might help:

• Ermine
• Statifier