New Versions (1 Viewer)

[Jean-Marc]

It could be, but if the update involves the same files you have not backed up? It's not the same?

Thanks

Tgx[/QUOTE

I think it will be 10 times faster to update with the "update package" because a complete new release "reset" the configuration skin. With the "update package" no need to backup, even if the update involves a file containing a personal modification (if you change this file, I will have to apply again my mod to it).
Example with the home screen: if your release do not involve it, you must backup your file, install the update and then install again your backed file: why I would do all this stuff if I can avoid it??

Edit: but Tgx, don't loose time with my considerations, you have better things to do, I can manage that!!

 

[emphatic]

Best update would be a patch that just changes all of the lines in the affected .xml files. I imagine though that it would be quite a task to:
1) design the small app (a .bat file?)
2) keep track of all changes to input into the file

But for a user to drop a single file into the skin folder (thus setting the correct working path for it's operation) then running it would be very smooth. Also, can .bat files open .xml files? This way ONLY the changed lines in the files would be changed, and any user changes would remain (as the patch would search for lines by the author, changed lines would not be found and changed by the patch).

Emph

 

[Tgx]

I think it will be 10 times faster to update with the "update package" because a complete new release "reset" the configuration skin. With the "update package" no need to backup, even if the update involves a file containing a personal modification (if you change this file, I will have to apply again my mod to it).
Example with the home screen: if your release do not involve it, you must backup your file, install the update and then install again your backed file: why I would do all this stuff if I can avoid it??

For me it's simpler to post the updates and fixes in a thread, as i've begun using since version 2.1.1.
I'm going to put everything i do in this thread, so that everyone could easily see what i'm doing, and could test only the updates he/she likes. When there will be enough updates, i'll release a new complete version of the skin.

Thanks

Tgx

 

[Tgx]

Best update would be a patch that just changes all of the lines in the affected .xml files. I imagine though that it would be quite a task to:
1) design the small app (a .bat file?)
2) keep track of all changes to input into the file

But for a user to drop a single file into the skin folder (thus setting the correct working path for it's operation) then running it would be very smooth. Also, can .bat files open .xml files? This way ONLY the changed lines in the files would be changed, and any user changes would remain (as the patch would search for lines by the author, changed lines would not be found and changed by the patch).

Emph

A good idea, but i cannot figure out how i could build that batch file. It sounds a bit too complicated for me!

Thanks

Tgx