Killer Feature?

[Derek Broughton]

Reinhard Tartler wrote:

> Derek Broughton wrote:
>>
>> I completely agree with you - both that whereami actually does this, and
>> that we need a gui config tool.
> 
> I also love wheremai, but, I'm a bit confused how you could have a
> graphical user interface to it without loosing too much functionality.

You've got two stages in whereami - detect where you are, and run
appropriate scripts for the location.  We already have GUIs to run
scripts - kcron and gcrontab do it for cron - so there's no reason that
part can't be under GUI control.  The detection is where network-manager
could be extremely useful.  I can imagine a tool that integrates a network
browser and lets you select an object you see in the browser, and tell
it "whenever this object becomes visible or disappears perform an action".

> The next step would be to call it in appropriate locations. For me, I'm
> using it from wpasupplicant action scripts, which suits me well. But
> even this isn't a standard setup.
> 
> I think we have 2 problems with this approach: Whereami needs to be
> integrated cleanly, and whereami needs to be configurable more easily.

Much as I like Whereami, I don't think it's the way to do this.  The
information needed should be available via dbus, and the gui tool would
have to figure out essentially what messages to watch for to meet your
requirements (e.g., if you're asking it to watch for a shared folder on an
SMB network, then it needs: a network interface, an SMB browse master for
that network, and finally that drive - some of that information will be
generated automatically, but some may require either polling or triggering
an exception action if an expected device is not found).
> Greetings,
> Reinhard

-- 
derek