RE: Fonts; syntax coloring; type annotations

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Shaping
> Sent: Monday, December 25, 2006 2:01 AM
> To: Strongtalk-general
> Subject: Re: Fonts; syntax coloring; type annotations
>
>
>
> > I'm not sure why you would want a monospaced font, but please yourself.
>
> The reasons are old (~12 years or so) and involve some combination of
> strict typography and less than excellent eyesight.
>
>
>   The
> > reason your changes aren't taking effect is that the painters used to
> > render
> > the programming environment are cached in class variables in class
> > ProgrammingEnvironment, so they are only built once (Painters hold the
> > graphics state for rendering).  Look at the methods in the instance
> > category
> > 'private-painters' in ProgrammingEnvironment.  If you set any
> of the class
> > variables in that class to nil (or just save and restart the image after
> > changing the font specification)
>
> I saved and restarted the image after changing the font in a method
> pane (I
> could not find any other place to do this, and am assuming that the
> scope
> for the change is all method panes; not sure).  There was no change.
>
> I tried setting CodePainter to nil, saving, and restarting.  This did
> not
> work either.

My last email outlined how to change the font the browsers use for code.
Changing the font using the context menu in a method pane as you describe
simply changes the font used for subsequent characters typed at that
insertion
point, and is a feature of text windows, not of the browser; the font
changes made that way are not persistent in any way.

Setting the CodePainter to nil should work.  If it doesn't appear to change,
then you are probably not choosing a font name that Windows knows, and the
'best fit' font is usually 'Lucida Sans', which is what the programming
environment uses already.  FontSpecs are used to specify the font you
*want*, but the system (windows) is not bound by that; it picks the closest
font it thinks fits.  Try changing the point size first, that will always
change the appearance, that way you can see that your changes are taking
effect first.

> I feeling like I'm missing something basic.  When I save my image, and
> restart by double clicking strongtalk.exe, I don't get the same set of
> windows.
> I see that I've created the new .bst file, and suppose that this is
> being used, but
> I'm not sure now.  Dragging the .bst onto strongtalk.exe brings up the
> command
> window, briefly, but that is all.

Images in Strongtalk are not the same as in other Smalltalks.  Images are
not used for data/dev-environment persistence.  In Strongtalk right now,
only your *code* is saved between sessions.  So your changed font should be
saved, but not your windows or other state.  I agree that ideally
programming environment/browsing state would be saved between sessions, but
our design approach did not view the image as an appropriate place to jumble
code and programming environment state together, as in other Smalltalks.
The programming environment is not yet very sophisticated; it had just
started working at the point development originally stopped, and we simply
hadn't gotten to storing dev-env state yet.

-Dave


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---