Re: [Mesa3d-dev] OpenVG-1.1 support disabled
On Monday 17 August 2009 12:41:55 Andreas Pokorny wrote: > Hello, > > 2009/8/16 Zack Rusin : > > [...] > > Yes, the code required to actually read/rasterize and render glyphs is > > missing. So basically the entire api_text.c would need to be implemented. > > What's in there was basically done to pass the VG conformance > > setters/getters tests, but once it was decided that for a project we were > > working only OpenVG 1.0 will be a requirement I just never went back to > > finish 1.1. > > It wouldn't be too hard to finish this off (assuming addition of > > FreeType2 as a dependency of course) > > Why do think that FreeType is required? I thought converting from > outline curves to vg path data and managing the kerning info is done > by the user? VG only has to manage the images and paths attached to a > font. Yes, the VG side is fine, but we'd, quite frankly, need at least one semi real- world example to make sure it's at all usable and for that we'd need FreeType2 to be able to at least play around with some basic fonts. So not for OpenVG code, but for a demo/test. z -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] OpenVG-1.1 support disabled
Hello, 2009/8/16 Zack Rusin : > [...] > Yes, the code required to actually read/rasterize and render glyphs is > missing. So basically the entire api_text.c would need to be implemented. > What's in there was basically done to pass the VG conformance setters/getters > tests, but once it was decided that for a project we were working only OpenVG > 1.0 will be a requirement I just never went back to finish 1.1. > It wouldn't be too hard to finish this off (assuming addition of FreeType2 as > a > dependency of course) Why do think that FreeType is required? I thought converting from outline curves to vg path data and managing the kerning info is done by the user? VG only has to manage the images and paths attached to a font. regards, Andreas -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] OpenVG-1.1 support disabled
On Sunday 16 August 2009 07:18:13 Andreas Pokorny wrote: > Hi there, > I saw that the openvg state tracker already implements version 1.1 The > code is only deactivated by the OpenVG main API header provided in the > master branch. Is there anything missing in the implementation? Yes, the code required to actually read/rasterize and render glyphs is missing. So basically the entire api_text.c would need to be implemented. What's in there was basically done to pass the VG conformance setters/getters tests, but once it was decided that for a project we were working only OpenVG 1.0 will be a requirement I just never went back to finish 1.1. It wouldn't be too hard to finish this off (assuming addition of FreeType2 as a dependency of course) z -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
