Now I know how to make plug-ins so… you can probably guess the rest.
http://github.com/skurfer/Viscosity.qsplugin/downloads
--
Rob McBroom
<http://www.skurfer.com/>
The magnitude of a problem does not affect its ownership.
i have many servers on my viscosity list and the menu bar icon does
not show me what's currently connected unless i click on it.
> nice and i can confirm it works but how about a disconnect/connect
> action without selecting a specific server? the disconnect could just
> apply to whatever connection is on and the connect, if without a
> specific server, would connect to the last connection used.
Oh, believe me, I’ve thought about this. I just haven’t discovered a reliable way to query the application to find out it’s current state. It’s AppleScript library provides only “connect” and “disconnect” and they require a specific connection name.
The last connection used thing might be possible, so long as it was “used” via Quicksilver because again, I’m not sure how you would get such information directly from Viscosity.
If anyone has suggestions/experience related to getting such information, I’m listening.
--
Rob McBroom
<http://www.skurfer.com/>
It's not that I think guns, drugs, prostitution, swimming, eating and reading should be legal. It's just that no one on Earth has the authority to make them illegal.
> Does Viscosity keep track of its recent connections in a plist file
> somewhere?
I can’t find such a plist, and since the application itself provides no UI for recent connections, my guess is that it doesn’t track them.
There is `~/Library/Caches/com.viscosityvpn.Viscosity/Cache.db`, which may be of use, but I don’t know what format that’s in or how safe it is to mess with. I’m guessing it’s SQLITE3 and that read-only queries wouldn’t hurt anything, but I haven’t tried to verify either of those assumptions.
> hows it going with this plugin? i've recently restarted using it. pretty useful although that inability to get to recent connections quickly would have been nice to have.
It’s going well. I mean, it’s complete as far as I’m concerned. :) Like I said before, Viscosity has no concept of recent connections so there’s no way the plug-in could access them.