It is best to be in a Morphic project when you file this code in. The
easiest way is to use the screen menu, select "open...", select "project
(morphic)", click inside the small orange window that pops up to "enter"
the Morphic project, pop up the Morphic screen menu, select "open...",
select "workspace", from your web browser you should select all of Bob's
page, copy, return to Squeak, paste into the workspace, double click
past the end of the text in the workspace to select it all, pop up the
workspace menu, select "more...", select "file it in" -- you should see
a little progress window for "Reading a stream", then a window titled
"about UIExample" should pop up telling you how to begin. Yes it's worth
the bother to see it.

(This code comes down as Unix format and unless you convert the file to
Mac format, or copy it into the workspace to file it in like above, you
*still* get the screwed up end-of-line in Squeak when you look at the
source in the browser. I thought this sort of nonsense was fixed in the
standard Squeak distribution by now. A filein should _always_ be
converted to the correct eol convention before it gets into the image.)

-- Dwight

Tim Cuthbertson wrote:
> 
> I (a newbie) cannot figure out how to get this code into my image.
> 
> I have copied it from my web browser screen into a Workspace, selected all
> of it, and gave the Do It command. This resulted in an error (I think it was
> "Nothing else expected").
> 
> Then, I tried selecting it all from the web browser screen, pasting it into
> a file, opening the file in a Smalltalk File List, selecting it all, and
> clicking menu item "File it in". No error message, but the new classes were
> still not in my image.
> 
> How do I use this code?
> 
> Thanks,
> Tim
> 
> ----- Original Message -----
> From: Bob Arning <arning at charm.net>
> To: <squeak at cs.uiuc.edu>
> Sent: Sunday, June 20, 1999 8:37 PM
> Subject: Re: genuine squeak newbie
> 
> http://www.charm.net/~arning/BobsUI.13Jun624pm.cs.txt
> 
> This is a simple data-entry screen with a few data types and edits. A
> possible approach would be to examine this with an eye to really
> understanding it (I kept it a bit simple so that the totality was
> graspable). Once you think you understand it, think about how you would like
> to extend it. I will be happy to answer questions about what is there or to
> offer suggestions as to future improvements.