more quick actions
minimize quick actions
Topic starter
In the context of version 12, we are going to rework the WebVue documentation, and in particular, I want to be able to deliver clean and clear indications about the support of SCADA Basic instructions when executed in a Web session. The summary of what is supported/not supported is being written/checked prior to being incorporated in the online help.
Apart from that we have been thinking about how to prevent people from designing an application that is not going to work in WebVue.
The last idea that popped up in my mind would be to invent a new, generic return code (say -1000), that would be documented as
Not implemented in Web session
or
Not supported in Web session
Something similar to the E_NotImpl we used to see in COM interfaces. You would know you should not used the instruction while you design/test your application in WebVue, on-the-fly.
What do you think ? What would be a good way to prevent people from designing application wrongly in this respect.
Regards
Posted : 06/09/2017 6:18 pm
I think it's a good idea.
Another idea: In Intellisense, using a color code indicating the instruction/mode is not available on a web session. I don't know if it is technically possible but using this way the designer will see during his development instead of seeing during his tests (meaning after development!).
Nico
Posted : 07/09/2017 8:04 am
I think it's two good ideas !
Posted : 07/09/2017 1:42 pm
Topic starter
Only 2 replies
Does it mean all other forum members are Ok with the level of information we have today ?
Never really knowing if a SCADA Basic instruction will work or not in a WebVue context is not an issue as real as I suspect ?
Posted : 02/10/2017 10:30 am
Good idea to have color code with intellicense. And if possible the same color code in the help too.
Qualification of version 12 will begin soon and I think testers and developers will have the opportunity to help.
Posted : 02/10/2017 1:28 pm
The list of instruction supported or not is in the help.
So I don't understand what you want to do.
Posted : 02/10/2017 3:05 pm
The idea, I think, is to make something better than a simple list lost somewhere in the help. It is very good to have it already but not enough.
It would be easyier to know on the fly if what we are coding is compatible or not. Color code seems to be convenient both in the scada editor and in the help (not everyone is using our editor). And a return error code specific in case of using non WebVue instruction in a WebVue context would be good too.
Posted : 02/10/2017 4:57 pm
Yes exactly,
Romain (and others) I give you a really basic example for your understanding.
The instruction BEEP
In the help it is written 'No limitations'
Ok but what happens when you run this instruction from a web session? Of course it beeps on the server and not on the client.
So, in my point of view, this instruction is not really available for a web session. By the way it returns always 1...
So, the job we are doing now is to check and list for each instruction and each mode the actual behavior and return.
Second step will be probably changing some behavior (i.e. for Beep => do nothing) and make a specific return for web station.
And, of course, update the Help.
Long job...
Nico
Posted : 03/10/2017 7:34 am
I understand, finnaly it means that Help have to be update by checking all scada instructions.
I think that put another color in intellisence can lose people which don't use WebVue.
Posted : 03/10/2017 12:48 pm