Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52621 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79177 invoked from network); 1 Jun 2011 04:45:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Jun 2011 04:45:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.163 smtp163.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.163] ([207.97.245.163:33011] helo=smtp163.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D3/21-02790-4E3C5ED4 for ; Wed, 01 Jun 2011 00:45:25 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp56.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 592B33D85DB; Wed, 1 Jun 2011 00:45:22 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp56.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id C13893D85CD; Wed, 1 Jun 2011 00:45:21 -0400 (EDT) Message-ID: <4DE5C3E0.7050200@sugarcrm.com> Date: Tue, 31 May 2011 21:45:20 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Hannes Landeholm CC: "internals@lists.php.net" References: <36AF85D9-01D5-43B0-9456-A288E740A85B@roshambo.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] removing some cruft From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Yeah, I was wondering why the magical logo thing was implemented like that. > Just use the href= "data:image/png;base64,..." scheme instead if you really > need a logo there. Combine that with smaller size and heavy jpeg compression > and it shouldn't make the HTML /that/ bloated. Well, there are some browsers that don't support data: (ahem, IE7) but I'd say cleanness is more important and those browsers must die anyway :) That, however, doesn't solve problem with credits page, and IE hates navigable data: (meaning HTML) so we couldn't use it for credits. But if someone submits patch for images, I don't see a problem with that. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227