Date of Meeting: 18th July 2000

Present: S.Jackson, G.Morpurgo, V.Paris
Excused: G.Crockford, M.Jorda Garcia

OP Frame
Stephen presented a first version of OPSkel, extension of JFrame.
This OP Frame has
    --> a minimal menu bar on top
    --> a bottom bar containing
            - 'Msg' button, to show messages
            - Text field, to show the program status, the foreground color depending on the type of status (ready, busy, error, ...)
            - 'Activity' image, which can flash while the program is busy performing an action.
                There could be a time out parameter added to the method which starts the flashing.
    --> several standard dialog boxes popup-able at the application level.

Example program
Mani began to build an example of 'SL Equip State' application.

Actions

• Continue with OPSkel.
• SL Equip State application.
• How can we share StOpMI files and make them accessible from PC and HP ?

Date of Meeting: 13th June 2000

Present: S.Jackson, M.Jorda Garcia, G.Morpurgo, V.Paris
Excused: G.Crockford

OP Beans
OPBeans can be composite elements, containing several simple components.

Callbacks
Mani presented several options for Actions files:
    - one Action file per type of OPBean
    - one Action file per OPApplication.
Another possibility would be to provide
    - one Action file per part of application, i.e. per panel.

Actions

• Strategy for Callback attachment : try one Action file per panel.
• OPFrame.

Date of Meeting: 29th May 2000

Present: G.Crockford, S.Jackson, M.Jorda Garcia, G.Morpurgo, V.Paris

OP Beans
A first version of the OPLookAndFeel is done and most of the basic components are defined.
We should now work on how to attach Callbacks. The strategy should not depend on the IDE tool.
We must also define how to connect OP Beans.

Actions

• Strategy for Callback attachment.
• Demo program.

Date of Meeting: 16th May 2000

Present: G.Crockford, S.Jackson, M.Jorda Garcia, G.Morpurgo, V.Paris

OP Beans

• Default colors for all OP Beans will be provided by the OPLookAndFeel.
• The users might be able to define their private pallette with 'sub-classes' of our OP Beans.

• We could add some button to watch the state of the application.

• Continue to define the OPLookAndFeel.
• Continue to define OP Beans.
• Definition of an OP Frame.
• Build a demo program to be shown and demonstrated regularly to the OP specialists, for feedback.

Date of Meeting: 2nd May 2000

Present: S.Jackson, M.Jorda Garcia, G.Morpurgo, V.Paris
Excused: G.Crockford

OP Beans

• The OPLookAnd Feel is being defined.

• Two classes are created, one for the Application and one for the Frame.
• Examples ( 1 and 2 ) assembling different OP Beans in an OP Frame have been shown.

Milestone plan

For the time being, Mani is the only one who works full time on the project. We have to be more realistic and postpone the end dates.
The Milestone Plan has been reviewed, and the Responsibility Chart accordingly.

Actions

• Definition of the basic OPLookAndFeel for OP Frame and all OP Beans.
• Improve existing OP Beans and create more.
• Definition of default actions performed by the OP Beans.

Date of Meeting: 10th April 2000

Present: S.Jackson, M.Jorda Garcia, G.Morpurgo, V.Paris
Excused: G.Crockford

OP Java Frame

• An application Frame would fill the whole space left by the console manager on the display.
• There will be a Status Bar at the bottom and a Message window. Both could be hidden.
• A Menu Toolbar will contain commands acting at the application level, and, being eventually common to all applications. Could be hidden.
• A 'busy' image, which can be flashing, at a defined place in the frame, should be available.

• SPS and TZ selections could be considered as OP Java Beans and possibly be embedded into applications.

They could enforce the selection to be global for all applications running on that console.
• A 'busy' Java Bean would make an image flash a number of times (or for a certain time), and then raise an exception.

• Build prototypes for existing applications -> Stephen and Mani.
• LEP Orbit (contact  person : Jorg Wenninger)
• LEP RF (contact person : Mike Lamont)
• Transfer Lines Trim (contact person : Véronique Paris)
• The Milestone plan will be reviewed -> Véronique