Checking for XYplorer Updates

[TheQwerty]

Naah, then I would have to update that file every day.

Too bad.. makes it worthless to me and probably many of the people that frequent the forums.

You get an email anyway on each new beta, don't you?

No, I find those e-mails useless since they only link to the post and don't provide the actual change logs.

Besides, incorporating the e-mail into a program to check and update XY is quite a bit more work and inconvenience than checking a URL. Currently the only good way, is to check the beta thread and do a bunch of HTML parsing (have you ever looked at jacky's updater?), and as always scraping is prone to frequent problems when the format/wording/layout changes from what is expected.

I guarantee it would be easier and more reliable in the long-term for you to automate your updating process to include uploading, posting changes, and modifying the PHP file.


Not sure why you seem so insistent on making it difficult for users to upgrade...

[TheQwerty]

Naah, then I would have to update that file every day.

You mean you can't have a script that does it automatically for you when you publish the update?

Write one for me.

Provide the details and document your current process...

[admin]

I was just joking. As I said before: You get an email anyway on each new beta, don't you? So what the fuss.

[TheQwerty]

I was just joking. As I said before: You get an email anyway on each new beta, don't you? So what the fuss.

Did you not read my response to that?

(Sorry I posted twice instead of editing..)

[j_c_hallgren]

I was just joking. As I said before: You get an email anyway on each new beta, don't you? So what the fuss.

Not sure about others here, but email is not self-contained within the program and gives no details on what new vers is, not even the vers nbr...and...many other appl have built-in 'chk for updates' that will either update it (most do if desired) or at least notify users of availability of an update...I don't like those that auto-upd but having it inform me of upd being there within the appl is quite handy.

[TheQwerty]

many other appl have built-in 'chk for updates' that will either update it (most do if desired) or at least notify users of availability of an update...I don't like those that auto-upd but having it inform me of upd being there within the appl is quite handy.

I've always been a huge fan of how Beyond Compare does it.

First, it's configurable; I can not only disable checking for updates, but I can also set the number of days it should wait between checks.

When enabled, it automatically checks in the background and when a new version is available displays a message to the right of the menu bar (see this borrowed image since I'm up to date).

If the user clicks that text it pops up a dialog that links to their change log on the web, and allows the user to start the update process.
If the user does it downloads the new version, upgrades, and then prompts the user if it's okay to restart Beyond Compare to complete the update.
If they choose to restart it does so and returns the user to exactly where they were before the restart (re-opens the same files, focuses the same lines, etc.)

It's fantastic because it stays entirely out of my way if I don't want to update, but when I do it's quick, painless, and allows me to resume my work with very little interruption.

[admin]

I was just joking. As I said before: You get an email anyway on each new beta, don't you? So what the fuss.

Did you not read my response to that?

(Sorry I posted twice instead of editing..)

Whoops, yes, I skipped it.

Anyway, I won't support this for BETA versions, but I will add it to the config for official versions.

[admin]

I was just joking. As I said before: You get an email anyway on each new beta, don't you? So what the fuss.

Did you not read my response to that?

(Sorry I posted twice instead of editing..)

Whoops, yes, I skipped it.

Anyway, I won't support this for BETA versions, but I will add it to the config for official versions.

Or not. I stupidly spent the whole morning with this boring stuff and finally failed for performance reasons. What a waste. Topic closed.