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.

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.


, that will cause the painter to be rebuilt
> by the corresponding access method in that category.  Example: The class
> variable CodePainter holds the painter for normal method code, and is
> accessed and lazily initialized by the instance method 'codePainter'.

Why not just trigger an event to cause the needed rebuildings?

>
>>Also, I want to port my
>> formatter/colorizer from VW.  Has anyone done any work in this area
>> yet?
>
> Not that I know of.
>
>> How do I temporarily switch off type annotations everywhere, without
>> actually deleting them?
>
> There isn't a way to do that right now, since we didn't see that as a
> desirable feature (it would be like turning off comments- they make the
> code
> easier to understand).

I experiment with strict grammatical disciplines in Smalltalk and in
programming schemes building on top of it.  This makes the annotations
ultimately unnecessary and undesireable (the full explanation would
lead too
far), but I want to be able to turn them back on during my
acclimation/conversion period, when I lose my way in the new image.


Shaping

>
> -Dave
>
>>
>> Shaping
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
 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
-~----------~----~----~----~------~----~------~--~---