Use more standard method for registering GF with Thor #149
Replies: 5 comments 6 replies
-
I vote for removing this from GF. |
Beta Was this translation helpful? Give feedback.
-
If you mean by this removing the code from GoFish.App and adding it instead to the Version file (which only exists and is referenced as part of Thor CFU), I heartedly agree. |
Beta Was this translation helpful? Give feedback.
-
@Jimrnelson The most recent development state is at https://github.com/lscheffler/GoFish, clone [email protected]:lscheffler/GoFish.git and use the dev branch. The file that should hold the Thor code is Could you alter this so that it does what it should do? Thanks |
Beta Was this translation helpful? Give feedback.
-
Sure, will do so over the weekend if time permits. This is mostly migrating code from with GF.App into the version file. However, it's tricky to test. |
Beta Was this translation helpful? Give feedback.
-
This has been taken care of. Months ago, actually. |
Beta Was this translation helpful? Give feedback.
-
The standard way for registering GF with Thor (supported by VFPX Deployment) is that the creation of the Thor Tool be created within the Version file.
GF actually has this embedded in the GoFish.App.
(For reasons I could never grasp, Matt Slay wanted the Thor Tools to be registered every time GF was called, which meant it had to be baked into GF.)
Beta Was this translation helpful? Give feedback.
All reactions