MK has emailed me ssClasses with one change, i.e., GETENV("TMP") is replaced with CURDIR(). However, my CURDIR() is my folder for my tables named records. So implementing this will result to something like this:
and so on...
I cannot deny that MK really needs it like that. However, personally, one of the reasons why I throw those images in temp folder is because I do not want my app cluttered with any of those. But that is my personal choice. ssClasses library no longer affects me or MK alone so I wanted your opinions as well on this.
An alternative I am thinking is this, create a public empty class in your topmost prg like this:
ossClassLib = CREATEOBJECT('EMPTY')
So you can control where the images will go.
I prefer an empty class over a public variable as it is less prone to affect your other variable declarations in your project. Plus maybe in the future we will need some more of the same so all I need to do then is simply add another property to it.
Inside the class for extracting images will be something like:
Or is there something better than that?
Another is the issue of overwriting only the images when it is not there. Would you rather I remove skipping of extraction when the image is there or would I retain it? If we retain it, then images won't be extracted anymore when it is there and it will be a bit faster (nanosecond difference?). That is the PRO. The CON is if I make any changes to the images, then those that are on your client's side won't be updated as long as those old images exist. That is the main reason why ss_support.app simply replaces images on every run.
1. Do I go for fixed CURDIR() or do we use Empty Class for image location?
2. Do I check for images and skips overwriting if it is there or I simply overwrite it on every form run? You won't know overwriting is done as it is very fast (nanosecond).
If you are interested to participate, please post your opinions below. Alpha 4 will be based on your opinions. And the sooner you can respond to this, the sooner I can touch the library.