> Let's say that Factor had a Mac Paint kind of application. I start it > up, draw a picture, and exit the tool. It leave the picture object on > the stack. I go into a new project vocabulary: > > IN: a-new-picture > > I then "assign" the object to a word name: > > :> the-picture > > At this point I can "synchronize" the system. I've created an object, > given it a name in a new "workspace" and done all of this without > dealing with any files.
What's wrong with having a picture object in the stack and then doing "foo.png" save-bitmap ? Now you have a file in the standardized PNG format (not some weird Factor-specific serialized object), not to mention it saves us from having to extend the vocabulary system to support binary data in vocabularies (how would you edit such a vocabulary in a text editor?). I think part of the reason Smalltalk didn't take off is because it took a very insular approach to dealing with the outside world. Let's not repeat their mistakes. Slava ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
