chromium

Arquivos

T

Histórico

gman@google.com da2e11bea2 Add ClientInfo

This allows an app to ask a few things from the client.

1) How many objects the client is tracking. This is useful
for a quick way to check that you're freeing resources.

While the developer could use client.objects.length or
client.packs[ii].objects.length that wouldend up creating 
hundreds of thousands of NPObjects.

2) Check if the software renderer is being used

3) Check the approximate amount of memory used by textures.
Again, they could compute this with 
client.getObjectsByClassName('o3d.Texture') but it seemed
like it might be useful.

I say approximate because I would have to dig down into
the indivdual renderers to get better info since a NPOT
card will use more memory but it didn't seem worth it.

4) check the approximate amount of memory used by hardware
buffers.


Review URL: http://codereview.chromium.org/155276

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20334 0039d316-1c4b-4281-b951-d872f2087c98

2009-07-09 22:59:37 +00:00

cross

Add ClientInfo

2009-07-09 22:59:37 +00:00

mac

This is the O3D source tree's initial commit to the Chromium tree. It

2009-05-27 23:15:42 +00:00

build.scons

This is the O3D source tree's initial commit to the Chromium tree. It

2009-05-27 23:15:42 +00:00

converter.gyp

This adds in the GYP files needed for our GYP build,

2009-06-24 01:46:45 +00:00

README.converter

This is the O3D source tree's initial commit to the Chromium tree. It

2009-05-27 23:15:42 +00:00

README.verifier

This is the O3D source tree's initial commit to the Chromium tree. It

2009-05-27 23:15:42 +00:00

README.verifier

The verifier is a command line utility that will verify shader files.

This utility is used to verify that a shader will compile when given
to O3D to render.  On Windows, it will test-compile the given shader
with both Cg and HLSL compilers.  On Mac and Linux platforms, it will
only compile using Cg (since DirectX isn't available on those
platforms).  This will help users on Windows verify that their shaders
will run when displayed on Mac or Linux platforms, and will help
everyone verify that their shaders compile.

If an output file is specified, it can be used to convert shaders to a
form that can be used directly in O3D.  It strips out unneeded blocks
(like the technique/pass blocks) and replaces them with the O3D
comments which describe the shader entry points.

The command line arguments are as follows:

Usage: o3dVerifier.exe [--no-condition] <infile.fx> [ <outfile.fx> ]

--no-condition: This will prevent conditioning of the shaders into the
                form expected by O3D.  Specifying this causes the
                verifier to ignore any output file specified (since
                that would just be copying the file, and not doing any
                conditioning).  This option is useful only for
                verifying pre-conditioned shaders.

<infile.fx>: This is the input filename of the shader to be validated.

<outfile.fx>: An optional argument giving the name of the desired
              output location of the conditioned shader file in the
              form expected by O3D.  If you don't specify this, then
              no output is created.