RE: [mylar-dev] Persistence of Tasks between Eclipse Sessions

["Mik Kersten" <beatmik@xxxxxxx>]

Yes, background synchronization is starting to work well, and we just need
to fix the bug with too many things showing up as incoming:

124908: improve bugzilla notification of incoming information
https://bugs.eclipse.org/bugs/show_bug.cgi?id=124908

Once we do that it would be good to flip to the open policy you suggest so
that opening reports is immediate if there are no changes from the last
synch.  But there's a question of what we do if there are changes.  For now
I think that we should do what regular files do if they've been updated
while you have them open with local changes, and what we already do if a
synch happens on a report after you've made changes: pop up a dialog asking
whether you would like overwrite or not (if you say yes we mark it will show
as conflicting).

Mik 

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Wednesday, April 19, 2006 11:02 AM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Persistence of Tasks between Eclipse Sessions
> 
> 
>    By the way, Mik, I noticed that when opening editor for Bugzilla
> issue from query hit, Mylar runs task synchronization firs, which may
> take some time. It would make sense to show an editor for currently
> available task info, kick off background sync and update editor upon
> completion.
> 
>    regards,
>    Eugene
> 
> 
> Mik Kersten wrote:
> > Sorry for the slow reply Felix.  The intent is that persistence of all
> Task
> > List information is taken of for you.  However, the tasks that appear in
> the
> > Task List are proxies for the actual tasks.  So what's stored is their
> > description and other relevant attributes, but not their contents (e.g.
> > Bugzilla comments).  If you want to store any additional information you
> > need to create a subtype of DelegatingTaskExternalizer.  As a general
> rule,
> > look to the mylar.jira plug-in for an example of the current API usage,
> and
> > see how JiraTaskExternalizer does this.
> >
> > I'd like to apply your patch, and all patches for eclipse.org projects
> must
> > come from bug reports, so could you please create a report for that and
> > attach?
> >
> > We pulled subtasks out of the UI ages ago, so I'm not surprised if
> > externalization for them is broken even though some unit tests remain.
> > Please file a bug report for this.  Also, there has been ongoing
> discussion
> > on subtask support in the task list, which I've summarized in the
> following
> > report.  It would be helpful if you could add your ideas or use cases
> there:
> >
> > 137543: [discussion] task list support for subtasks
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=137543
> >
> > Mik
> >
> >> -----Original Message-----
> >> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Felix Schwarz
> >> Sent: Wednesday, April 12, 2006 7:14 AM
> >> To: mylar-dev@xxxxxxxxxxx
> >> Subject: [mylar-dev] Persistence of Tasks between Eclipse Sessions
> >>
> >> Hi all,
> >>
> >> I have a question regarding persistence of tasks between Eclipse
> >> sessions: After writing an implementation of a
> >> AbstractRepositoryConnector, implementing subclasses of
> >> AbstractRepositoryTask etc., I like to see my imported repository
> >> tasks re-appearing after an Eclipse restart.
> >>
> >> I noticed that there is a TaskListManager [1] which has
> >> readExistingOrCreateNewList(). Unfortunately, subtasks, the repository
> >> kind and some other information is not saved in tasklist.xml. What is
> >> the recommended way dealing with these problems? Do I have to
> >> implement a special serialization interface?
> >>
> >> There was another problem in TaskList [2] which was easy to fix though
> >> (patch attached).
> >>
> >> [1] src/org/eclipse/mylar/provisional/tasklist/TaskListManager.java
> >> [2] src/org/eclipse/mylar/provisional/tasklist/TaskList.java
> >>
> >> Felix
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev