The next step toward completing RCP DtaQ Demo is to provide the User Interface (UI) to the demonstration model, that is a GUI to enter the values for the input data queue. To do this means adding support for the model input data queue and an EditorPart for the user to enter the instruction and message to send to the model running on the System i.
This is what it looks like:
View image
... Read the rest of entry >>
Posted @ 06/19/2007 5:48 PM By Bill Blalock
• • •
RCP DtaQ Demo's "preferences" are hard-coded into Me.java. Remember that class from 101? The stuff which varies for each System i -- where the system name or IP address and data queue paths were defined? It would be nice if the user could change that instead of having the programmer modify and compile Me.java. A preference page would look like this:
Lets do it.
... Read the rest of entry >>
Posted @ 06/10/2007 8:30 PM By Bill Blalock
• • •
You can't use WDSCi 7 (Version 7 of Websphere Development Studio Client for System i) to develop RCP applications -- at least not without making compromises.
Close but no cigar. Maybe next time around.
This information is directly from IBM (the first two points), the result of two PMRs.
1. The javadocs for SWT and JFace are not included to save space.
2. The source for Eclipse is not included for legal reasons.
IBM / Rational doesn't knows what all the effects of leaving out the Eclipse... Read the rest of entry >>
Posted @ 06/03/2007 12:23 PM By Bill Blalock
• • •
Elena Lower wrote an article published this month in System iNEWS, ProVip (May 2007), "5 Tips for Integrating Java with System i Resources". RCP DtaQ Demo project will benefit from the first tip, Connection to the System i. Lets apply it:
These changes give RCP DtaQ Demo a logon dialog consistent with the graphical appearance of the application and is more functional. The user can cancel the logon without ending the application and later call for the logon dialog through the file... Read the rest of entry >>
Posted @ 05/31/2007 7:40 PM By Bill Blalock
• • •
Typically a rich client does not have console output. The classes brought over from Java data queue 211 write their output to stdout. They were designed for a Java command line or console application. RCP DtaQ Demo will be modified to eliminate the console output and use the rich client user interface (UI) and log file. When finished the application would look like this:
- No console output
- The messages are written to the View (think subfile).
- The status line is used to alert the... Read the rest of entry >>
Posted @ 05/13/2007 11:00 PM By Bill Blalock
• • •
This exercise builds an RCP application which monitor's the output data queue of the demonstration model. Eclipse RCP wizards are used to create an RCP application with a view that contains a table, the table shows a String[] with the values "One", "Two" and "Three." This blog entry shows how to run the wizards and modify the code generated by the wizards, and how to use the data queue classes created in Java data queues 211 blog entry.
The RCP application looks like when it first starts... Read the rest of entry >>
Posted @ 05/06/2007 7:00 PM By Bill Blalock
• • •
Now we have a
- demonstration model for MVC running on the System i written in RPGLE
- demonstration view-controller for MVC on the System in written in CL
- demonstration console based view-controllers for MVC written in Java which locks the application while waiting to read the output of the model (DtaQExample1 and 2)
- demonstration console based view-controllers for MVC written in Java where a Thread waits to read the output of the model (DtaQExample 3a, 3b and 3c).
What about Eclipse and... Read the rest of entry >>
Posted @ 04/29/2007 6:00 PM By Bill Blalock
• • •
A previous blog entry "Java data queues 201 -- the thread side of a thread based console application view-controller for System i demonstration model" solved the problem of the java application being stuck waiting to read a data queue by putting the read data queue part of the program into a separate thread. Each time a data queue read occurs the thread fires a PropertyChangeEvent. The event contains the information read from the data queue.
This blog entry address the rest of the example... Read the rest of entry >>
Posted @ 04/21/2007 1:00 PM By Bill Blalock
• • •
WDSc 7.0 has been available for a month now and it lives up to the expectations. System i Network has articles on the new version and more are on the way.
WDSc 7.0 can be used for Rich Client Platform development! The prior version of WDSc (6.01) did not completely support RCP development because it was based on Eclipse 3.0 and RCP development really needs Eclipse 3.1. WDSc 7.0 is based on Eclipse 3.2.1 ... close enough!
The RCP introductory tutorials which used Eclipse 3.2.x can now be... Read the rest of entry >>
Posted @ 04/15/2007 12:00 PM By Bill Blalock
• • •
The prior blog entry presented a Java console application which performs the same function as the CL view-controller -- write a data queue then read. The examples used the techniques covered in IBM's documentation. That was a starting place -- putting the classes explained in the Java toolbox documentation into a console view-controller.
The write-then-read pattern does not work for GUI clients. The desktop application has to be free to service inputs from the user while waiting for the... Read the rest of entry >>
Posted @ 04/08/2007 8:00 PM By Bill Blalock
• • •