Before Ext JS 4 I used to define classes like:
Code:
window['http://my_unique_namespace_id.com/appid'] = {....};
.....
(function(my_ns){

    my_ns.myClass = Ext.extend(Ext....., {
        .......
    });

})(window['http://my_unique_namespace_id.com/appid']);
The point is to allow complete and straight-out freedom in naming namespaces rather than just sticking with something alfanumeric that would be appropriate for using as a JavaScript identifier.

Now I can't see a way to continue using the same practice while taking advantage of the Ext.define feature in Ext JS 4. Indeed, the following won't work because Ext seems to be always binding namespaces to what it thinks global namespace is.

Code:
(function(my_ns){

    Ext.define('my_ns.myClass', {
        ....
    });

})(window['http://my_unique_namespace_id.com/appid']);
Is there a way to use Ext.define for defining a class within an arbitrarily given namespace object, rather than just giving a string like 'my_ns.myClass' to parse?