I know what you mean, keeping track of patches can be a real headache...
You could approach it from a "maintainers" standpoint, like they do with the Linux kernal patches. Anyone who would like to contribute code enhancements, etc, could email you the new code for your approval and inclusion into any new releases. That way you control new release versions with whatever feature(s) you think are good for the BlitzUI application. This also allows you to control the update release frequency without getting tied up in "update mania". Just a thought.
The nice thing about this method is that you'll get the benefit of having others who program in Blitz to help mature your application.
The BlitzUI program is immensely useful now and I believe it will become a "got to have" tool for UI development as it continues to develop.
You could approach it from a "maintainers" standpoint, like they do with the Linux kernal patches. Anyone who would like to contribute code enhancements, etc, could email you the new code for your approval and inclusion into any new releases. That way you control new release versions with whatever feature(s) you think are good for the BlitzUI application. This also allows you to control the update release frequency without getting tied up in "update mania". Just a thought.
The nice thing about this method is that you'll get the benefit of having others who program in Blitz to help mature your application.
The BlitzUI program is immensely useful now and I believe it will become a "got to have" tool for UI development as it continues to develop.