support multiplicity of QA

[10der 832]

Hey, @m.roszak @A.Socha

some many times ago i am asking about how to support N similar (copyes) QA devices.

So, when user has 15 QA devices (for example it's a HVAC) and i provide a new functionality or fix a bug in QA.

now user sequentially open on the edit all 15 QA and clrt+С / ctrl+V 

it's annoyed, especially when user with no experience. 

 

you said what you thinking about this case.

and what now?

 

PS: we are asking also a make shared libs. It's was when no HC3... it was when HC2 in production. and also you ignoring... no make a sharable libs for QA

[jgab 2,642]

41 minutes ago, 10der said:

Hey, @m.roszak @A.Socha

some many times ago i am asking about how to support N similar (copyes) QA devices.

So, when user has 15 QA devices (for example it's a HVAC) and i provide a new functionality or fix a bug in QA.

now user sequentially open on the edit all 15 QA and clrt+С / ctrl+V 

it's annoyed, especially when user with no experience. 

 

you said what you thinking about this case.

and what now?

 

PS: we are asking also a make shared libs. It's was when no HC3... it was when HC2 in production. and also you ignoring... no make a sharable libs for QA

One could make a master QA that spawns 15 child QAs - then only one QA to update.

However, integrated with the marketplace it would be nice with an upgrade mechanism/schema.

Multi-file QAs solves some of the library wants.

...sorry, I know you didn't ask me  

[rangee 32]

I agree whit you 10der

 

In my case lot of QA uses same "SOMECODE". When I edit "SOMECODE", ZBS edit all of QA which contain "SOMECODE".

It's very inconvenient and  wasteful.

 

upload someting.lua  and dofile("something.lua") will solve this.

[petrkl12 228]

The native support for QA auto update could be cool but you have some examples how to do it even with current QA ie. ER4 from @jgab

Also better strategy is creating master QA with child QAs with less memory/cpu consumptions…

[BlueSmurf 0]

My vote: Add Git support to the HC3.