We are moving our repo to GitHub with the rest of the Autodesk open source projects. We plan to move the Wiki over, but I'm not sure how to move the Discussion (so we may create a link in the Wiki to refer here). There is an Issues section in Git, so hopefully we can use that to track bugs and requests. Most of us are still fairly new with Git, so please be patient as we figure out how best to take advantage of its full potential.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We'll keep the other versions here for now. At some point we might move 2018, but there's no point in moving anything before that. We won't delete anything here of course.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it is the "same code". Of course, core 2019 has improvements (and hopefully no regressions :) ) from 2018, so I can't say it is exactly the same, and I believe that exporting steel connections is only 2019, since that is new functionality. But in general, we'll try to keep the two branches in sync. We may decide that since we are still actively improving 2018, it is just easier to have it all in one place, instead of 2018 here and 2019 there; or we might just deal with a transition year and then whenever the next release is out, be entirely on Git.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think some people will have the preference that also 2018 is moving to GitHub for making code contributions, since R2018 is still the currently used version for production. They are mostly only switching to the next version after the 2nd service release.
And if I understand correctly also compiling the code is gonna made easier (topic of Emanuele?), so maybe it could help in managing the repeated question "when is the next version available", if each of us can compile it at anytime with the improvements at that particular time. ( BTW, when is ... :-) )
Last edit: Dirk Van Rillaer 2018-06-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Branches for different versions is one of the big reasons why I was advocating for the switch from Source Forge and github. I just created a Revit2018 branch, you should be able to work in that branch if you prefer and we can still merge changes into the master (2019) branch. https://github.com/Autodesk/revit-ifc/tree/Revit2018
Post if you have problems with this.
Cheers,
Jon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Probably I have too many blond questions about the "how to build" process, that it is better that I patiently wait until the notes are written (as now is mentionned on GitHub at the openingspage):
"We are in the process of greatly simplifying the build progress. We will add notes shortly once this work is complete."
I referred in my previous message to "some people" in the 3rd person, since I'm not (yet) a 'coding person' myself.
I see that you entered in the Branch Revit2018 some commits/fixes (I still have to learn to use the correct terms). After these commits are verified/approved, it would be nice if I would be able to compile it myself and can continue testing in Revit (but as you probably figured out in my first line, I currently don't have a clue on how to do that). Not only for testing purposes this would be helpfull, but I could imagine that also for some firms it would make the update cycle of the exporter easier.
Regards,
Dirk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My understanding at the moment is that Jon made changes so that downloading the code and using Visual Studio 2015 should have it just "work". I'll work with him to update the README to reflect that (or the reality...)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Note that you can also download the code and build at any time a version that might be ahead of the last released installer. However, we will note which are the 'stable" versions that end up in the AppStore, keeping in mind that any code that isn't corresponding to a stable version (1) won't be digitally signed and (2) won't have gone through Autodesk QA.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
https://github.com/Autodesk/revit-ifc
We are moving our repo to GitHub with the rest of the Autodesk open source projects. We plan to move the Wiki over, but I'm not sure how to move the Discussion (so we may create a link in the Wiki to refer here). There is an Issues section in Git, so hopefully we can use that to track bugs and requests. Most of us are still fairly new with Git, so please be patient as we figure out how best to take advantage of its full potential.
Great work, only the 2019 version is on GitHub?
When can we expect the other versions ?
We'll keep the other versions here for now. At some point we might move 2018, but there's no point in moving anything before that. We won't delete anything here of course.
Is the code of 19.1 similar to 18.4 (concerning issues with 18.4)?
Yes, it is the "same code". Of course, core 2019 has improvements (and hopefully no regressions :) ) from 2018, so I can't say it is exactly the same, and I believe that exporting steel connections is only 2019, since that is new functionality. But in general, we'll try to keep the two branches in sync. We may decide that since we are still actively improving 2018, it is just easier to have it all in one place, instead of 2018 here and 2019 there; or we might just deal with a transition year and then whenever the next release is out, be entirely on Git.
I think some people will have the preference that also 2018 is moving to GitHub for making code contributions, since R2018 is still the currently used version for production. They are mostly only switching to the next version after the 2nd service release.
And if I understand correctly also compiling the code is gonna made easier (topic of Emanuele?), so maybe it could help in managing the repeated question "when is the next version available", if each of us can compile it at anytime with the improvements at that particular time. ( BTW, when is ... :-) )
Last edit: Dirk Van Rillaer 2018-06-28
Hi Dirk,
Branches for different versions is one of the big reasons why I was advocating for the switch from Source Forge and github. I just created a Revit2018 branch, you should be able to work in that branch if you prefer and we can still merge changes into the master (2019) branch.
https://github.com/Autodesk/revit-ifc/tree/Revit2018
Post if you have problems with this.
Cheers,
Jon
Hi Jon,
Probably I have too many blond questions about the "how to build" process, that it is better that I patiently wait until the notes are written (as now is mentionned on GitHub at the openingspage):
"We are in the process of greatly simplifying the build progress. We will add notes shortly once this work is complete."
The tips on the Sourceforge-page are a little bit to cryptic for me to get a fast start:
https://sourceforge.net/p/ifcexporter/wiki/Development%20Environment%20Tips/
I referred in my previous message to "some people" in the 3rd person, since I'm not (yet) a 'coding person' myself.
I see that you entered in the Branch Revit2018 some commits/fixes (I still have to learn to use the correct terms). After these commits are verified/approved, it would be nice if I would be able to compile it myself and can continue testing in Revit (but as you probably figured out in my first line, I currently don't have a clue on how to do that). Not only for testing purposes this would be helpfull, but I could imagine that also for some firms it would make the update cycle of the exporter easier.
Regards,
Dirk
My understanding at the moment is that Jon made changes so that downloading the code and using Visual Studio 2015 should have it just "work". I'll work with him to update the README to reflect that (or the reality...)
Note that you can also download the code and build at any time a version that might be ahead of the last released installer. However, we will note which are the 'stable" versions that end up in the AppStore, keeping in mind that any code that isn't corresponding to a stable version (1) won't be digitally signed and (2) won't have gone through Autodesk QA.