And further to that the Common lib should be kept small and not try
to generalize
its support too much. Any specific areas that are being supported
(like internet tools -
if someone added SOAP and google API tools)
should be developed in the UserLib so that people can selectively
install that.
Which suggests now that "User Lib" is a slightly limited name.
Maybe "Code Respository"
On Mar 1, 2006, at 6:13 PM, Arie van Schutterhoef wrote:
But doesn't that correspond to migrating
specific classes out of a UserLib and into Common?
-A Common Lib suggests something that supports the whole of the
system and is important to the functioning of it. Without Common
Lib SC
won't run.UserLib is a private library or rather specific to one
way of
doing things
depends on a lot of things of course), without that SC can work
quite nicely.
AvS
_______________________________________________
sc-dev mailing list
sc-dev@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-dev