On Jan 11, 2010, at 10:41 PM, Michael Roberts wrote:
CodeLoader is referenced in the ProjectLauncher, but assuming we don't want to support Pharo in a browser (??) then you could strip out the HTTPClient checks, leaving the part that reads from disk.
It would be nice to keep pharo in the browser now the question is can we do it without somebody payed to maintain it to be compatible with each version.
cheers, Mike
On Mon, Jan 11, 2010 at 2:09 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Jan 11, 2010, at 3:04 PM, Mariano Martinez Peck wrote:
Ok...and what about CodeLoader? I ask because it seems it uses ImageSegment to export categories and classes to disk.
Anyone uses it? If not --> remove.
I think it's just another lefover experiment.
Marcus
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project