![]() |
Parser module for MathML and TeX maths |
Introduction Screenshots Mailing Lists and IRC Alternative Browsers Special Thanks
FAQ
Download binaries Platforms Compiling Mnemonic Other useful software
Core Message modules Library modules Object modules Coding Guidelines Browse Source Using CVS
Website questions to: |
(The text below is for images but the same thing is true for other weird tags like maths. It's just here so I don't forget about it). The image parse OIL listens to the network/content and network/data messages. It turns these into internal structures representing the image. There has to be only one parser oil for each image type, but we could also put all the converter logic in a base library and have one big parser oil that just handles the messaging stuff. Image render oils are gui dependent. They can call msg_fetch_url for images, and then listen to the announcement of the internal data structure with the actual data. After that, they can announce the possibility of creating a gui widget and fill that with the data. The render oils can be made to listen both to base image structures they requested themselves and to all other ones that are announced. In the first case, the render oil makes a widget that does not have scrollbars, in the second case it makes a widget that does (for pure image viewing). Render oils will also have to listen to dom_create_events (or a modified version thereof which can announce that a subtree was passed on from another handler) and initiate loads, of course.
|