<div>Which is better if you want Smalltalk code to be includeable in the base Squeak?</div>
<div> </div>
<div>MIT or LGPL?</div>
<div> </div>
<div>I have a large Generator Package(s) that is all marked up as GPL in Dolphin Smalltalk.</div>
<div> </div>
<div>I think that this Generator stuff could take a place alongside Collections and Streams</div>
<div>in the base Squeak / Croquet image.</div>
<div> </div>
<div>I am reluctant to think about porting from Dolphin to Squeak. I tend to sign myself</div>
<div>up for things that I can't do. I'm gung ho for about a day and then reality sets in.</div>
<div>It's easier just to talk. To dream. But I guess the idea that it might get into the Squeak</div>
<div>image makes it more attractive. To try. To even think about.</div>
<div> </div>
<div>( Some resistances come to mind.</div>
<div>Perhaps it's not up to the generally accepted practice of including practically zero</div>
<div>documentation? And could not be included for that reason? The change log is</div>
<div>too big. There are long rants in there. poetics. nonsense. the included text</div>
<div>looks like some Mandelbrot set? With too many usage examples and ideas</div>
<div>written into the comments? )</div>
<div> </div>
<div>Are there any automated ways of going from Dolphin to Squeak?</div>
<div>File out Class by Class and fileIn and copy method by method?</div>
<div>If I strip out some stuff from Dolphin Packages would they just fileIn to Squeak?</div>
<div>But if there are no loose methods in Squeak Packages then the whole thing is</div>
<div>impossible.</div>
<div> </div>
<div>It would be cool if there was some standard way to transfer code between the</div>
<div>different Smalltalks. But I guess they are just too different. And the idea of</div>
<div>making a commonality comes and goes. But never sticks.</div>
<div> </div>
<div>-Kjell</div>
<div> </div>
<div> </div>