[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ptp-dev] Major breaking API change
|
HI Feiyi,
IJobNewProcessEvent and IJobRemoveProcessEvent are now called
INewProcessEvent and IRemoveProcessEvent respectively. These are made
available when you implement the the IJobChildListener interface.
For IJobChangedProcessEvent you have two choices. If you just want
bulk notification of the processes that have changed, use
IChangedProcessEvent. If you want notification of the attributes that
have changed on a particular process, use IProcessChangeEvent. The
former is available by implementing the IJobChildListener interface,
the latter by implementing the IProcessListener interface.
Greg
On Oct 10, 2007, at 12:03 PM, Feiyi Wang wrote:
Greg -
I have delayed the update from HEAD as I was working on the debug
launch issue. Now after the sync with head, as you mentioned, a
number of events gets renamed and reduced, but it is not clear from
the message on what replacement or venue should be, can you
elaborate more? Specially, the JobConsole can't resolve the
following the symbols, as they are gone.
import org.eclipse.ptp.core.elements.events.IJobChangedProcessEvent;
import org.eclipse.ptp.core.elements.events.IJobNewProcessEvent;
import org.eclipse.ptp.core.elements.events.IJobRemoveProcessEvent;
import org.eclipse.ptp.core.elements.listeners.IJobProcessListener;
Thanks
Feiyi
Greg Watson wrote:
These changes have now been committed. Please let me know if there
are any problems.
Greg
On Sep 29, 2007, at 9:29 PM, Greg Watson wrote:
Hi everyone,
I'm planning to commit a large number of changes to the PTP core
plugins at 5pm EDT on Monday. The purpose of these changes are to
improve the scalability of the model and the UI, particularly on
systems with large numbers of nodes, or when launching large
jobs. The changes are as follows:
1. Each model element can generate two types of event: child
events and element events. Child events are generated when any
child of the element is added/removed/changed. Element events are
generated when attributes on the element change. In the new
scheme, only a single child event may be generated, even if many
child elements are affected. This allows the resource manager
implementation to reduce the number of events that are sent, and
allows the UI to optimize how it displays the changes.
2. Rename/reduce the number of model events. There was
considerable overlap in the events that were generated by the
model, so these have now been consolidated. I've also renamed the
events and event listeners to better reflect their purpose.
These changes will mainly affect clients of the model (e.g. the
debugger). However, resource manager implementations will need to
update to the new interfaces. This was relatively painless for
ORTE, MPICH2, etc. so I don't expect any major problems with
other RM implementations.
If anyone has questions or comments, please let me know.
Greg
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev