On Mar 19, 2011, at 4:05 PM, Guillermo Polito wrote: > > > On Sat, Mar 19, 2011 at 8:45 AM, Stéphane Ducasse <[email protected]> > wrote: > I have another problem is: > imagine we do not match category to package so this means that users > will have to add explicitly their categories > to the package > > So I load Foo > > I get the contents of > Foo and Foo-B categories into RPackage Foo. > > I save Foo and it save the classes in Foo and Foo-B (categories are > not considered just rpackage contents) > > Now > I add a category Foo-C (because the browser let me do it) > -> may be system should ask me: do you want to add to the Foo > RPackage? > -> may be I should do it explicitly > > Better is that we have a browser only showing RPackages > > Then what happen if I add a new class Zork in Foo-C > > The class category will be Foo-C and again does the system has to check in > which package it should put the class? > How do I map Zork class? > -> explicitly? > -> What happens if I do it via a browser only showing classes and > categories? > > > So the mapping Category to package is not that bad else we will have to check > *****ALL***** the time > if a class should be put in a package or not and compare category with > package names. > And we will have all the crap of matching with sub subc.... most specific > categories.... > > So I would like to community to react to this mail because this is important > and people will get frustrated after. > > I think that a one to one mapping to category is a good idea. > + having a browser just showing packages would be good. > > Yeap, I think that giving tool support is the key here. > I don't like the implicit approach because it'll lead to miss-understandings > and eventually RPackage can be used in several ways other than One-to-One > with categories. > > So, something I'd like to ask, since I'm not entirely aware of the subject: > Which are the concepts behind a Package and a Category? should they be the > same or not? why?
RPackage does not rely on any conventions: everything is explicit: you add you methods/class to the package. Now my point is how to make the transition smooth. Stef
