Re: imaging model (was: JPush)
Ralf Juengling <[email protected]>
| Newsgroups | gmane.lisp.lush.devel |
|---|---|
| Message-ID | <[email protected]> |
I think I got the idea, Thanks. So, how serious a candidate is cairo today? I looked at the website and almost all the backends are vaporware at the current time. The library seems to be pretty young. What other alternatives are there? You mainly have in mind existing rendering libraries with all the backends you want, I guess, and we would just have to write interfaces to the library. - Display Ghostscript http://www.gyve.org/dgs/ seems to be dead/unmaintained - Libart http://developer.gnome.org/doc/whitepapers/canvas/x134.html Is mature and has been used in gnome for a couple years now. Don't know about backends. - OpenGL Yann, you mentioned that. Is there a subset of OpenGL that would make a decent 2d imaging model? There is mesa, an open implementation. It has been around for a while and seems to support a lot of backends, http://www.mesa3d.org/systems.html, but no document description languages like PS. What else? Ralf On Thu, 3 Nov 2005, Yann LeCun wrote: > On Wednesday 02 November 2005 08:23 pm, Ralf Juengling wrote: >> On Wed, 2 Nov 2005, Yann LeCun wrote: >>> - a better imaging model for the default graphic driver >>> (the existing one is based on the old Xlib). >> >> What is a graphics driver's "imaging model"? You might point >> to something I know (e.g., does matlab have an "imaging model")? > > An imaging model is the set of graphic primitives that are given to > you for drawing stuff. For example, Xlib, OpenGL, Imlib, PostScript, > PDF, SVG, Quartz, and Cairo all defined an imaging model (some of them > are also APIs). An imaging model is not exactly an API, because you > could have several APIs for the same imaging model, and a single API > could be compatible (or emulate) several imaging models. It's more > like a set of behaviors. > > Xlib, which Lush uses for its default driver, is pixel-map oriented > and doesn't allow such things are resolution independence, > alpha-blending/compositing, antialiasing, 3D, texture mapping, etc. It > was the hottest thing in 1988, but it's badly out of date now. > > If we write a new graphic interface for Lush with more functionality, > we might want to consider an imaging model that can be implemented > with standard APIs on various platforms of interest. We might want to > use Cairo, which has backends on Linux, Windoze and Mac that > can talk to X, OpenGL, Quartz, PDF, PNG, PostScript, SVG, > frame-buffer,.... > See http://cairographics.org/introduction > > -- Yann > > > > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php