Excellent news and should support CPG1.5 too.
The only drawbacks I see are with frameless integration. Firstly, not all users have cURL enabled. Secondly, I see a lot of css conflicts with some of the current templates so I am sure users will want to know how to fix these.
true not all have curl enabled. but this is used in many core functions of jfusion you can live without it but many plugins use curl for the dual login, so it wont work without it. (so its kind of required)
I also like to comment on the css conflicts, the 1.2.0 version will also have a css parser that removes most of the css conflicts, it do this parsing the css files and applying #jfusionframeless as a "prefix" to all css rules, (this means that only copper mine rules should apply to the copper mine code, and not joomla).
now the "bigger/renaming problem" is when you have joomla css that apply to the copper mine, this i try to prevent using a "default" css file that in affect reset every rule set to the by other css. this file is not yet perfect as i only have so much time and not all browsers read css the same sadly ..
here is a link to the default css:
http://joomla.fanno.dk/components/com_jfusion/views/css/default.cssand here is an eksamble of how one of the css files from copper-mine has been parsed.
http://joomla.fanno.dk/cache/jfusion/css/universal_1548d2120ad75b8ffe648119a9b1589a.cssI might also not that this plugin for copper mine is NOT plugin specific. it is a universal plugin that aim to be able to sync with almost all software out there. this is also why it uses curl for the frameless view. as a real integration (all tho better, would require me to define globals and so on..)
anyway if there at a feature time comes a huge userbase for it we can always look in to creating a coppermine plugin on its own =)
-Thanks for listening!
Morten