/plugins/ProjectViewer/tags/pv_2_1_3_7/docs/TODO

# · #! · 65 lines · 56 code · 9 blank · 0 comment · 0 complexity · 804e47146ec0e3cd034710aab9f38e40 MD5 · raw file

  1. --------------------------------------------------------------------------------
  2. Bugs:
  3. - check drawing problems in ProjectCombo (arrow being drawn twice in some situations)
  4. --------------------------------------------------------------------------------
  5. Features:
  6. - Unit testing using jUnit. This will be tricky if we want to automate testing
  7. the GUI. But we can cover some bases with non-GUI tests.
  8. - create "addNode" events for nodes other than VPTFile.
  9. - better icons for VPTGroups
  10. - better icons for VPTProject
  11. - create nice API for the IconComposer class.
  12. * how to resolve conflicts when more than 1 version control provider
  13. exists?
  14. - 'new project' generators
  15. - new project from template
  16. - new project from VC system (see below)
  17. - version control integration
  18. - VC_Check: VC Plugins register a Hook that gets the project root and checks
  19. if that project is under version control
  20. - import filters (see importer/CVSEntriesFilter.java)
  21. - interface FileFilter
  22. - new project from VC system (initial checkout)
  23. - status in tree views
  24. - cvs status only for files
  25. cvs status -vR <root-dir>
  26. - possible states
  27. Up-to-date
  28. The file is identical with the latest revision in the repository
  29. for the branch in use.
  30. Locally Modified
  31. You have edited the file, and not yet committed your changes.
  32. Locally Added
  33. You have added the file with `add', and not yet committed your
  34. changes.
  35. Locally Removed
  36. You have removed the file with `remove', and not yet committed
  37. your changes.
  38. Needs Checkout
  39. Someone else has committed a newer revision to the repository.
  40. The name is slightly misleading; you will ordinarily use `update'
  41. rather than `checkout' to get that newer revision.
  42. Needs Patch
  43. Like Needs Checkout, but the CVS server will send a patch rather
  44. than the entire file. Sending a patch or sending an entire file
  45. accomplishes the same thing.
  46. Needs Merge
  47. Someone else has committed a newer revision to the repository, and
  48. you have also made modifications to the file.
  49. File had conflicts on merge
  50. This is like Locally Modified, except that a previous `update'
  51. command gave a conflict. If you have not already done so, you
  52. need to resolve the conflict as described in Conflicts
  53. example.
  54. Unknown
  55. CVS doesn't know anything about this file. For example, you have
  56. created a new file and have not run `add'.