Planning

= Planning = Each site should put a list of items they want to get done. Item should be as specific as possible, and they can be grouped into category with a brief preamble. Each item should bear a MH (Must Have), SH (Should have) and NH (Nice to Have) to rate the relative degree of importance of the items to the site.

== BNL ==

Infrastructure

• (MH) Review main page so that it formats properly (currently main part may go below side menu)
• (SH) Better way to handle external library dependency
• (NH) Investigate maven based build
• (SH) Review help system

Standardize on features - review features to make them as much as possible usable out of the box by a product developer and by a user with a generic Eclipse RCP platform.

• (NH) Create a single "Epics 3 support" feature that enables epics for all data providers (DAL, utility.pv, PVManager). The current support for the protocol must be included ad-hoc for every provider by including it in the product. There is no way that a user (non/developer) can select the applications and the protocol he needs from an update site. Given the multiple providers, that the user should not be aware of which ones each application uses, and the limitation of the eclipse plug-in system, we propose that the features install all plugins for all data providers, even if not installed. At runtime, the unused plugins would not be activated. Note that this does not preclude a product developer to avoid using these feature and referring directly to the plugins.

CSS Build.

• (SH) incorporation of unit testing into the headless build process.
• (NH) source gathering directly from mercurial repository.

PVManager

• (MH) Interface to write data (right now, limited to monitors)
• (SH) Debug plugin to see the status of data source connections

Displays and Widgets

• (SH) Display that can display a multiple waveform (including data composed of two waveforms, data + displacement), with linear/cubic interpolation
• (SH) Widget to compare waveforms of setpoints and readbacks
• (NH) 3D waterfall plot
• (SH) UI to change the color scheme of waterfall plot
• (MH) Better integration of waterfall plot (Widget in BOY, object contributions)

== SNS == === Product Modularization === The SNS, BNL and KEK products are very similar. For the KEK product, the code that is common with SNS (and 99% BNL) was copied into org.csstudio.utility.product

Can that be shared between KEK, SNS, BNL, others? If not, what's missing?

=== Live Data Interface ===

• (SH) Transition from utility.pv to PVManager? What about data types? Right now, util.PV and archivereader are very convenient because they use the same data types. Is it useful, possible, easy to convert existing code to PVManager?

=== BOY ===

• (SH) Web viewer for display files (RAP, possibly limited to read-only PV access)

=== BEAST === See [wiki:BEAST_Plans]

• (MH) Better communication between separate setups
• (MH) Dialer
• (NH) phone system

== DESY ==

=== Infrastructure / Platform ===

• (MH) Remove unwanted GUI components: Move 'Statistic View' in new plugin, Remove 'Authorize IDs' menu entry (Done)
• (SH) Make platform independent from DAL (Most likely solved by modularization of core components)
• (SH) Remote Management: Adjust remote management plugins for new ECF 3.4 version. Remote update via P2 should also be possible.
• (NH) Move test code in fragments that the CSS product holds only production code.

=== BOY / SDS ===

• (NH) Common widget library

=== Build ===

• (MH) Run JUnit and Plugin tests in headless build. (Buckminster?)
• (NH) Migrate from Hudson to Jenkins

=== PUSH ROUTINE ===

• (MH) Establish pre-push hook aborting push on failed tests and increased CS and FB warnings.