Lobo Cobra HtmlPanel 在 JavaScript 操作后不更新 GUI
我开始在 Swing 中实现 HTML 浏览器。 我想使用 Lobo Cobra 工具包，因为该工具包包含 CSS 和 JavaScript 的渲染器和解析器。 这些页面看起来非常漂亮并且易于使用（一个类实现来显示 html 页面）。
我想在 swing 中显示 HTML 页面，它可以显示 javascript 生成和修改的对象，例如闪烁的圆圈。 据我所知，cobra 工具包可以显示静态 JavaScript 命令，例如“document.write”或 closwWindow() 实现，但不能从 JavaScript 更新 GUI。
有人以前使用过 Lobo Cobra Toolkit，并且可以给我一些示例代码或提示来显示带有动画 JavaScript 对象的 HTML 页面吗？
I started implementing a HTML browser in Swing. I want to use the Lobo Cobra toolkit because this toolkit inclused a renderer and parser for CSS and JavaScript. The pages are looking very nice and it is easy to use (one class implementation to show a html page).
I want to show HTML pages in swing which can show javascript generated and modified objects, like a flashing circle.
As far as i know, the cobra toolkit can show static javascript commands like 'document.write' or closwWindow() implementations, but not updating the GUI from a JavaScript.
Did someone work with Lobo Cobra Toolkit before and can give me some sample code or tips for showing HTML pages with animated JavaScript objects inside?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我的印象是，只要您设置了通知，您的代码就会被调用来对 DOM 进行所有更改，无论是在页面加载时完成还是在页面加载后通过 Javascript 动态完成。
我最初会设置一个实现 DocumentNotificationListener 接口的对象 (X)，并为每个调用的方法记录一条消息。 然后使用 Y.addDocumentNotificationListener(X) [其中 Y 是 HTMLDocumentImpl 对象] 将其设置为侦听器，并加载页面以查看实际调用了哪些方法。
最坏的情况是，您必须在每次方法调用时重新呈现 HTML 页面，但您应该能够优化其中的大多数方法。 例如，更改节点（DOM 对象）的颜色（这会导致调用 X.lookInvalidated(...)）不需要重新渲染整个页面，因为节点大小不会更改。
I'm under the impression that, as long as you set yourself up for notifications, your code will be called for all changes to the DOM whether done on page load or dynamically by Javascript following the page load.
I would initially set up an object (X) implementing the DocumentNotificationListener interface and log a message for every method called. Then set that up as a listener with Y.addDocumentNotificationListener(X) [where Y is your HTMLDocumentImpl object] and load up your page to see which methods are actually called.
Worst case is that you'll have to re-render your HTML page on every method call, but you should be able to optimize most of them. For example, changing colors of a node (DOM object), which results in the X.lookInvalidated(...) being called, wouldn't require re-rendering of the whole page as the node size doesn't change.