methods for license conversion
ssastre at seaswork.com
Mon Jul 9 20:08:28 UTC 2007
I had to agree to forget implementation anecdotical (and temporary)
madness and standing on OpenGL shoulders.
> -----Mensaje original-----
> De: squeak-dev-bounces at lists.squeakfoundation.org
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] En
> nombre de sig
> Enviado el: Domingo, 08 de Julio de 2007 20:10
> Para: The general-purpose Squeak developers list
> Asunto: Re: methods for license conversion
> On 06/07/07, Blake <blake at kingdomrpg.com> wrote:
> > On Thu, 05 Jul 2007 14:14:50 -0700, tim Rowledge
> <tim at rowledge.org> wrote:
> > > Don't know the answer to that one; I was under the
> impression that
> > > Cairo was 'just' graphics but I haven't really researched
> it per se.
> > > Given
> > It's vector graphics, though you can build a UI with it. I
> > (incorrectly) thought it mapped to native tools.
> About Cairo, as noted on site:
> Cairo is a 2D graphics library with support for multiple
> output devices. Currently supported output targets include
> the X Window System, Win32, image buffers, PostScript, PDF,
> and SVG file output.
> Experimental backends include OpenGL (through glitz), Quartz, and XCB.
> 1 fact: i assume it proposes a cross-platform layer of
> abstraction on top of existing graphics libraries (like
> DirecX/OpenGL whatever).
> 2nd fact, i dont like: its 2D only.
> I prefer to directly use OpenGL (which is already a
> cross-platform) and provides enough capabilities to develop a
> UI using 2D graphics or 3D (like composite desktops/games
> e.t.c). I think using OpenGL directly for creating UI is
> better choice for squeak.
> I implemented a scratch replacement of Canvas/Display stuff
> to use GL via FFI for drawing morphic with squeak.
> Premiliary, based on rough calculations it renders desktop 3
> to 5 times faster than currently used Balloon/BitBlt. Also, i
> noticed that changes needed to make use of GL with morphic
> architecture is minimal, and opening a wide range perspective
> for creating a stunning and fast UI for squeak, not limited
> by third-party libraries, which providing own abstraction layer(s).
> Anyways, to use modern graphics cards features with squeak,
> we have no choice but to use some of the existing external
> libraries. And OpenGL is a winner here, without a doubt.
> > > The real point though is simply that we can do something
> > > when we have tools that allow us to start from
> almost-scratch whilst
> > > still having an existing system to build the new code in.
> Spoon can
> > > provide a way to develop a chunk of code in an image with all the
> > > tools we're currently used to, save it out as a spoonful
> and have the 'new '
> > > image be spoon-fed the package. It's like
> cross-development without
> > > so much cross :-)
> > I think that sounds great. But don't we need Spoon first?<s>
> > I also think that such a project would be an excellent
> opportunity to
> > show the usefulness of traits.
> > ===Blake===
More information about the Squeak-dev