The next beta does 1b) but why do you want a default namespace? I can do it easily - but I cant quite see how you would use it.
That was mostly a minor convenience because I usually keep separate projects for different set of classes and everytime I have a bunch of empty folders in my projects.
One VS project can contain a set of classes inside "mynamespace.UI" and another set of classes inside "mynamespace.network" while another VS project can contain a set of classes inside "mynamespace.flashUI".
If I am in this kind of situation, usually, I have to create the projects with an empty folder called mynamespace and have my classes inside the subfolders.
Having the possibility to specify the root will give me the possibility to save the VS projects inside the folder "mynamespace" (or getting rid completely of complex structures of empty nested folders) and having just folders that contain the classes in my projects.
Usually the compiler doesn't complain if I am working with classes inside the same namespace and the folder scope is not starting from the root of the namespace path.
Like I said this is mostly a minor convenience to me (and probably I am really used to it because C# allows me to do that
) but the most important feature was 1b) and I am glad that you have fixed it.
Do you have already a date scheduled for the release of the intellisense fixes?
If not anytime soon, are you accepting an extra tester?