@awadrummer said:
Does anyone know if this plugin is compatible with Sketchup Pro 2018?
I did a little test and I ran into some issues for su2018 
I will try to find some time to look into them...
@awadrummer said:
I'm looking to upgrade, but can't live without this one.
Great to hear you like it!
I'm working on a new plugin that uploads the current SketchUp model directly into the open source BIMserver (as IFC).
You need a running BIMserver to try it:
https://github.com/opensourceBIM/BIMserver/wiki/Get-Started-Quick-Guide
Any BIMserver users on SketchUcation? Interested in testing? 
Fix for mac! Menu layout needs some work still.
Check out the plugin store
@dan rathbun said:
This is going to bloat model files.
Yes, I'm glad they DO store the scheme inside the model so you don't have to redistribute it seperately, but more than one "copy" in the model indeed seems bloated.
I'm curious what happens when you upgrade a model from IFC 2x3 to 2x4(when a scheme is available). I'm affraid you would have to re-assign every single property... and manually remove the old scheme to get rid of the duplicate classifications.
@dan rathbun said:
But... the actaul value in the nested dictionary is a string "partial" ?
Ie, not the integer of the choice ?
Yes indeed, a string. There is another atribute called something like "options" which contains a list of valid options (as strings). The entire classification scheme that goes with the selected ifctype(ifcBuilding) is stored inside the componentdefinition. So you can check validity right from the definition without having the original source scheme.
HaHa!!!
I just found out that classifications are stored as nested attribute dictionaries!
That means you can set classifications(if you're a bit careful) using the "normal" way with "set_attribute", I guess even in the free version...
A "IfcBuilding" for example gets an attribute dictionary called "IFC 2x3" which gets a nested attributedictionary "CompositionType" which gets a nested attributedictionary "IfcElementCompositionEnum" in which "value" can be set as "partial"
Cheers!
Jan
@dan rathbun said:
.
I do not understand why some coders go out of their way, to write minimalist hard to read and understand code. Come back 3 years from now and see if the coder remembers what the code is supposed to do, without spending a half hour consulting method documentation, etc.
LOL Thank you very much! I totally agree with you. It indeed seemed a nifty piece of code I found on stackoverflow, but every time I needed to edit it, it took me half an hour to re-interpret it(and I'm still not 100% sure how the tap works).
Now you write it out it does not seem so difficult anymore
I should have added the indentation myself the moment I tried to understand what it did 
Hi Dan,
I also removed a "tap"-call because it was added in ruby 1.9.
Would you consider this a good substitute? Or would it be much slower?
hash = {}.tap{ |r| bt_entities.each{ |ent| ent.properties_editable.each{ |k,v| (r[k]||=[]) << v } } }
hash = bt_entities.inject({}) {|h,ent| ent.properties_editable.each{ |k,v| (h[k]||=[]) << v}; h}
something I borrowed from:
http://stackoverflow.com/questions/5490952/merge-array-of-hashes-to-get-hash-of-arrays-of-values
I've been able to remove the dependency on pathname and it's running now on SU7 and SU8.
Although one (probably showstopper) problem remains. Auto-updating of modified objects does not work on SU7 because the "EntitiesObserver.onElementModified" method was added in SU8.
That means updating geometry must be done manually by disabling and re-enabling the observers (red/green button).
New version added to this post, I will add it to the plugin store when I also fixed the MAC issue, but that has to wait a little until I get my hands on a MAC 