Remove namespace for easy scripting

[GoogleCodeExporter]

I would like to see main scripts to be in the global namespace to avoid to add 
"using" statements at the beginning of each script that may use HoTween.

I do see why you wanted to see your classes added to specific namespaces to 
avoid class conflicts yet I believe you could leave the core feature classes 
and types in the current namespace system but place the core classes one would 
use in Unity3D scripts would be easier to use if they were placed within the 
global namespace.

Thanks for considering this enhancement request.

Original issue reported on code.google.com by philippe...@indiefreaks.com on 3 Dec 2013 at 1:16

[GoogleCodeExporter]

I understand these reasons, but I'm afraid it's not possible for two reasons:
1) too late :P I could think about it for HOTween V2, but otherwise it would 
break backwards compatibility (unless I create a rather illogical namespace 
hierarchy)
2) as far as I know, there are other Unity packages that use the same names as 
the ones used in HOTween's core (like Tweener), so name conflict would be 
unavoidable

Original comment by daniele....@gmail.com on 3 Dec 2013 at 1:31

• Changed state: WontFix

[GoogleCodeExporter]

Understood.
If you plan on a V2, please consider this enhancement request and naming your 
classes in such a way they would have high probabilities to avoid conflicting 
with other packages.

Thanks ;)

Original comment by philippe...@indiefreaks.com on 3 Dec 2013 at 2:55

[GoogleCodeExporter]

I will seriously consider it, though going namespace-less scares me :D

Original comment by daniele....@gmail.com on 3 Dec 2013 at 5:45