Hello João, > This makes sense. Yes. Take a look at umit dir on trunk: > > drwxr-xr-x 4 ignotus users 4096 2009-04-22 09:52 core/ > drwxr-xr-x 4 ignotus users 4096 2009-04-22 09:52 db/ > drwxr-xr-x 4 ignotus users 4096 2009-04-29 00:54 gui/ > drwxr-xr-x 5 ignotus users 4096 2009-04-22 09:52 interfaceeditor/ > drwxr-xr-x 3 ignotus users 4096 2009-04-22 09:52 inventory/ > drwxr-xr-x 4 ignotus users 4096 2009-04-22 09:52 merger/ > drwxr-xr-x 3 ignotus users 4096 2009-04-29 00:14 plugin/ > > If there will be "zion", "umpa" and "pm". There will be some things in > core that can be used by them (e.g. UserConf.py, I18n.py) and a huge > number of it that is Umit specific (e.g. Nmap*, OS*). > So, maybe a "common" sub-package must be provided. I think "radialnet" > should be moved to this dir too. And, I can't think in a better place > name that is not umit.umit for the rest of "core" and "gui".
That's something to consider, indeed. That's why following this umit.something pattern is better for integration. Cheers! -- 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 ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
