[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] getShaderInfoLog/getProgramInfoLog format specification
And just like before, you can continue to add more and more features whenever you want without having to wait for 4, 5 or 6 browser teams to find the time to do it for you. You won't need to argue here about which format should be supported (text, JSON? XML?) and whether it it be internationalized or which warnings to include vs errors and which other features you want. If you want a feature add it, if you can't agree fork it.
You could even easily expand that into some kind of uber shader debugger that re-wrote/re-compiled the shaders on the fly as you try to step through them.
I think as a library it's a great idea but I don't see how putting this in the browser or the official spec would be anything but a giant time sink. Time that would be better spent implementing a library or shipping the next couple versions of WebGL