This should be low hanging fruit for your development team, but I also don't know your stack:
I want to be able to 'Bookmark' samples, folders, whatever. I can probably save you some design time, so here's a MVP of what the developers may like to do:
Load FL Studio: setupBookmarks()
- Method could be a sibling or child of your File Explorer ops.
- Search for (local only) 'bookmarks' file. Does a file exist? Do we have a *cache?
Check for cache and Bookmarks file diff
- If bookmarks file hash has changed (compare to new hash to old hash) return and continue loading the fresh bookmarks.
- Else, we're going to load the cache.
Try loading whichever file found (loadBookmarks(filePath)), catch if failure
* Cache logic is explained below.
Load Bookmarks: loadBookmarks(file)
- (Logical state: File found and ready to process)
- Create Bookmarks/Favorites entry at the top of the file explorer.
- The state file contains a delimited series of paths: Load paths into an array.
- For each **item in the array, create a file shortcut in Bookmarks that points to this item.
- Dispose of shortcuts (treat them as temp files) or cache the bookmarks by making a copy of the current bookmark state, save hash of bookmarks file.
** If item is a folder you'd have to recursively*** call and, for each item in the folder, create a shortcut in the parent folder, or continue tunneling down into each sub folder.
*** For a MVP, maybe don't worry about folders and subfolders. This is a typical op but obviously exponentially increases your space complexity.
Like I said, this is pretty low hanging fruit. Give it to the intern.
Post your ideas and suggestions here
2 posts • Page 1 of 1
[You can only see part of this thread as you are not logged in to the forums]