Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Thu, 10 Feb 2011 11:11:09 -0500

Hello:

For what it's worth, you can post CSS questions to the CSS mailing list
instead of tech-talk, but I'll reply where we started to keep the thread.

> I read the section "Use of dropins, direct plugin manipulations" (in
> http://sourceforge.net/apps/trac/cs-studio/wiki/UpdateRepository) and I tried
> to modify the config.ini file as explained but I still do not see my plugin !
OK, so at least we know that your plugin is simply not loaded, and then the
widgets in there will obviously also not be available.

Another for what it's worth: When I copy your
org.csstudio.opibuilder.widgetExample.SimpleBarGraph_1.0.0.201102091335.jar
that was part of the DebugInfo.zip that you emailed earlier into the
"dropins" folder of the SNS CSS product, it works just fine:
Show up under Help, About..., "Installation Details" button, Plug-ins,
and also shows up in the BOY palette.
Just your icon is about 2 orders of magnitude bigger than the usual widget
icons ;-)

Maybe, just to make sure, you try that as well:
Download the SNS CSS product, install your new widget into its "dropins"
folder.

If it works with the SNS product, but it doesn't work with the ITER product,
we know where to look next.

Things to do:
Check the log file (your workspace/.metadata/.log, or run with command-line
option -consoleLog), is there any error in there that might explain why your
plugin isn't loaded? Some missing dependency?

> I have a question regarding css installation for ITER project that I have
> (codac package): why is there 2 css folders and so 2 plugins?...
I don't know, ask the people at ITER who create that product.
But note that you have no "dropins" folder:
> [root@vmware-ezc css]# ll css
> total 404
> drwxr-xr-x 2 root root   4096 Dec 22 12:13 about_files
> -rw-r--r-- 1 root root    577 Dec  8 01:12 about.html
> drwxr-xr-x 3 root root   4096 Feb 10 15:52 configuration
> -rwxr-xr-x 1 root root  26949 Dec  8 01:12 css
> -rw-r--r-- 1 root root    148 Dec  8 01:12 css.ini
> -rwxr-xr-x 1 root root    112 Dec  8 01:12 css.sh
> -rw-r--r-- 1 root root   2972 Dec  8 01:12 icon.xpm
> -rwxr-xr-x 1 root root 332320 Dec  8 01:12 libcairo-swt.so
> drwxr-xr-x 4 root root  20480 Feb 10 16:15 plugins

The 'plugins' folder is managed by the P2 update mechanism:
It knows the versions of everything, it can install new stuff, revert back
to old version etc.
One should not manually fiddle with the plugins in there.
Manually added plugins are ignored on purpose, because P2 doesn't know where
they come from, when they were added, how to remove them, how to upgrade
them.

Instead, use a "dropins" folder that's meant for manually installed
additions that are beyond the control of the update mechanism.

Thanks,
Kay

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System