![]() This should include the motivations behind the library structure and oleutil usage. Test/Project directory will include the Visual Studio Community 2013 project for the C# COM server for testing.ĭocumentation directory will contain the documentation files for describing how to use the library for Google Go. I was also thinking of moving some of the helper code I created to here as well or simply removing the helper code I created, since it probably isn't being used. ![]() Oleutil directory will contain the current oleutil. Most of the code that could be used throughout the other packages would be contained in core.Ĭore-shared directory would contain most of the existing code with modifications to match interfaces in core.Ĭore-Cgo directory will mostly not exist until it is started by someone. It would also include interfaces for core-shared and core-cgo to implement, so that you could use either one. TL DR: Move the code from the current base directory to child directories so someone can go get /mattn/go-ole/core and go get /mattn/go-ole/core-shared and go get /mattn/go-ole/oleutil instead of having to download everything.Ĭore directory would contain all of the class structures that be type casted for COM. As well as what would be broken and have to be changed for those already using this library. The question is whether this would be accepted if I went ahead with this idea. I was thinking about restructuring and I was wanting some feedback before I start working on this with my fork. Leave a ticket, if there is breakage, so that it could be fixed. ![]() This contract should allow you to upgrade to new minor and patch versions without breakage or modifications to your existing code. Minor versions will only add new additions and changes. Which means that the major version will always maintain backwards compatibility with minor versions. ![]() Go OLE uses semantic versioning for version numbers, which is similar to the version contract of the Go language. The tests currently do run and do pass and this should be maintained with commits. It will be used to register a COM server and then run the test cases based on the test COM server. It is currently only used to test the build and ensure that the code works on Windows. It is also not currently possible to test the library on Linux, since COM API is specific to Windows and it is not currently possible to run a COM server on Linux or even connect to a remote COM server.ĪppVeyor is used to build on Windows using the (in-development) test COM server. Currently, Travis-CI is not used to test cross-building, but this may be changed in the future. Travis-CI was added to check builds on Linux to ensure that go get works when cross building. You will have to add these to your own account for your fork in order for it to run. Continuous integration configuration has been added for both Travis-CI and AppVeyor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |