They already have the experience of successfully getting Phaser and cocos creators to migrate to it, and it should be a lot easier for them to work on C3. The only way I can think of is if you can contact their staff on github and negotiate an adapter to help C3 export on it. I seem to have seen some people migrate to it by embedded webviews to run some web games, but there are some restrictions on running efficiency.
But these things are too complicated for me to discuss. On the other hand, they may need to build their own brands and monopolize this part of the market. Also because of compatibility issues, in the early years, most users were using very old low-end devices, which may not support some new features. Restrictions allow only specific functions to run. On the one hand, security issues may be considered, and it must be made safe and controllable. I 100% agree, but unfortunately, the reason why they design a browser instead of using modern browsers directly may involve corporate strategy. I don't know why they wouldn't use a real browser engine - it would be much less work both for them and for us, and modern browser engines have exceptional features and performance. If they supported real browser-based webviews, it would be much more likely we could support it. WeChat application/mini program general: WeChat official account setup WeChat mini program creation Makring & sale fetaures. So I'm afraid so long as they use their own custom not-a-real-browser engine, I would be extremely reluctant to work on this if they supported real browser-based webviews, it would be much more likely we could support it. Meanwhile if they just used a webview and used a real browser engine, we could achieve near-100% compatibility with very little work. So it turns out being a huge time sink with product-wide disadvantages and then everyone still complains about it being broken anyway.
#Wechat mini program creator help code
It takes an enormous amount of development work and still never ends up working 100% correctly, with endless bugs that never happen in real browsers, and endless incompatibilities with how real browsers work, causing us to have to write complicated code all through the engine to deal with the various problems, which in turn risk breaking other platforms and making maintenance more difficult for the codebase as a whole. Past painful experience has taught me that trying to support non-standard browser engines is difficult to justify. As far as I can tell from a quick glance at the docs, they don't use a real browser engine - it doesn't use HTML and CSS, instead using something they call WXML and WXSS.
0 kommentar(er)
