Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
Currently, when previewing a website, RocketCake creates a folder in the home directory ("/home/user/rocketCakeTmpPreview"). But this clutters the user’s home folder. So It would be better to store preview files in a more appropriate location, such as: /home/user/.rocketcake/tmpPreview, or /home/user/.cache/rocketcakePreview (temporary/cache data following XDG standards) Additionally, it would be helpful to include an option that automatically deletes the preview folder when RocketCake is closed. Or an simpler approach would be to place the preview folder in "/tmp/", so "/tmp/rocketcakePreview", which is designed for temporary files and is typically cleared automatically on system reboot. |
||||
|
Yes - I wanted do do this but the problem is that most users now have their browser (like Firefox) installed via flatpak - and it cannot access these folders for the preview. This was the workaround for now. |
||||
|
it would be helpful to include an option that automatically deletes the preview folder when RocketCake is closed I don’t think an auto-clean function would be a good idea, at least not if the sole aim is to avoid clutter. If I look into my /AppData/Local/Temp/ folder (Windows) I find it's cluttered anyway. Also, on "Preview" RocketCake overwrites existing files with same file names. So it doesn't add much clutter. But there is another reason why I wouldn't like an auto-clean: If a website uses self-hosted fonts, I like to put the /fonts/ folder into the preview folder, so to view the website with the preferred font face already in Preview. If there was an auto-clean on RocketCake closure, the fonts would be lost and I had to put them back again when I resume working on the website. If at all, I would vote for a "Clear Preview Folder" menu item. |
||||
|
niko wrote: Yes - I wanted do do this but the problem is that most users now have their browser (like Firefox) installed via flatpak - and it cannot access these folders for the preview. This was the workaround for now. Yeah, That makes sense, but: No, most users do not have their browser installed via Flatpak, especially since Firefox (typically) comes preinstalled (as a system package, or on Ubuntu, as snap (snap is also sandboxed, so maybe similiar issues occur)). If Flatpak applications have access to "/home/user/", then they can also access its subdirectories, such as "/home/user/.cache". But the best solution would probably be to simply add an option that allows users to choose the location of the preview folder themselves. |
||||
|
That' true. I'll add a feature like a menu "Clear Preview Folder" to the TODO list. |
||||
|
|
){kind=link}