Re: [mylar-dev] task list externalization

[Eugene Kuleshov <eu@xxxxxxxx>]

Wim Jongman wrote:
> I have been meaning to ask this. Why not use EMF for serialization?
 One reason is to not introduce additional dependency. Another reason, 
that it is quite possible that xml was a temporary option.

 Actually, I am now more leaning toward the idea, that all 
ITaskListElement subclasses should have common abstract class with map 
of attributes (something similar to how repositories are handled). Then 
we can eliminate all externalizers completely because code will be generic.

 regards,
 Eugene


> Eugene Kuleshov wrote:
> >  While I am in an enthusiastic mood, I'd like to suggest to make some 
> > changes in ITaskListExternalizer API that need to be done before 1.0 
> > release.
> >
> >  The main reason is to eliminate org.w3c.dom.* classes from this API 
> > and reduce runtime memory footprint of the task externalizers.
> >
> >  As a first step we can introduce own classes for Element, which may 
> > use dom classes internally (for now). So, connector's externalizers 
> > will only deal with our Element and won't have to change their 
> > implementation if we'll need to change externalizer internals.
> >  Another benefit of own element is that we can have stream based 
> > implementation at least for writing task data. That should help to 
> > speed things up for saving big task lists.
> >
> >  See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=166609
> >
> >  regards,
> >  Eugene