[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] JavaModel on Eclipse start/stop
|
The model is not persisted across session, it can lazily be reconstructed
from underlying resources.
It is the responsibility of a client to save transient elements, such as
working copies (e.g. save editors before exiting).
The package explorer is rendering the model in the UI. UI is persisting the
rendered tree by asking each element it cares about for its memento.
A memento can be converted back into an element in the next session (again
on UI request).
A memento is nothing more than a string representation for a Java element
handle (i.e. pretty much a path to a given Java element, nothing about
actual contents).
Cristian
Amitroaie
<cristian@xxxxxxx To
> jdt-core-dev@xxxxxxxxxxx
Sent by: cc
jdt-core-dev-boun
ces@xxxxxxxxxxx Subject
[jdt-core-dev] JavaModel on Eclipse
start/stop
12/08/2005 01:19
AM
Please respond to
"Eclipse JDT Core
developers list."
Hi,
I started to develop a plugin for some language in Eclipse and one of
the
main sources of inspiration is JDT/CDT.
I browsed a lot through the sources and I got stuck with the JavaModel.
I
do not realize where it stars and were it ends. CDT seems quite a
copy/paste
so I am lost there too.
For now, a concrete question: What happens between two Eclipse
invocations?
How is the model saved/restored? In other words who handles the
persistence,
if any?
Thanks, Cristian
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
