Re: [sr-dev] [kemi] porting module functions with input/output PV parameters

2017-01-13 Thread Daniel-Constantin Mierla
On 13/01/2017 17:30, Mititelu Stefan wrote: > >> 1. What would be the best practice for porting module functions >> that read/write data from/to a pseudo-variable? ...At the moment >> I'm thinking of using str for input and return; probably this >> will lead to partially duplicati

Re: [sr-dev] [kemi] porting module functions with input/output PV parameters

2017-01-13 Thread Mititelu Stefan
> > 1. What would be the best practice for porting module functions that > read/write data from/to a pseudo-variable? ...At the moment I'm thinking of > using str for input and return; probably this will lead to partially > duplicating the code of the existing module functions. > > > The idea is to

Re: [sr-dev] [kemi] porting module functions with input/output PV parameters

2017-01-13 Thread Daniel-Constantin Mierla
Hello, On 13/01/2017 15:30, Mititelu Stefan wrote: > Hi, > > I've been reading about new kemi interface that will be available in > 5.0. Writing configs in lua/python is awesome!!! and javascript via app_jsdt to make it more awesome for the internet world :-) > > I am currently looking into and

[sr-dev] [kemi] porting module functions with input/output PV parameters

2017-01-13 Thread Mititelu Stefan
Hi, I've been reading about new kemi interface that will be available in 5.0. Writing configs in lua/python is awesome!!! I am currently looking into and trying to add kemi support for a module and have some questions: 1. What would be the best practice for porting module functions that read/wri