Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Fri, 4 Mar 2016 19:32:47 +0000

> On Mar 4, 2016, at 1:17 PM, Ralph Lange <[email protected]> wrote:
> 
> On 04/03/2016 17:38, Kasemir, Kay wrote:
>> [...]
>> Meanwhile, I’m not sure what to suggest:
>> Properly structure your display files because it’s the right thing to do, and accept that for some time it’ll be slow loading?
>> Or use a monolithic display file because that loads faster?
>> Maybe only optimize for speed on displays that are opened/closed a lot.
> 
> Could this "flattening" be done programmatically, so that you could "optimize" displays as part of the build or deployment, while keeping the original structure and waiting for a better world to arrive?

In principle, this could be done as a standalone student project in for example python.
The task is basically to read an “.opi” XML file,
look for each ‘linkingContainer’,
replace that with a ‘groupingContainer’  that holds what’s in the linkingContainer’s “opi_file”,
and save the result as the optimized display.

Possible issues:
The linkingContainer can scale itself to fit the content, or scale the content to fit the container, or leave all at the original size.
The groupingContainer would only allow keeping all at the original size.

You may also keep your *.opi files behind an http:// link, and linking containers again refer to an http:// link to always get the ‘latest’ files.
So now you’d have to run the flattening process on the client side to get the flattened file de jour, then open that locally.

Thanks,
Kay

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System