I have a multi-pronged question here. I had (well have) used Thor's update process to update all the VFPx tools pointing to MSFT's former site for VFPx.
Side note: It's apparently undocumented but VFPx tools can still be updated through Thor. So long as the update comes from outside MSFT's dead web site, everything works. Occasionally an update will come through, such as Doug Hennig's new Project replacement.
So, things are now on GitHub. OK. How does one manage this?
1) How do we determine which is the latest version? That's a serious question as there are two places that can have the update.
2) What tools do you recommend for Github?
3) Thor would download an extension and put it in a specific directory for Thor to manage. Let's call it directory X. The Github downloader would ostensibly put it in directory Y. Is there a way to not only point to directory X for a specific GitHub VFP tool but to have it unpacked in that directory?
4) How about integrating new VFP tools on GitHub into Thor? Does one just manually make the directories and update metadata somewhere?
There's probably several more questions but that will get us started.
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Anyone want to take a stab at this?
Bill Anderson
On Fri, Aug 23, 2019 at 4:16 PM Bill Anderson billand88@gmail.com wrote:
I have a multi-pronged question here. I had (well have) used Thor's update process to update all the VFPx tools pointing to MSFT's former site for VFPx.
Side note: It's apparently undocumented but VFPx tools can still be updated through Thor. So long as the update comes from outside MSFT's dead web site, everything works. Occasionally an update will come through, such as Doug Hennig's new Project replacement.
So, things are now on GitHub. OK. How does one manage this?
- How do we determine which is the latest version? That's a serious
question as there are two places that can have the update.
What tools do you recommend for Github?
Thor would download an extension and put it in a specific directory for
Thor to manage. Let's call it directory X. The Github downloader would ostensibly put it in directory Y. Is there a way to not only point to directory X for a specific GitHub VFP tool but to have it unpacked in that directory?
- How about integrating new VFP tools on GitHub into Thor? Does one just
manually make the directories and update metadata somewhere?
There's probably several more questions but that will get us started.
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Have you tried posting this in the Thor Google group, Bill? Or posting a comment on the Github project? To the best of my knowledge all the VFPx projects were migrated to Thor so Thor's updater should be working.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Bill Anderson Sent: Thursday, August 29, 2019 10:16 AM To: profoxtech@leafe.com Subject: Re: Thor Updates and VFPX GitHub site
Anyone want to take a stab at this?
Bill Anderson
On Fri, Aug 23, 2019 at 4:16 PM Bill Anderson billand88@gmail.com wrote:
I have a multi-pronged question here. I had (well have) used Thor's update process to update all the VFPx tools pointing to MSFT's former site for VFPx.
Side note: It's apparently undocumented but VFPx tools can still be updated through Thor. So long as the update comes from outside MSFT's dead web site, everything works. Occasionally an update will come through, such as Doug Hennig's new Project replacement.
So, things are now on GitHub. OK. How does one manage this?
- How do we determine which is the latest version? That's a serious
question as there are two places that can have the update.
What tools do you recommend for Github?
Thor would download an extension and put it in a specific directory
for Thor to manage. Let's call it directory X. The Github downloader would ostensibly put it in directory Y. Is there a way to not only point to directory X for a specific GitHub VFP tool but to have it unpacked in that directory?
- How about integrating new VFP tools on GitHub into Thor? Does one
just manually make the directories and update metadata somewhere?
There's probably several more questions but that will get us started.
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
Hi Bill,
As for GitHub (or git in general), I've been using Tortoise Git. I also use Tortoise for SVN and Mercurial for other repos (yes, I'm kind of repo agnostic).
To answer the rest of your questions and to show you it is really documented:
Details on how the "classic" approach to the Thor updater works, see http://mattslay.com/how-thor-checks-and-distributes-new-versions-of-tools-in....
VFPX on GitHub has a mechanism to more easily handle updates, as described at https://vfpx.github.io/thorupdate/. However, not many project managers have implemented that so few projects support it, unfortunately. Right now, it is better to go to the GitHub repository for the projects you actively use to check for the latest version.
It is my opinion that someone is going to have to step up and take charge and just assist the project managers in moving their download process to GitHub as documented. The real problem here is that many projects are dormant and some of the project managers have lost interest. In those cases, it is a one-time job. Other project managers are super busy with other things and don't have the time. Project Managers need to allow this person access to the repos, or allow for pull requests to make the update. As you can see, the process is not difficult, but does take a little time with several steps.
Rick White Light Computing, Inc.
www.whitelightcomputing.com
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Bill Anderson Sent: Friday, August 23, 2019 07:17 PM To: profoxtech@leafe.com Subject: Thor Updates and VFPX GitHub site
I have a multi-pronged question here. I had (well have) used Thor's update process to update all the VFPx tools pointing to MSFT's former site for VFPx.
Side note: It's apparently undocumented but VFPx tools can still be updated through Thor. So long as the update comes from outside MSFT's dead web site, everything works. Occasionally an update will come through, such as Doug Hennig's new Project replacement.
So, things are now on GitHub. OK. How does one manage this?
1) How do we determine which is the latest version? That's a serious question as there are two places that can have the update.
2) What tools do you recommend for Github?
3) Thor would download an extension and put it in a specific directory for Thor to manage. Let's call it directory X. The Github downloader would ostensibly put it in directory Y. Is there a way to not only point to directory X for a specific GitHub VFP tool but to have it unpacked in that directory?
4) How about integrating new VFP tools on GitHub into Thor? Does one just manually make the directories and update metadata somewhere?
There's probably several more questions but that will get us started.
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]
Rick,
*>> VFPX on GitHub has a mechanism to more easily handle updates, as described at https://vfpx.github.io/thorupdate/ https://vfpx.github.io/thorupdate/.<<*
I didn't know about this page, so this will get me unblocked for now.
Thanks!
Bill Anderson
On Fri, Aug 30, 2019 at 11:04 AM Rick Schummer < profox@whitelightcomputing.com> wrote:
Hi Bill,
As for GitHub (or git in general), I've been using Tortoise Git. I also use Tortoise for SVN and Mercurial for other repos (yes, I'm kind of repo agnostic).
To answer the rest of your questions and to show you it is really documented:
Details on how the "classic" approach to the Thor updater works, see
http://mattslay.com/how-thor-checks-and-distributes-new-versions-of-tools-in... .
VFPX on GitHub has a mechanism to more easily handle updates, as described at https://vfpx.github.io/thorupdate/. However, not many project managers have implemented that so few projects support it, unfortunately. Right now, it is better to go to the GitHub repository for the projects you actively use to check for the latest version.
It is my opinion that someone is going to have to step up and take charge and just assist the project managers in moving their download process to GitHub as documented. The real problem here is that many projects are dormant and some of the project managers have lost interest. In those cases, it is a one-time job. Other project managers are super busy with other things and don't have the time. Project Managers need to allow this person access to the repos, or allow for pull requests to make the update. As you can see, the process is not difficult, but does take a little time with several steps.
Rick White Light Computing, Inc.
www.whitelightcomputing.com
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Bill Anderson Sent: Friday, August 23, 2019 07:17 PM To: profoxtech@leafe.com Subject: Thor Updates and VFPX GitHub site
I have a multi-pronged question here. I had (well have) used Thor's update process to update all the VFPx tools pointing to MSFT's former site for VFPx.
Side note: It's apparently undocumented but VFPx tools can still be updated through Thor. So long as the update comes from outside MSFT's dead web site, everything works. Occasionally an update will come through, such as Doug Hennig's new Project replacement.
So, things are now on GitHub. OK. How does one manage this?
- How do we determine which is the latest version? That's a serious
question as there are two places that can have the update.
What tools do you recommend for Github?
Thor would download an extension and put it in a specific directory for
Thor to manage. Let's call it directory X. The Github downloader would ostensibly put it in directory Y. Is there a way to not only point to directory X for a specific GitHub VFP tool but to have it unpacked in that directory?
- How about integrating new VFP tools on GitHub into Thor? Does one just
manually make the directories and update metadata somewhere?
There's probably several more questions but that will get us started.
Bill Anderson
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
-
Bill Anderson -
Richard Kaye -
Rick Schummer