You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I sat in Doug's session of last week's DevCon in Frankfurt I remembered that I have done modifications to the class. And as I now looked through my code, I found that it actually was guite a bit I did back then.
No idea, why I did not publish it at that time. Maybe the next project was calling for attention and later contribution became difficult, as most of the stuff was done in 2011, when version 1.30 Alpha was current, which is the version I'm still working with.
But as we now have Git, I guess what I should do, is to fork the current branch and see if I can adopt my modifications to the current version - as far as they have not already been implemented by now.
In theory we then should be able to merge that into the new version.
I have been using Git for years, but up to now only as a consumer. So I'm not too familiar with the way it works. However I doubt that it is able to deal with our vcx/vct and scx/sct files. Prgs should be no problem.
If I see it right, there are also sourceSafe-Files (vca / sca). Having them here is a bit like "belt and suspenders", but as those files are in fact the flat file representations of our propritetary formats, this might be the way to go. I am using SourceSafe as well.
I'll write an individual "issue" for each modification/idea/remark I made. I think this is better than one longer writeup and makes it easier for us to discuss whether the one or the other is worth being ported into the current version or if I'm on the wrong track. OK?
regards
Frank
The text was updated successfully, but these errors were encountered:
I don't think Cesar is doing anything with GitHub yet, so why not create a pull request with your changes or even just do a commit and push so your changes are merged into the repository?
When I sat in Doug's session of last week's DevCon in Frankfurt I remembered that I have done modifications to the class. And as I now looked through my code, I found that it actually was guite a bit I did back then.
No idea, why I did not publish it at that time. Maybe the next project was calling for attention and later contribution became difficult, as most of the stuff was done in 2011, when version 1.30 Alpha was current, which is the version I'm still working with.
But as we now have Git, I guess what I should do, is to fork the current branch and see if I can adopt my modifications to the current version - as far as they have not already been implemented by now.
In theory we then should be able to merge that into the new version.
I have been using Git for years, but up to now only as a consumer. So I'm not too familiar with the way it works. However I doubt that it is able to deal with our vcx/vct and scx/sct files. Prgs should be no problem.
If I see it right, there are also sourceSafe-Files (vca / sca). Having them here is a bit like "belt and suspenders", but as those files are in fact the flat file representations of our propritetary formats, this might be the way to go. I am using SourceSafe as well.
I'll write an individual "issue" for each modification/idea/remark I made. I think this is better than one longer writeup and makes it easier for us to discuss whether the one or the other is worth being ported into the current version or if I'm on the wrong track. OK?
regards
Frank
The text was updated successfully, but these errors were encountered: