Move some pipemenu functions to bl-include.cfg? about bunsen-pipemenus HOT 7 CLOSED

If it's re-usable, then the function can be put in the library. If it's not, it doesn't belong in a library -> seems reasonable to me.

from bunsen-pipemenus.

For example, browserExists(), screenshooterExists could be replaced by appExists(), slightly rewritten to allow different arrays to be accessed. Such an appExists() might be re-usable in a different part of the forest.

BTW is .cfg really a suitable file ending for a collection of shell functions?

from bunsen-pipemenus.

"It would be more elegant, but is it worth the effort?"

Yes it would be better to have library functions, but since it doesn't affect anything atm is it worth the effort of re-writing scripts at this stage? It could be left for BL Deuterium (aka BL Hydrogen 1.1 )

from bunsen-pipemenus.

^true. There's plenty of stuff to sort out as it is.

from bunsen-pipemenus.

^ Agreed. So I suggest to keep things private that don't need to be public :D

from bunsen-pipemenus.

What do you mean by private? Just use another branch, perhaps?

from bunsen-pipemenus.

Not in a library but in the files. No library. Like functions declared static in C. A bit unlucky choice of words on my side.

from bunsen-pipemenus.