ProjectLibrary.txt 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. TODO
  2. - ResourceManifest filePathToUUID wont work as intended as file-path comparison is case sensitive plus it wont deal with slashes properly
  3. - Remove WPath. In general, but specifically from CmPath.h, CmFileSystem.h and Projectlibrary
  4. - ResourceTreeView - Element sorting doesn't work
  5. - ProjectLibrary Save/Load - saves/loads the hierarchy of ResourceEntries
  6. - ResourceManifest needs to store relative locations when I save it, so that user can move Project folder safely
  7. - Resource import queue (ability to display progress bar for resources that are importing)
  8. - Implement Delete command for ResourceTreeView
  9. --------------------
  10. Test:
  11. - OSDropTarget
  12. - Drag and drop one file from Explorer into TreeView
  13. - Drag and drop multiple files from Explorer into TreeView
  14. - Drag and drop entire folders from Explorer into TreeView
  15. - Dragging folders or files from within Resources to another sub-folder in Resources
  16. - File monitoring
  17. - Add a file and ensure it is imported
  18. - Delete a file and ensure it has been cleaned up
  19. - Add a whole folder hierarchy with files and see if it is constructed properly
  20. - Delete a folder hierarcha and ensure it has been cleaned up
  21. - Start-up
  22. - Load up ProjectLibrary with a complex hierarchy already existing, with multiple files to import
  23. - Save/Load (After it is implemented)
  24. - Ensure that leaving application and then reloading will still recognize previously saved assets and will not reimport them
  25. - Also ensure that UUIDs will be properly read from .meta files
  26. -------------------
  27. LOW PRIORITY
  28. What happens when importer fails importing a file?
  29. - This can be one of the lasts steps, but I will likely need to go through all importers manually and set them up so they return proper error codes
  30. and clean up properly on error.
  31. - In fact they should use exceptions but those should be translated to error codes when returned to Importer
  32. - OR just write directly to debug log?
  33. - Probably log and error code, since I will need to inform the outside world that import failed somehow