jay (support) wrote:Benjamin, we understand very well what the API provides, what we'd like it to provide, and the gap between.

If I create a plugin, the user needs someway to get that information....

The bottom line is this: state information can be accessed. Perhaps not as conveniently as some might wish but it's there and accessible. Holding back useful functionality (like enabling the built-in controls of subclassed devices) because it may hide informational state information, which is already fundamentally hidden in Indigo Touch/IWS seems quite counterproductive to me.

And, just as a reminder - you can create clipping files with control pages in them to distribute to your users if you choose. Again, it's not the perfect, but it's available (no need to whine about the limitations/problems with it - I'm just pointing out something that might help).

Jay,

I disagree. User's had enough problem with the Applescript Security Script, and while there have been huge steps forward with the v5.x upgrades that make Switchboard significantly easier...

I can't imagine the difficulties of supporting users trying to copy IWS control pages from a clipping file would entail.

I want to use more of these features.... For example, Inside of switchboard is a prototype Security Control panel.

But I am concerned about ease of use issues for the end-users. I can't see adopting a feature that will involve the user having to do complex setups, since I know from the Security Script that'll end up with me crying in my Coca-Cola.

Right now, I have several users complaining that Switchboard is too complex, and they can't understand it... I am tempted to ask them to install the Classic Security script as a comparison....

I am targeting my plugins to be accessible to the average user, and trying to keep the complexity of the install down.
If that means certain features have to wait to be introduced to the users, then that is what I will do...

- Ben

So would it be inappropriate to make a Tron reference here?

Ben: "I fight for the users!"

Ok, ok, I'll shut up now. I know when I'm out of my league.

Gosh, guys, didn't mean to start a WAR... just making the comment that for some plugins with a lot of obscure states (NOAA plus has what? 50 or 60 at least, and I've got several for friends who live in various areas of the state) it'd be nice to be able to look at some of them remotely, even though the hassle of putting them ALL into a control page or variable folder would be prohibitive. If I ever get the time to learn plugin architecture well enough (as Jay knows, I'm still asking newby questions), I may write a "Display Device State" Plugin that has two States: "Device ID" and "DIsplay State Name and Value" and two actions: "Step Down List" and "Step Up List" to move from state to state. Then I can create one of those for each Device I want to watch and drop 3 items referenceing each of them on a control page: A display State text field, button for next state and button for previous state, letting me walk through every "state=value" of the device I'm interested in....Probably still not user friendly enough for nongeeks, and still no ability to CHANGE anything, but a lot better than what I'vew got now.

johnpolasek wrote:Gosh, guys, didn't mean to start a WAR...

Not a war.... And I should say that I have different opinions on priorities, Matt & Jay and doing fine with Indigo.

My patience isn't doing to well, since Real Life (TM) has real dealt my family a big blow. For the last year, my sister-in-law and her two children have moved in with us due to their father dying....

So I've had a hard time finding time to program and so forth... So I'm a little edgy lately...

But we're working on retrofitting the basement into living space for them....

But I'm looking into the web page issue with FMID, and looking to put out a switchboard update soon...