>> BTW, now we have Igor's method trailers we can start playing with more than >> two source files, e.g. /not/ appending a Monticello package's source to the >> changes file, but merely adding it to a special directory, e.g. sources. > > Yes. I told about potential use of new trailers, where we can implement a > model > for storing/retrieving source code from any kind of storage. > > Unfortunately it requires some remodelling of system's source-code > management system, > to get rid of hard-wired SourceFiles code and add an abstract layer > for source management. > So we could implement different source managers, where .source and > .changes will be just default one. > > One of my ideas was to use CouchDB for storing everything there. It > opens quite interesting opportunities, > like being able to browse a history of some particular method up to > 1.0 squeak release :) > > @Stef: add this to pharo todo list :)
but this one is on the path of veronica phd so we should do it fast. Veronica likes to work under pressure so this is good. stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
