[ptp-dev] Update

[Donny Kurniawan <donny.kurniawan@xxxxxxxxx>]

Some descriptions on old and new classes:

DebugProcess: The usual process object, it is linked to the PProcess

DebugProcessSetNamed: The usual process set, designed to be linked
with the process set in UI.

DebugProcessSet: The anonymous (nameless) process set , using BitList.
We have this, to avoid " DebugProcess [ ] ". In other words,
semantically speaking DebugProcessSet is the same like an array of
DebugProcess(es). However, it is not the same like the
DebugProcessSetNamed.

The external debugger (well, the AbstractDebugger) keeps and maintains
a list of PProcess(es) (referencing the PProcess(es) from the
ptp.core), i.e. the debug model, which gets updated (i.e. changed the
status to STOPPED, RUNNING, etc.) in response to the debug events.

Questions and Problems:

How does the Project (user-created projects) tie with the Runtime
model? It seems that the Project doesn't get passed to the
ModelManager. Shouldn't it be the case?

Still need to streamline the code



Thanks,
Donny