On 01.09.2011, at 15:17, Jecel Assumpcao Jr. wrote: > Was being able to input drawings one of the good things? There was one > Lisp GUI that put a lot of effort into allowing you to input objects > instead of just text. It did that by outputting text but keeping track > of where it came from. So if you pointed to the text generated by > listing the contents of a disk directory while there was some program > waiting for input, that program would read the actual entry object. > > It is frustrating for me that while the Squeak VM could easily handle an > expression like > > myView add: <yellowEllipseMorph> copy. > > I have no way of typing that. I can't use any object as a literal nor as > input. In Etoys I can get close enough by getting a tile representing > the yellowEllpiseMorph from its halo and use that in expressions. In > Self I could add a constant slot with some easy to type value, like 0, > and then drag the arrow from that slot to point to the object I really > wanted. It was a bit indirect but it worked and I used this a lot. The > nice thing about having something like this is that you never need > global variable again.
In a Squeak workspace you can enable the "create textual references to dropped morphs" checkbox which at least lets you do this interactively. Saving as project and loading keeps this working. However, outside of the Etoys environment hardly anyone in the Squeak community uses projects - all exchange is based on text files. While the system itself is nicely object-based, its boundaries are dumbed down to a manageable level. Lots of tools exist to deal with text, but storing, sharing, or merging objects is still hard. Perhaps because in Smalltalk objects are still too tightly bound to their environment? - Bert - _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
