phatch-dev team mailing list archive

[Nadia Alramli <nadiana@xxxxxxxxx>]

Hi,


> I'd like to hear your opinions. This was mine:
> Actually this is a design decision what to do with variables (such as
> width, height, folder, type, ...) during multiple saves. I've been
> thinking already about this during Phatch 0.1
>
> I thought of three strategies:
>
> 1) keep old, prefix new
> - keep the variables of the original source file with the original names
> - add the variables with the prefix "new." to the newly saved files
>
> 2) prefix old, keep new
> - store the variables of the original source file with the prefix
> "source.", "base." or "old."
> - keep the variables of the original source file with the original names
>
> 3) index variables with suffix
> - original variables gets suffix ".0"
> - second saved file gets suffix ".1"
> (of course variables without suffix are still valid and than we should
> decide if it is the latest or the first file)
>
> Maybe my preference is 3, but I am curious to hear your opinions.

Solution number 3 sounds good to me. But I'm not sure if you refer to all
variables or just the ones that may change with every save. The width and
height for example cannot change in save. It might help if you separate
variables that can change in save than other variables.


>
> What do you expect when in one action list you save 3 times with
> different sizes in percentages (like for icons)?

I expect the resulting images to be in the same directory where I choose
them to be. Many users may decide to separate icons in different directories
with meaningful names. Currently the result is really confusing. For
example: Set the first save path to <folder>somename/<subfolder> and the
second to <folder>_phatch/<subfolder> and the result will be in
<folder>_patch/omename/ . omename is the result of a substring on
<folder>somename/. Which brings me to think that the issue might be in the
way the path is calculated rather than the way variables are changed.


> I think it needs to
> be of the last save otherwise features like text offset with % will be
> broken.

Hmm, I'm not sure I understand this. Why would the % offset get broken in
this case?

Best Regards,
Nadia


>
> Best regards,
> Stani
>
> --
> Phatch Photo Batch Processor - http://photobatch.stani.be
> SPE Python IDE - http://pythonide.stani.be
>
> _______________________________________________
> Mailing list: https://launchpad.net/~phatch-dev<https://launchpad.net/%7Ephatch-dev>
> Post to     : phatch-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~phatch-dev<https://launchpad.net/%7Ephatch-dev>
> More help   : https://help.launchpad.net/ListHelp
>