Newbie squeak question

Alan Lovejoy sourcery at pacbell.net
Fri Jul 2 22:03:58 UTC 1999


Jeff Carr wrote:

>  Ok I give up --- I am missing something very basic.  When in a squeak
>  project, I can FileIn a *.st file.  Then what?  I can view the class
>  structure, etc --- but how do I build something that executes?  The *.st
>  file I have should result in a new browser type, with special functionality.

By default, filing in code results only in a) adding new methods, b) adding
new classes, c) changing existing methods, d) changing existing classes,
e) removing old methods, f) removing old classes, g) recategorizing
classes and/or methods, or h) initializing classes.  Additionally, a file-in
can evaluate expressions as though they were "do its" in a workspace.
But any such general expressions must be added by hand; they will not
be automatically included in a file-out.  It is often the case that new tools
that one files in will not appear on the system menus unless and until
the cached menus are rebuilt.  Changing the code that builds a menu
does not automatically cause a cached menu to be rebuilt.

Without more information about the code you filed in, it is unclear what
you may need to do to make it fully operational.

--Alan


Content-Type: text/x-vcard; charset=us-ascii;
  name="sourcery.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Alan Lovejoy
Content-Disposition: attachment;
  filename="sourcery.vcf"

Attachment converted: Anon:sourcery.vcf 5 (TEXT/R*ch) (0000AD76)





More information about the Squeak-dev mailing list