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.

Then we can after have a browser that show categories as tags and sort the 
classes accordingly.

So people please thing a bit because I want to make progress and losing my time 
is boring.


Stef

Reply via email to