Script to upgrade opi file from previous versions to the newest.

Define extension points to handle the creation, submission and display of properties associated with log entries.

Add scrollbar to list selection widget
Enable double click move
Image stack should work with InputStreams

Auto complete is great but can be sometimes irritating as Word could be when it formats things for you!

So, trying to be more user friendly, we would like to propose something more Google like. Let’s see what it means.

From Chrome URL field on a new Tab, I start to enter “new”:

The highlighted line below represents what will be selected if I press Enter – it is also the string in the URL field. If I continue “new y”, then “new York” is proposed and automatically completed. This becomes the “Google Search” and “new y” appears only as second choice:

If I lose the mouse focus, the completed Google Search becomes the current value:

In CSS, we could do the same. I start to type the beginning of a PV Name (No History for now) as “UT” and the db parsing find that the closest match between standard separators is “UTIL-“:

If I want to append what has been proposed, I just use the arrow -> or End key and I continue to specify my PV Name. If I use Backspace or Delete key, it has the same effect as using the down arrow and selecting “UT”.
So I enter my PV Name piece by piece:

What happens if the completion could not be done because more than one option is possible. With Chrome, the possible choices are listed but there is not automatic completion and the highlighted line represents what I have entered (and no more than that):

I cannot make any screenshot for CSS as it is not working properly for now… But the idea is that I have for example “UTIL-xxx” and “UVAC-yyy”. If I start typing “U”, “UTIL-“ and “UVAC” would be proposed but none of them will be selected. I will have to use the down arrow key to select “UTIL-“ for example or continue to type “T”.

It was decided "Expression".

Modify current Tooltip property so it can also accept OPI path and macros.

Double click display will create a label and waiting for inputting text. If no text is inputted, no label should be created.

This may reduce the the confusing of too many widgets.

The image attachment are not correctly initialized leading to the empty buffer being passed to the widget.

With the adoption of the new PV field format, there needs to be some policy on how to handle backward compatibility for existing screens/configuration files.

Move widget from apputil.ui and logbook.ui
Start deprecating apputil.ui

Hide color depth if its not in RGB mode. Make them unconfigurable in runtime.

This could provide all the features as SWT Grid layout

This can help to create a label for a widget very easily. It will popup a dialog to ask for label name and position.

For example, select the grouping container or display that contains current selected widget. If use shortcut multiple times, you can finally select the display.

This should include the wiki, and should be cleaned up for new release process.

Also, add a compatibility list for each release.

Updating issue

An arrow angle or arrow height option for polyline.

With the move to PVManager which supports formulas a new format needs to be created.

How to handle chars which have meaning in formulas.

Unique identifier preceding formulas:
ca://ab-c
=‘ca://abc'-'ca://def’
=query(“ab*”)

The container will become a PV array provider, so all its children PVs can be passed to another application. For example, export the PVs to a text file. Show all the PVs in PV Table.

Reload the OPI just like reopened the OPI so disconncted PVs can be connected.

Requested from ITER:
One use case is for example, to look for which opi and which widget use this PV. For now, the search feature just show the list of opi files, but when you double click on one of the files, no widget is preselected. It should be good to select the first one that is using this PV.

If there are only native widgets, the OPI will only paint once on startup. But the native widget may loaded later, so it may miss its first update to locate the native widget.

For large amount of data, it may be faster to draw data on an image first and then draw the image at once. Need to investigate this possibility.

The files ALARM_MYSQL.sql and MYSQL_USER.sql have inconsistent casing on the database name (ALARM vs alarm).
This means it does not work on Linux unless the casing is changed to be consistent across both files.

The agree behavior for OPI file upgrades:

• Be able to run old boy opi xml versions,
• Save as new format (and no longer can read from old boy version)

Script programmers will be responsible for reading the compatibility document for the release/upgrade, and fixing their own scripts.

Warnings in console for ‘pv {"longString":true}’ not being used, but still write String to byte[]; warn but still support writing Integer[] to double[].

This warning should be kept for one version, then fail in the next version.

BOY Proble OPI should supports displaying waveform as string.

Important fix for parsing query string