> Yeah btw i've the same structure in PM as well PM.Core and PM.Gui. But > are we creating a namespace? or simply collating software with no > cares about the general structure? > I mean it's reasonable to have > > org or yournamespacehere > | -> PM > | -> Gui > | -> Core > | -> umit > | -> gui > | -> core > > but it's a wrong design to have: > > umit > | -> gui > | -> core > | -> PM > > PM it's not a umit dependency and no software is using PM so no need > to have it under umit but i can understand your need to have under > another namespace.
I understand your point. But, if it is to be another namespace, what namespace would it be? Umit is the name of the organization *and* the name of the main interface. Perhaps the problem is that when we say Umit, you guys think it related to the main interface. But when we say Umit, we're saying the organization in this sense. So, it shouldn't come to the ground of it uses umit.core or umit.gui but to the ground of Umit Project, the organization that created and maintains these projects. >> Not quite. The problem we had with higwidgets was because people were >> installing zenmap and umit in the same machine. not applicable to our >> changes. Setup tools can deal with that easily also. > > I don't think. I mean we could have exactly the same problem with an > user having installed an old version umit and a brand new installation > of zion or whatever that uses umit.core. In this case, then, we're not safe at all because people will always update and will always get new stuffs there. The installation script must deal with this. >> Perhaps you said that because you were under the impression that all >> projects should remain under trunk. But it isn't the goal. As Luis >> said, you're baiscly going to do the following: > > But if that's not the goal why do that? The things are still separated. To define one namespace and a sane standard for modules. >>> 3) Problems in the distribution to mantain everything separate. But >>> this was the original situation? >> >> That's not a problem, as we have to maintain and keep things separated >> anyway. > > But are already separated. You want to join and then revert to > original situation :P Not quite. We're not putting things together because they have the same naming convention and namespace. As I said, we can keep them separated as they are, but we use the same namespace without moving any branch to trunk. 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
