-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen files for vme-300 EVM and EVR #187
Conversation
@agaget , could you test if it works fine for you? |
Thanks for adding VME. And the color doesn't work for me. Please use Macro and not directly color code. If you want a different color use your own color.def. |
My bad you have used macro, but it doesn't work for me either. The color def used is in the directory. To illustrate the difference: your bob and then mine If you want your read and write to use the same color, you can use in you color.def something like that |
HI @agaget , my bob looks like this. |
I just rebased my commits to the updated master branch and added the vme screens to the launch panel. |
opi/bob/evg/_evg_mxc.bob
Outdated
<height>19</height> | ||
<foreground_color> | ||
<color name="Write_Foreground" red="0" green="255" blue="255"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not the version of Phoebus that matter. Here the problem is that you've removed the macro Write_Foreground, same on different place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be something like this.
I guess I need to change the default background of the text input and text update.
Do you prefer the following style?
Do you have a specific background color for the text update and text entry? I am OK with any color as long as the contrast between the foreground and background is enough.
Thanks!
Ran Hong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we don't understand each other.
I don't care about the color, but I care about the respect of the color name macro.
As an example I use the file color.def there : https://github.com/epics-modules/mrfioc2/blob/master/opi/bob/color.def
If you don't know the color.def file, it's just a file where you define the code rgb of a macro. The advantage is that from a project to another if we have a different color convention, you just have to change your own color.def but not the bob files.
(the same exist with the font, but I don't use one)
In phoebus configuration file you can define which files to use there :
# Display configuration
org.csstudio.display.builder.model/color_files=color.def
org.csstudio.display.builder.model/font_files=font.def
org.phoebus.ui/welcome=welcome.html
I have tried in the color.def in the repo to be as close as possible as the standard name to be a maximum compliant with everyone
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HI @agaget ,
Indeed I didn't know that the default color can be configured in this way. I used the color.def from the repository and updated the foreground colors of the read/write fields.
Could you take a look at the commit that I just pushed?
Thanks for your instructions on defining the color macros.
Ran Hong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, the reason why I removed the macro Write_Foreground in the first place was that I planned to use the default color for the text entry, which is the macro "Text". My default color.def has different colors for read and write background colors.
I like the idea to have Write_Foreground and Read_Foreground, so people have more flexibility to make their own color schemes using color.def.
opi/bob/evg/evm-mtca-300.bob
Outdated
@@ -1162,10 +1133,6 @@ $(pv_value)</tooltip> | |||
<color name="Header_2_ForeGround" red="255" green="255" blue="255"> | |||
</color> | |||
</foreground_color> | |||
<line_color> | |||
<color name="Header_2_Background" red="114" green="159" blue="207"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You've removed all the "Header_2_Background" please put it back.
Otherwise It uses the Macro "Grid" by default.
You can use
Header_2_Background=Grid in your color.def if you prefer the original Grid color.
If you can be compliant with that in your VME bobs, it would be perfect too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add back the foreground_color section:
<foreground_color> <color name="Header_2_ForeGround" red="255" green="255" blue="255"> </color> </foreground_color>
The line_color section causes an error while loading the screen.
<line_color> <color name="Header_2_Background" red="114" green="159" blue="207"> </color> </line_color>
After saving the screen I found that cssphoebus removed this section. Seems that the group widget does not have a property line_color.
I just updated the screens so all groups have the Header_2_ForeGround as the foreground_color.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line_color was added by a student of us few month ago, I think you are not using the last version of Phoebus. I am using Phoebus v4.7.4.
I should indicate the minimum version of the bob in the README
opi/bob/evr/_evrdlygen.bob
Outdated
@@ -14,10 +13,6 @@ | |||
<x>86</x> | |||
<width>37</width> | |||
<height>19</height> | |||
<foreground_color> | |||
<color name="Write_Foreground" red="0" green="255" blue="255"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here please for Write_foreground
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done in the last push.
For now still too many modifications that break previous installations. Also you've change witdh for some bob. It messes up all the other bob using them. Example for _evroutput.bob but I spot problems for other In MTCA EVR then and now |
Probably it is easier for me to keep all the files used by mtca systems intact. If I need to adapt any subscreens to the VME system, I will add a separate file. I will make this change today. |
@agaget I just reverted all the files the mtca screens are using. Now in the file list there are only new files except for the launcher. |
54be3e9
to
61b2e0a
Compare
@agaget I just updated the files I added for the VME cards. Now the evg-seq and evr-expert files can be shared. Best regards! Ran Hong |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems nice to me !
Thanks for complying to my requests :)
@jerzyjamroz I let you merge then ? |
My pleasure to learn the way you handled the screens. At APS, people have been using another color scheme for a long time. With the macros it will be easy to adapt to that scheme. |
1: Some of the existing screens (mostly subscreens) are updated: fixing version compatibility, color and size
2: Added screens and subscreens for evm-vme-300
3: Added screens and subscreens for evr-vme-300
The screens for the mtca cards are mostly intact. I made minimal size adjustments to make things fit.