Forgot to send to the list
---------- Forwarded message ---------- From: Guilherme Polo <[email protected]> Date: Fri, Feb 27, 2009 at 10:21 AM Subject: Re: [umit-devel] Putting all umit packages inside an umit package To: Francesco Piccinno <[email protected]> On Fri, Feb 27, 2009 at 10:18 AM, Francesco Piccinno <[email protected]> wrote: > 2009/2/27 Guilherme Polo <[email protected]>: >> On Fri, Feb 27, 2009 at 9:52 AM, Francesco Piccinno <[email protected]> >> wrote: >>> 2009/2/27 Rodolfo S. Carvalho <[email protected]>: >>>> On Fri, Feb 27, 2009 at 8:52 AM, Guilherme Polo <[email protected]> wrote: >>>>> Hi, >>>>> >>>>> Can we move to a cleaner namespace in umit ? I'm hoping to change it from: >>>>> >>>>> umitCore >>>>> umitCore.radialnet >>>>> umitGUI >>>>> umitGUI.radialnet >>>>> umitDB >>>>> umitInterfaceEditor >>>>> umitInterfaceEditor.selectborder >>>>> umitInventory >>>>> umitPlugin >>>>> >>>>> to: >>>>> >>>>> umit >>>>> umit.core >>>>> umit.core.radialnet >>>>> umit.gui >>>>> umit.gui.radialnet >>>>> umit.db >>>>> umit.interfaceeditor >>>>> umit.interfaceeditor.selectborder >>>>> umit.inventory >>>>> umit.plugin >>>> >>>> I agree totally with this structure. I like the idea of having a >>>> 'umit' central package. >>>> Additionaly, for UmitWeb, we can have the extra packages: >>>> >>>> umit.web >>>> umit.web.views >>>> >>> >>> Me too but I think that would be better that interfaceeditor is a leaf >>> of gui, like also inventory. For plugins i suggest that core and gui >>> part should be separetad, so the gui part will be included directly in >>> umit.gui while the core part will be umit.core.plugin. >> >> Uhm, maybe. But this kind of change requires better planning. >> umitInventory doesn't fit entirely into umitGUI, so I'm not sure why >> you are suggesting to it be entirely inside umit.gui. I also believe >> interfaceeditor doesn't fit entirely inside umitGUI, but I'm not >> suggesting anything since I haven't looked at its code. > > I'm not suggesting umitinventory in gui, i've not suggested that about > inventory, but I've only copied you original suggestion. Interface > editor doesn't fit entirely in gui but it's about gui so I think it's > better to have it as a leaf of gui, while the only gui related stuff > should be merged in the upper leaf. > > Btw every owner of a part should think about this refactoring and post > his proposal here before refactoring starts. > This is not a refactoring, it is just merely using umit as a main package with the other already existing packages as subpackages. You are planning a refactor, not my initial proposal. -- -- Guilherme H. Polo Goncalves ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
