Hello,
I just started with a fresh 2.3 image, downloaded and filed in all of the updates from the server, and then changed my default text size (TextStyle changeDefaultTextSizeBy: 1).
This worked for the most part, but when I am in a Morphic world and try to use the various browsers/workspaces/etc from the 'tools' flap, the change does not (fully) apply. For example, when I create a new SelectorFinder from the 'tools' flap, the 'PluggableList' portions (used to display selector names, and specific methods) have the font changed, but the 'PluggableText' portion (used to enter selector name fragments) still have the old font size.
I surmise that this is because the 'tools' flap creates creates new tools from a prototype, which it stored at the time of the update (before I changed the default text size). My question is: what is the best way to change this? I know I could start with a fresh image, but I want to learn about Morphic while I'm at it.
I have several thoughts. One is to inspect my way down to to relevant 'PluggableText' components in the flap, and manually change the text size. I have a feeling this isn't the best way.
Another idea is to replace the old prototypes with new ones by somehow dragging them off and the new ones on. I don't really know how to go about this, but I'm sure it can be done. If possible, this is the option I'd like to use (because of the learning it involves).
Yet another idea is to destroy the global flaps, and rerun whatever initialization method(s) created them during the filein process. I don't know how complicated this would be; I've been unable to find out how to do this, either.
The last idea is to start from scratch, and do the font size change first. Like I said, I'd prefer not to do this.
Sorry about the length, and thanks very much for any help, Josh
Josh -
Yet another idea is to destroy the global flaps, and rerun whatever initialization method(s) created them during the filein process. I don't know how complicated this would be; I've been unable to find out how to do this, either.
Having just visited this region for other reasons (space reclamation), I offer the following suggestion:
1. Use the preferences... window to set useGlobalFlaps to false.
2. Browse to System-Support/Utilities
3. In the class pane choose class vars to inspec the class variables
4. Select the item 'FlapTabs' -- it will show an orderedCollection
5. In the value pane, select all that, replace it by 'nil' (without the quotes), and choose 'save' from the menu or use cmd-s
This should put you in such a condition that, if you then turn the useGlobalFlaps preferences on again, it will recreate things from scratch.
Good luck.
- Dan
----- Original Message ----- From: Dan Ingalls DanI@wdi.disney.com To: Joshua Gargus gargus@ugrad.cs.ualberta.ca Cc: squeak@cs.uiuc.edu Sent: Thursday, March 25, 1999 1:17 PM Subject: Re: default text size problem.
Josh -
Yet another idea is to destroy the global flaps, and rerun whatever initialization method(s) created them during the filein process. I don't know how complicated this would be; I've been unable to find out how to do this, either.
Having just visited this region for other reasons (space reclamation), I
offer the following suggestion:
Use the preferences... window to set useGlobalFlaps to false.
Browse to System-Support/Utilities
In the class pane choose class vars to inspec the class variables
Select the item 'FlapTabs' -- it will show an orderedCollection
In the value pane, select all that, replace it by 'nil' (without the
quotes),
and choose 'save' from the menu or use cmd-s
This should put you in such a condition that, if you then turn the
useGlobalFlaps preferences on again, it will recreate things from scratch.
Dan/Reinier, I followed the above procedure for recreating all global flaps, and it seems to have worked (all new windows have the expected highlighting attributes when mousing over close and grow boxes). However, the newly created windows seemed to be clipped behind the example Morphic browser. Is this correct? Why are the new windows scoped tothat morph's viewport in the current project?
Regards.
Joshua,
Just evaluate:
Utilities reinstateDefaultFlaps
and all will come right -- the prototypes in the Tools flap will be reconstituted, and will reflect your changed default text size.
-- Scott
At 9:23 AM -0800 3/25/99, Joshua Gargus wrote:
Hello,
I just started with a fresh 2.3 image, downloaded and filed in all of the updates from the server, and then changed my default text size (TextStyle changeDefaultTextSizeBy: 1).
This worked for the most part, but when I am in a Morphic world and try to use the various browsers/workspaces/etc from the 'tools' flap, the change does not (fully) apply. For example, when I create a new SelectorFinder from the 'tools' flap, the 'PluggableList' portions (used to display selector names, and specific methods) have the font changed, but the 'PluggableText' portion (used to enter selector name fragments) still have the old font size.
I surmise that this is because the 'tools' flap creates creates new tools from a prototype, which it stored at the time of the update (before I changed the default text size). My question is: what is the best way to change this? I know I could start with a fresh image, but I want to learn about Morphic while I'm at it.
I have several thoughts. One is to inspect my way down to to relevant 'PluggableText' components in the flap, and manually change the text size. I have a feeling this isn't the best way.
Another idea is to replace the old prototypes with new ones by somehow dragging them off and the new ones on. I don't really know how to go about this, but I'm sure it can be done. If possible, this is the option I'd like to use (because of the learning it involves).
Yet another idea is to destroy the global flaps, and rerun whatever initialization method(s) created them during the filein process. I don't know how complicated this would be; I've been unable to find out how to do this, either.
The last idea is to start from scratch, and do the font size change first. Like I said, I'd prefer not to do this.
Sorry about the length, and thanks very much for any help, Josh
At 9:23 AM -0800 3/25/99, Joshua Gargus wrote:
... Another idea is to replace the old prototypes with new ones by somehow dragging them off and the new ones on. I don't really know how to go about this, but I'm sure it can be done. If possible, this is the option I'd like to use (because of the learning it involves).
Yes, indeed! The default flaps are only intended to serve as examples of what can be done with flaps, the assumption being that users will modify them to suit their own purposes.
If you want to replace the "Tools" flap's prototypical browsers windows, etc., with new ones that reflect your changed font defaults, you could proceed as follows:
(1) From the "flap" menu on the Tools tab, suppress "mouseover" and "dragover" behavior temporarily, so that the flap won't keep disappearing at inopportune moments while you try to manipulate its contents.
(2) From that same "flap" menu, tell the Tools flap to "suspend parts bin behavior". This will allow you to remove items from it, add new items to it, and rearrange its contents.
(3) Open a Preferences editor and set "allowSysWindowEmbedding" to true. This is necessary in order for the flap (or *any* paste-up area other than the World itself) to be willing to let you drop a window into it.
(4) Drag the old "System Browser" miniature out of the flap and drop it in a trash can.
(5) Get a fresh System Browser in the traditional way from the open... menu.
(6) Drop that new System Browser onto the interior of the Tools Flap. It will reduce to a miniature. Position it as you wish within the flap.
(7) Repeat steps 4-5-6 for anything else you want to change in the flap.
(8) Now reverse the settings you made in steps 1, 2, and 3, and you're done.
Note that any manual modifications you made to the new Browser between steps 5 and 6 (e.g. changes to title, color, size) will be in the new prototype, so that new browsers you tear off from the revised flap will reflect those changes.
This sequence is a little more complicated than many other flap modifications you might be motivated to make, because it involves temporarily suspending parts-bin behavior and it also requires temporarily suspending a window-handling preference.
In contrast, if you've created a simple button and wish to have it available on the left flap, you could just drag it over that flap and drop it there, and that would be all it took. Similarly, you could deposit a TextMorph there, and the result would be that the same body of text would be universally available in all your (morphic) projects, etc.
Hope this helps,
-- Scott
squeak-dev@lists.squeakfoundation.org
-
Dan Ingalls -
Joshua Gargus -
shaping＠bigfoot.com -
SWallace