I see a good niche for Jive: Rich applications with very custom UI that need the exact same rendering across browsers. I've had a case recently that cross browser rendering of some custom HTML components I made gave me some headache, so maybe Jive could be used, with the added benefit of allowing it to be compiled to native (desktop/mobile).
I'm wondering about retina displays, does it support automatic adaptation to hidpi screens for typefaces, vector components and also a mechanism to auto-switch between a retina/regular dpi image for when a raster is needed? If not, how hard would it be to implement it, and is it planned?
Hi Nickolay!
I see a good niche for Jive: Rich applications with very custom UI that need the exact same rendering across browsers. I've had a case recently that cross browser rendering of some custom HTML components I made gave me some headache, so maybe Jive could be used, with the added benefit of allowing it to be compiled to native (desktop/mobile).
I'm wondering about retina displays, does it support automatic adaptation to hidpi screens for typefaces, vector components and also a mechanism to auto-switch between a retina/regular dpi image for when a raster is needed? If not, how hard would it be to implement it, and is it planned?
Cheers!