> It will be a overhead on gui and core. But no objections there. In the past > we made it with RadialNet and it is reasonable.
I got your point... but I wouldn't consider overhead, as it will consume the same amount of chars: umit.scan.gui.radialnet umit.gui.scan.radialnet What I was thinking about, was to have the bigger scopes in the namespace first, like: umit. scan. (smaller scope) gui. (smaller scope) radialnet. (smaller scope) whatever_on_radialnet (smaller scope) This way, it looks like you're drilling down in the scope. If we do umit.scan.radialnet.gui, it looks like we expect something different inside radialnet, then we discover that it also has a gui. That's the reason, as far as I could express. I'm not sure, though, if I did it well. Let me know if you didn't understand... Thinking on this perspective, what do you think about it? Kind Regards, -- Adriano Monteiro Marques http://adriano-marques.blogspot.com http://www.umitproject.org http://www.pythonbenelux.org "Don't stay in bed, unless you can make money in bed." - George Burns ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
