From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Shawn O. Pearce" Subject: Re: [JGIT PATCH 0/3] Request for help: graph-based UI Date: Sat, 25 Jul 2009 13:59:36 -0700 Message-ID: <20090725205936.GF11191@spearce.org> References: <200907212140.32520.robin.rosenberg@dewire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Robin Rosenberg , Johannes Schindelin , git@vger.kernel.org To: Douglas Campos X-From: git-owner@vger.kernel.org Sat Jul 25 22:59:45 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1MUoLI-00022U-MD for gcvg-git-2@gmane.org; Sat, 25 Jul 2009 22:59:45 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752620AbZGYU7g (ORCPT ); Sat, 25 Jul 2009 16:59:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752618AbZGYU7g (ORCPT ); Sat, 25 Jul 2009 16:59:36 -0400 Received: from george.spearce.org ([209.20.77.23]:45143 "EHLO george.spearce.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752414AbZGYU7g (ORCPT ); Sat, 25 Jul 2009 16:59:36 -0400 Received: by george.spearce.org (Postfix, from userid 1001) id BD1DD381FD; Sat, 25 Jul 2009 20:59:36 +0000 (UTC) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Douglas Campos wrote: > Just a question.. all graphic things that we implement in swing aren't > usable inside eclipse with swt-awt bridge? They should be usuable inside the SWT-AWT bridge, but that bridge is really dicey to get working right sometimes. I had a lot of trouble with it at my prior day-job and am happy I no longer have to deal with it. For the most part, SWT and AWT are similar enough in their rendering that its possible to build most of a layout algorithm to be rendering API agnostic, and then permit implementation of AWT and SWT backends. But that still is duplicated effort, vs. straightforward code reuse. -- Shawn.