• The Milestones plan and the Responsibilty chart have been modified.
• A Web page is under construction for the User Guide.
• A prototype is being built for CESAR project.
• The tool installation is under way. Mani is creating an installation script.

• StOpMI  folder on a PC/Linux.
• ORACLE access to build lists.

• Should the stopmi.<method>s be recognisable, e.g. containing "OP" in their names ?
• Tabs for multi-panels ?
• Do we need a "Back" facility to return to the previous GUI state ?

Date of Meeting: 24th October 2000  Present: Mani, Veronique

• Preparation for Demo #2 (on Thursday 26).
• Discussion about tests with Chart & Table from PS/CO.

Date of Meeting: 17th October 2000  Present: Mani, Veronique

Mani presented a proposition for Inter-Panel connections.

Question
Should the stopmi.<method>s be recognisable, e.g. containing "OP" in their names ?

Meetings
StOpMI meetings will take place every Tuesday at 10h30 in the Pavilion.

Actions

• Prepare Demo #2.
• Try JClass Chart from the PS/CO server.
• ORACLE access to build lists.

Date of Meeting: 3rd October 2000
Present: M.Jorda Garcia, V.Paris

OPSkel
An optional toolbar has been added.

OPLookAndFeel
A more complete one has been implemented.

OPBeans

• Tabs for multi-panels have been proposed.
• Do we need a "Back" facility to return to the previous GUI state ?

Actions

• Demo #1 for OP  on Thursday 5 October 16:00.
• Negociate with KL-Group for an offer concerning JClass Chart ByteCode.
• StOpMI  folder on a PC/Linux.

Date of Meeting: 12th September 2000
Present: M.Jorda Garcia, G.Morpurgo, V.Paris

OPBeans

• The OPBean class has been removed. The OPBeans now inherit from the basic Java component classes.
• The KL-Group offer for JClass Standard Suite (SourceCode) is much too expensive, another offer (ByteCode) will be asked for.

The definition of the OPGeneric files included in these slides can be seen in the following JavaDoc. The source code of two action files from the implemented example can be checked as well.

Team work

• A PC/Linux with 512MB will be installed in the Pavilion and dedicated to StOpMI. It will contain all the files we want to share for development.
• A PC/WindowsNT will be installed next to this PC/Linux for demos and eventually development.

• Ask KL-Group for an offer concerning JClass Standard Suite (ByteCode).
• StOpMI  folder on a PC/Linux.
• Organise a Demo for OP  (probably Thursday 5 October p.m.).

Date of Meeting: 1st September 2000
Present: G.Crockford, S.Jackson, M.Jorda Garcia, V.Paris

OPBeans

• The KL-Group Table is being tried and seems appropriate.
• KL-Group will be asked to make and offer for JClass Standard Suite (SourceCode).

• Problem in applying the OpLookAndFeel: to be looked at.
• An example will be presented to OP specialists beginning of October.

• PC/WindowsNT computers are presently used by the team. We could also try with PC/Linux.
• A folder on PC/Linux could contain all the files we want to share for development. This folder would be accessible from PC/WindowsNT through the SMB protocol.

Back to the objectives
We will provide a tool to build applications having user interfaces of the same style, simple and uniform :

• OPSkel for the frame.
• OPBeans
• Java basic components with access to a limited number of properties
• and eventually a few composite beans re-usable by several applications.
• Action attachment .
• OPLookAndFeel applied to the whole.
• A User Guide.

• Ask KL-Group for an offer concerning JClass Standard Suite (SourceCode).
• StOpMI  folder on a PC/Linux.
• Apply the OPLookAndFeel.

Date of Meeting: 4th August 2000
Present: S.Jackson, M.Jorda Garcia, V.Paris

OPBeans

• Get<component>  methods are being implemented to provide access to all the properties&methods of the Java basic components.
• The Table OPBean has to be completed. We will try the KL-Group Table bean first.

Actions

• Apply the OPLookAndFeel.
• Ask for a license to try KL-Group beans.