I am trying to build a custom widget, which I have placed in my own namespace mojo; the widget's name is mojo.View.

When I test in FireFox 3, everything works beautifully--well, except for my own bugs, but I can handle those.

When I test in IE7, I get the error:

Could not load 'mojo.View'; last tried '/dojotest.nsf/mojo/View.js'

(FYI, dojotest.nsf is a Domino database, but it serves web pages like any other web server, and so should not e an issue.)

I have tried googling for this, and found JBurke's example described here

I am running a custom build of dojo (I have to have it run concurrently with an older version).
I'd like to use dijit-all instead of having to download loads of tiny files, however dijit-all has "dojo" hard-coded throughout where I want to use my custom namespace.

Is there a way of building dijit-all, or configuring it to use my namespace?

Thanks in advance.

Is there a widget factory built into Dojo?

I'm trying to use dojo.data to load modules and widget stores dynamically. I can get to this point where I if I hardcoded selectedModule and selectedWidget the module namespace is set up and all files and dependencies have been ajaxed into dojo but I can't instantiate. Any ideas? Solutions? A better way to do this... kind of going for a dojo factory effect.

Hardcoded version works
new dojoCustom.form.Button({title: "Click Me!"}, "widgetContainer");

This version not so much...
eval("new " + selectedModule + "." + selectedWidget + '({title: "Click Me!"}, "widgetContainer")');

I noticed the other day that the dijit 1.1 priorities are up. Is there soon to be dojo 1.1 priorities posted? Any release dates for dojo 1.1? We're using 0.4 to do development right now due to portal (it's the only reason) due to the fact we'd need 1.0 and 0.4 to run concurrently without frames/iframes. We've hit a pivotal point in development that we could switch over to 1.0 if and only if the dojo namespace collision is addressed (ticket #4573). I'm just writing to see if there is any movement in that direction so we can plan to include 1.0 or to permanently continue on with 0.4.