re: TrueType font support and 3.6

> [TrueTypeTextStyle] works ok, looks beautiful but seems to slow down
> my system quite a bit. We need profiling and improvements to make it
> suitable for default usage - something I think very important.

	It doesn't slow mine down, and it's not rediculously faster than yours
(mine's 500 MHz, yours is 200?)  If profiling reveals this to be
something that only affects, e.g., old RiscOS machines, I'd prefer to
release it and fix the problem later. This is very important. I would
even be happy if we just released it without profiling, since it's fine
on all the Unix, win32, and MacOS machines I've tried it on.


-C

--
Craig Latta
http://netjam.org/resume
[email protected]
Smalltalkers do: [:it | All with: Class, (And love: it)]
From [email protected] Fri Jun 20 19:31:13 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 23527 invoked from network); 20 Jun 2003 19:31:13 -0000
Received: from mail.gmx.net (213.165.64.20)
  by mail.theinternetone.net with SMTP; 20 Jun 2003 19:31:13 -0000
Received: (qmail 9169 invoked by uid 65534); 20 Jun 2003 19:31:13 -0000
Received: from gruenderlabor.cs.uni-magdeburg.de (EHLO atlantis) (141.44.23.5)
  by mail.gmx.net (mp008) with SMTP; 20 Jun 2003 21:31:13 +0200
From: "Andreas Raab" <[email protected]>
To: "'Discussing the Squeak Foundation'"
	<[email protected]>
Subject: RE: [Squeakfoundation]KCP & 3.6
Date: Fri, 20 Jun 2003 21:30:40 +0200
Message-ID: <000001c33762$6f1a67b0$1f00a8c0@atlantis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <[email protected]>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-BeenThere: [email protected]
X-Mailman-Version: 2.1
Precedence: list
Reply-To: Discussing the Squeak Foundation
	<[email protected]>
List-Id: Discussing the Squeak Foundation
 <squeakfoundation.lists.squeakfoundation.org>
List-Unsubscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=unsubscribe>
List-Archive: <http://lists.squeakfoundation.org/pipermail/squeakfoundation>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2003 19:31:14 -0000

> Do the "somewhat larger" issues mean problems as soon as we insert the
> DecPools, or changes when we convert the image?

The latter. The problems really come from either somewhat strange uses =
of
pool dictionaries (e.g., lower-case strings as keys) or from uses where =
the
pool is extended dynamically (TextConstants).

> if the second, does this mean it makes sense to insert the code, but
> convert the rest of the image in 3.7, or do you think this would be
> confusing?

I think it's perfectly reasonable and what I anticipated anyways. Even
though the remaining pools "ought to be converted" there is no =
requirement
for doing it in 3.6 - we've been living with them for so long and the =
places
where we had an immediate need for fixing them are fixed.

Cheers,
  - Andreas