SimpleUpdater

[highend]

Small wish: Another variable that allows us to choose if we wish to delete the downloaded xyplorer.zip file afterwards.

[serendipity]

Version 7
1) New ini key "OnlyNewer" when set to 1 will show only beta logs newer than the current beta. Default is 1.
2) Ini key "betas" can be set to "0" or "all" to show all logs (max=15)
3) Key "DelDwnldZip" when set to 1 will delete (outsourced to VBS file) the downloaded zip file . Default is 0.
Tip: Change ini key "Downloadfilename" to $newver to name downloaded zip files with version number. To keep old versions DelDwnldZip should be 0.
4) Update button now remains visible all the time. Position fixed to Top-Left.
5) Improved the way ini keys were read/written, now if any key is missing they will be written by the script.
6) Added two links to beta club and main page at the bottom of the page. Clicking these will close script and launch browser.

SimpleUpdater v7.xys

(28.94 KiB) Downloaded 271 times

[LittleBiG]

Thanks. It might not be fixed in the next version but i'll look into it.

I am really sorry, I misread the description. I thought the "Update to v..." button color changes in connection with the offocial and beta. My bad. There is no need to examine further.

[serendipity]

Thanks. It might not be fixed in the next version but i'll look into it.

I am really sorry, I misread the description. I thought the "Update to v..." button color changes in connection with the offocial and beta. My bad. There is no need to examine further.

No problem, I did not spend too much time looking for this as the code is still not so big.
Thanks.

[Marco]

Re the changelog(s) window

You may consider making it more XY-ish by following the color scheme that Don adopts in several other windows, for example the one of batch rename after you press F1. To increase readability he uses a yellow background, 255-255-225 in RGB / 60°-12%-100% in HSB / #ffffe1 in HTML, and black fonts. This to maximize contrast.
There are also different studies that suggest avoiding color use when possible (http://www.amazon.com/exec/obidos/ASIN/ ... omputerrea for example). An idea could be using a regular Verdana for betas and a bold Verdana for majors. The change in shape as well as overall line luminance makes spotting the difference immediate.

Just my little suggestion. That said, great work

[serendipity]

Re the changelog(s) window

You may consider making it more XY-ish by following the color scheme that Don adopts in several other windows, for example the one of batch rename after you press F1. To increase readability he uses a yellow background, 255-255-225 in RGB / 60°-12%-100% in HSB / #ffffe1 in HTML, and black fonts. This to maximize contrast.
There are also different studies that suggest avoiding color use when possible (http://www.amazon.com/exec/obidos/ASIN/ ... omputerrea for example). An idea could be using a regular Verdana for betas and a bold Verdana for majors. The change in shape as well as overall line luminance makes spotting the difference immediate.

Just my little suggestion. That said, great work

Thanks Marco, I'll look into it.

[serendipity]

With respect to recent concerns by Don (link below), I might change the code to completely duplicate the beta page.
http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=8650

Also, since I am sometimes busy with my University work, Marco has agreed to contribute to this script and update it when needed. Also, anybody else willing to join us to improve this code is free to do so.

[Filehero]

Hi,

I didn't want to join the other thread where TheQuerty brought up the collaboration topic for obvious reasons.

Also, anybody else willing to join us to improve this code is free to do so.

My major problem is the constant lack of spare time to make a commitment to support what I call a collaboration. Hacking in the attic for oneself is one thing, but dealing with requests and bugs after release a totally different story. I know this nothing new but it's just to show that I've (again) learned my lesson with LayoutManager recently.

Beyond the scope of this very script, I currently don't see a clear way how a loose collaboration can be organized to suit the developers as well as the consumers need better than working on someones own.

TheQuerty mentioned the heaps of scripts that gotten buried in this forum. Just a thought: Maybe "we" can start off by "simply" trying to generate a "XY expansion pack" consisting of the "best" XY scripts released so far? Next, one could discuss wether this should become the code base on which a whatever-community-approach could be founded? Then "we" ......to be continued.

Maybe we/the crowd better discuss this further in a dedicated thread?


Cheers,
Filehero

[serendipity]

Hi,

I didn't want to join the other thread where TheQuerty brought up the collaboration topic for obvious reasons.

Also, anybody else willing to join us to improve this code is free to do so.

My major problem is the constant lack of spare time to make a commitment to support what I call a collaboration. Hacking in the attic for oneself is one thing, but dealing with requests and bugs after release a totally different story. I know this nothing new but it's just to show that I've (again) learned my lesson with LayoutManager recently.

Beyond the scope of this very script, I currently don't see a clear way how a loose collaboration can be organized to suit the developers as well as the consumers need better than working on someones own.

TheQuerty mentioned the heaps of scripts that gotten buried in this forum. Just a thought: Maybe "we" can start off by "simply" trying to generate a "XY expansion pack" consisting of the "best" XY scripts released so far? Next, one could discuss wether this should become the code base on which a whatever-community-approach could be founded? Then "we" ......to be continued.

Maybe we/the crowd better discuss this further in a dedicated thread?


Cheers,
Filehero

Will start with offtopic: I used your layoutmanager for the first time last Friday on a PC that needed simple layout and i did not want to click around to disable tons of buttons. I should say it was very useful. So thanks for that!

Now on topic:
My main reason to bring this up was to make sure that nice scripts here don't meet Jacky's updater kind of fate which is unfortunate.
Given how often we update, there could be common script we all could work on to improve.
I cannot speak for other scripts, but for any of my scripts you are free to change them as long as you tell me in advance so that I am not working on the same thing which a waste of our time.
And yes, do start a dedicated thread to discuss this.

[Filehero]

And yes, do start a dedicated thread to discuss this.

Done.

And thanks for finding my script helpful.


Cheers,
Filehero

[serendipity]

I've been discussion this script with Marco:

Code: Select all

  $url=readurl("http://www.xyplorer.com/xyfc/viewtopic.php?f=1&t=4&sd=d",1,0,2);
  $url= replace($url, '"./', '"http://www.xyplorer.com/xyfc/');
  $url=regexreplace($url, '</?a(|\s+[^>]+)>', '');
  $url=replace($url, 'No-Install Package', '<a href="xys:http://www.xyplorer.com/download/xyplorer_11.60_beta_noinstall.zip"> No-Install Package</a>');
  $check=html("$url","85%","85%");
  IF($check Like "http://www.xyplorer.com/download*"){
  status "download";
  }
  ELSE{
  status "Script closed";
  }

He came up with the concern that user's version maybe behind the one user sees on page one and hence no way to navigate to other pages.
Maybe he or others can join and take a shot at this.

[Marco]

Looking good. Maybe we continue this in the main script page so others can follow?
Also, if you have time you can go ahead and incorporate it in the main script.
I dont have the time until Friday Evening, so feel to post a new update if you like.
Few thoughts: maybe disable some links like installer which this script wont help with?
Maybe you can disable link which will take user elsewhere, i.e. beyond the realm of this script?

Disabling links selectively isn't very future-proof imo, since names can change. Maybe I can restrict the scope of the loop to the www.xyplorer.com/xyfc pages.

[serendipity]

Looking good. Maybe we continue this in the main script page so others can follow?
Also, if you have time you can go ahead and incorporate it in the main script.
I dont have the time until Friday Evening, so feel to post a new update if you like.
Few thoughts: maybe disable some links like installer which this script wont help with?
Maybe you can disable link which will take user elsewhere, i.e. beyond the realm of this script?

Disabling links selectively isn't very future-proof imo, since names can change. Maybe I can restrict the scope of the loop to the http://www.xyplorer.com/xyfc pages.

Yes, that would help. thanks.

[xycooper]

serendipity
Thanks you for your script.

For some reason I can't use version 5-7 but version 4 works fine for me.
When using v5-7 I get this error.

[serendipity]

serendipity
Thanks you for your script.

For some reason I can't use version 5-7 but version 4 works fine for me.
When using v5-7 I get this error.

Both have same exact commands for reading that file, strange.
Can you try:
1) Delete the SimpleUpdater.ini and try again.
2) Maybe the file output.txt is taking longer than 10 seconds to create.
Just about the line: $readpid= readfile("$outpid");
Change $count>20 to $count>40