Difference between revisions of "Mylyn Task List"

From Eclipsepedia

Jump to: navigation, search
(Task Data)
(Refactoring Objectives)
Line 6: Line 6:
 
*** Configuration data is being updated upon load anyway
 
*** Configuration data is being updated upon load anyway
 
** Presentation information such as hidden/readonly status fields being persisted
 
** Presentation information such as hidden/readonly status fields being persisted
** Actions being included (although perhaps this should remain as is)
+
** Operations being included
 
** Lazy loading
 
** Lazy loading
 
*** currently loaded at tasklist load time
 
*** currently loaded at tasklist load time
*** Could just have a flag indicating the existance of an offline file rather than load the data
+
*** Could just have a flag indicating the existence of an offline file rather than load the data
 
*** What does this break?
 
*** What does this break?
 
**Task Data Externalization
 
**Task Data Externalization
 
*** Switch to XML
 
*** Switch to XML
*** Use IMemento for now (if a problem we c
+
*** Possibly use IMemento
 
*** Separate files vs. one BIG file
 
*** Separate files vs. one BIG file
 
*** Consider zipping all the individual xml files together into one zip file (similar to Open Office file format ODF)
 
*** Consider zipping all the individual xml files together into one zip file (similar to Open Office file format ODF)
 +
 +
 +
*Repository Configuration
 +
**Leave as responsibility of connector assuming a contract:
 +
**Provide IMemento upon startup as an option
 +
**Remote configuration gathered periodically
 +
**Always available (even if repository is deleted, configuration sticks)
 +
**Task data combined with configuration upon presentation rather than persistence
  
 
==XML File Formats==
 
==XML File Formats==

Revision as of 12:09, 24 October 2006

Refactoring Objectives

  • Task Data Refactoring
    • Currently not nomalized
      • repository configuration options stored in same file
      • Configuration data is being updated upon load anyway
    • Presentation information such as hidden/readonly status fields being persisted
    • Operations being included
    • Lazy loading
      • currently loaded at tasklist load time
      • Could just have a flag indicating the existence of an offline file rather than load the data
      • What does this break?
    • Task Data Externalization
      • Switch to XML
      • Possibly use IMemento
      • Separate files vs. one BIG file
      • Consider zipping all the individual xml files together into one zip file (similar to Open Office file format ODF)


  • Repository Configuration
    • Leave as responsibility of connector assuming a contract:
    • Provide IMemento upon startup as an option
    • Remote configuration gathered periodically
    • Always available (even if repository is deleted, configuration sticks)
    • Task data combined with configuration upon presentation rather than persistence

XML File Formats

Task Data

<TaskData version="1.0" taskId="1" repositoryUrl="http://bugs.eclipse.org/bugs" repositoryKind="Bugzilla" modifiedTs="timestamp">
<Attribute id="...priority" modifiedTs="timestamp" author="rob.elves">
 <Value>xxx</Value>
 <Value>xxx</Value>
 <Value>xxx</Value>
</Attribute>
<Comment hasAttachment="true" attachmentId="1">
 <Attribute id="...author">
  <Value>rob.evles</Value>
 </Attribute> 
</Comment>
<NewComment>
   My new comment
</NewComment>
<Attachment id="1" isObsolete="false">
 <Attribute id="...attachment_date">
  <Value>date</Value>
 </Attribute>
</Attachment>
</TaskData>