Supporting/Expanding comment:
There are several bugs I've encountered which need to be
thought about to support upgradability:
1-the entire classpath of figures is coded into the .draw file
so it's not possible to re-package figures without making
old .draw file unreadable.
2-the IOException doesn't indicate which class is attempting
to read what type of value and the visitor pattern means
that the information is easily lost as the stack unwinds until a
suitable catch clause is found.
Requests 962391 and 962395 are larger issues but very
related to this problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JHotDraw 7 provides a new API named DOMStorable that fixes many shortcomings of the Storable API.
I suggest dropping the old file format in favor of DOMStorable, and implementing InputFormats for reading legacy .draw files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1043393
Supporting/Expanding comment:
There are several bugs I've encountered which need to be
thought about to support upgradability:
1-the entire classpath of figures is coded into the .draw file
so it's not possible to re-package figures without making
old .draw file unreadable.
2-the IOException doesn't indicate which class is attempting
to read what type of value and the visitor pattern means
that the information is easily lost as the stack unwinds until a
suitable catch clause is found.
Requests 962391 and 962395 are larger issues but very
related to this problem.
Logged In: YES
user_id=940971
Originator: NO
JHotDraw 7 provides a new API named DOMStorable that fixes many shortcomings of the Storable API.
I suggest dropping the old file format in favor of DOMStorable, and implementing InputFormats for reading legacy .draw files.