Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
https://www.panoramicweb.net/demo/blendt…scene20-11.html only default blend working the others not working
This post has been edited 1 times, last edit by "ChukA" (Jun 16th 2022, 3:39pm)
Last decade Web has changed significantly: flash and IE are dead, WebGL 2.0 is broadly supported by all browsers, WebGPU & WebXR are on the way, JavaScript evolved a lot, WebAssembly has arrived, etc.
@klaus.krpano how do you see the future of Krpano ?
Thanks for your hard work. I really appreciated your support.Hi,
Last decade Web has changed significantly: flash and IE are dead, WebGL 2.0 is broadly supported by all browsers, WebGPU & WebXR are on the way, JavaScript evolved a lot, WebAssembly has arrived, etc.
I'm following actively all these development of course!![]()
For krpano and also just for personal interest.
Some notes:
- WebGL 2.0 is nice and makes implementing some thing easier - and in krpano 1.21 I'm using it optionally for some shaders (with fallbacks for WebGL 1.0), but at the moment I think it's still too early for 'WebGL 2.0-only'. This would unnecessarily exclude too many devices and browsers. Depending on the needs the same that can be done in WebGL 2.0 can be also done also with WebGL 1.0, even when that requires more internal work.
That means there is currently no advantage or disadvantage of using WebGL 2 in krpano. But if someone whats to use it, in krpano 1.21 there is option to enable the WebGL 2.0 API.
- WebXR is already supported, but not all 'special' features from it, more to come here.
- 'JavaScript evolved a lot' - yes, but many things are just syntactic sugar, and nicer looking code is no reason to through away compatibility.
- WebAssembly is super interesting, but I don't see a need for it inside krpano. There is no heavy processing in krpano that could profit from a WebAssembly implementation.
- WebGPU - even more interesting, with it implementing certain things could be much easier and faster. But first here a fixed standard and broader support is required.
Beside these notes - note that these are all 'developer-features', not really relevant for the end-user. So far the outcome should be more important than the tools that were used to build it.
@klaus.krpano how do you see the future of Krpano ?
More capabilities/features and especially easier usage/tooling.
With the next krpano 1.21 version, which is mainly an update for viewer-side, I'm preparing parallel also a lot for krpano 2.0, which will be mainly a tools-side update.
Best regards,
Klaus