ticker, selector - save it as an argument?

[brobee]

Hi Guys,

Is it possible to implement a selector/ticker in bitbar? My idea is to run a script on different servers with different functions Let's say in the menu, there is an environment submenu with 3 options. I select dev, it saves and I can select the function, for instance build and it initiates my bash script. Optional: input is possible in bitbar?

I use bash, but py would be fine as well, but without any example I'm totally stucked.

echo "environment" echo "--dev" echo "--dev2" echo "--dev3" echo "action" echo "--build | bash=/Users...../bla.sh terminal=false" <= I can modify the script to read the arguments, but I need to pass here them. echo "--unitTest | bash=/......"

Thanks!

[gingerbeardman]

You could read/write a config file.

Read on script run. Write on menu item selection.

[brobee]

Thanks for your comment. Can you please provide a short example?

[gingerbeardman]

Here are some that do that kind of thing:

• PHP https://github.com/matryer/bitbar-plugins/blob/master/Dev/GitHub/github-ci.1m.php
• Python https://github.com/matryer/bitbar-plugins/blob/master/Web/Reddit/redditnotify.30s.py
• Ruby https://github.com/matryer/bitbar-plugins/blob/master/Weather/metar.5m.rb
• Shell https://github.com/matryer/bitbar-plugins/blob/master/Network/wireguard.sh
• Shell https://github.com/matryer/bitbar-plugins/blob/master/Dev/Kubernetes/minikube.5s.sh
• Shell https://github.com/matryer/bitbar-plugins/blob/master/Music/music-controls-playpause.10s.sh

[brobee]

I found a workaround with submenus using "----", so ticker/selector is not mandatory. (In the example files, I don't see selector and variable assignment)

Anyway, If I have a shell function, is it possible to call that or it works only with individual files?

For instance, it requires files, not functions. echo "--build | bash=/Users...../bla -> echo "--build | bash=bla" bla is a normal function in the same shell file.

[gingerbeardman]

You seem to be thinking about the script as only bitbar commands that you have to squeeze everything into. This is not the case.

You have the complete freedom of a shell script, part of which will generate the bitbar menu. So I would write the script as you need it, with conditional logic for branches, and then when it's working add in the bitbar stuff for "user interface".

If you need help beyond this, you might have some response at StackOverflow.

I'm closing the issue, but feel free to keep in touch here.