treesheets
treesheets copied to clipboard
aardappel
[Feature Request] Load Images From File Path
It would be nice if treesheets could display images using file paths rather than having to copy the image into the treesheet. The issue with the latter is that if many images are present in the treesheet, its size becomes large and saving starts to take a long time. If treesheets loaded the image on demand from image files then this problem would go away.
Agree that would be a nice feature.. an image could be either internal or external, with ways to switch between them.
Would it be possible to do this by just replacing the image loading logic to instead perform a file read?
We'd certainly want to keep the current feature of having internal images as default, as for many use cases it is better. Implementing that properly would be a bit more work than what you seem to be suggesting.
Not planned? Really? Is this feature really not that useful? I have to hard disagree on this.
I guess github doesn't give a lot of nuance between "we don't have plans for someone to implement this right now" vs "not planned until someone wants to actually implement it" vs "not planned because we never want it".
I'd say this could be a useful feature, if carefully implemented with good UI & code, but it seems neither myself or @t2b3 has plans to implement it any time soon.. so it really is in the second of those :)
@t2b3, maybe issues that are "this would be a good feature to have, but maintainers don't plan to work on it" could be left open, and instead mark them with "PR welcome" or similar?
Also note @AntonBogun that closing an issue is not the end of the world.. its easy to reopen the moment someone says they'll work on it
I just added a PR welcome label, that is for "this would be a good feature to have, but maintainers don't plan to work on it"
I guess github doesn't give a lot of nuance between "we don't have plans for someone to implement this right now" vs "not planned until someone wants to actually implement it" vs "not planned because we never want it".
I'd say this could be a useful feature, if carefully implemented with good UI & code, but it seems neither myself or @t2b3 has plans to implement it any time soon.. so it really is in the second of those :)
@t2b3, maybe issues that are "this would be a good feature to have, but maintainers don't plan to work on it" could be left open, and instead mark them with "PR welcome" or similar?
Also note @AntonBogun that closing an issue is not the end of the world.. its easy to reopen the moment someone says they'll work on it
@aardappel thanks for your reply! I applied the proposed scheme to some other issues as well.
