Compability with Domain Conf

Domain Variable was specifically built to replace Domain Settings + Domain Configuration, and personally I'm not really interested in making them compatible... I'd also be happy to look at patches of course, but I won't work on it.

[...] I would really like to use both simultaneously to manage domain specific settings on system forms in a number of third-party modules that doesn't use the Variable API?

Which third-party modules are you talking about? Adding support for the Variable API is usually not too complicated, so maybe support can be added to them!?

In case you haven't seen it, here's a list of known differences between this module and domain conf/settings/theme.

Google Analytics already has (at least partial) support for variable, see #1843960: Declare variables compatible with Domain Access; If you look at googleanalytics.variable.inc, you see everything that needs to be done when adding support: implement hook_variable_info(), and set the multidomain key to TRUE.

You can also put the hook_variable_info() implementation into your own module; so if any module owner doesn't want to implement the hook himself, you could do it in a separate module.

I think it's good to either keep the compatibility with Domain Conf or make the upgrade path module (now in sandbox) an official module or a feature of Domain Variable. I ran into situation where I needed to have different settings for different domains and languages. This module solves the issue perfectly but I was not confident enough to replace all the currently domain specific variables to use this new approach.

what would we need to make these modules compatible? I still have the strong feeling that switching to domain variable won't fit my needs as there is such an overwhelming amount of modules not defining there varaibles in hook_variable_info let alone defining them as domain aware variables.

could someone point me into the right direct of source code to look at? I'm willing to sacrifice some of my time getting this one done

mission state: accomplished. if anyone is interested I could set up a sandbox module.

under the hood: I have simply mimicked to domain_settings behavior (in fact, I'm attaching a new submit handler if domain_settings did so) and process the form data, pushing variables into the variable_store with variable_realm_set, variable_realm_get and variable_realm_del if needed.

works like a charm for me.

@attisan interesting, I would likely use you code to do some tests.

@pwiniacki see https://www.drupal.org/sandbox/attisan/2535610

From git://git.drupal.org/sandbox/attisan/2535610
 * [new branch]      7.x-1.x    -> origin/7.x-1.x
fatal: Couldn't find remote ref HEAD

@kerios83 - fixed. sorry about that.