CSSTUDIO-2072 Modified and extended functionality to paste several PV names (with an optional display name) into the Data Browser

[abrahamwolk]

This PR implements point 3 described in the discussion #2972, i.e. 3. Modified and extended functionality to paste several PV names (with an optional display name) into the Data Browser. (The PR #2998 implements points 1 and 2 of that discussion.)

In particular, this PR adds a new context-menu item "Add PV(s) from the Clipboard" to the Data Browser that allows one to paste a collection of newline-separated PV names, optionally together with associated Display Names, into the Data Browser:

The collection of pasted PV names can either be added to one axis only that they share, or they can be given individual axes; the following is a screenshot of the dialog that is opened by clicking on "Add PV(s) from the Clipboard":

EDIT (30 July 2024): The PR has now been updated to implement the proposal described in #3057 (comment).

The the original parsing mechanism (that existed before this PR) is now used when parsing PV names, with one modification only: when encountering a single quote character ', the parser will continue to the matching single quote character ', in order to allow for spaces etc in display names; this is how double quotes " and brackets () were handled already.

PV names that start and end with single quote characters are interpreted as the display name of the preceding PV name (if it exists).

[georgweiss]

General comment: this cannot be fully tested unless #2998 is merged first.

In DroppedPVNameParser, should there be another case on top of \r\n, i.e. \n, or even System.lineSeparator()?

AddPVsFromTheClipboardMenuItem has hard coded message strings.

[abrahamwolk]

In DroppedPVNameParser, should there be another case on top of \r\n, i.e. \n, or even System.lineSeparator()?

Yes, there needs to be a case for \n also. Given that Phoebus can be used on several Platforms, and that files can be exchanged between platforms, both cases need to be accounted for; it would not be sufficient to check only System.lineSeparator().

[abrahamwolk]

After a more careful reading of the code, I think it already handles both the case \r\n and \n: if either of these characters appears, the parser stops parsing the display name.

I have now added labels for strings in AddPVsFromTheClipboardMenuItem to messages.properties.

The PR is ready for review again.

[abrahamwolk]

The PR has now been updated to implement the proposal described in #3057 (comment).

The the original parsing mechanism (that existed before this PR) is now used when parsing PV names, with one modification only: when encountering a single quote character ', the parser will continue to the matching single quote character ', in order to allow for spaces etc in display names; this is how double quotes " and brackets () were handled already.

PV names that start and end with single quote characters are interpreted as the display name of the preceding PV name (if it exists).

[shroffk]

I am adding this to the discussion topics for Sept 16th