Re: netsurf-dev Digest, Vol 98, Issue 1
Hello All, Testing some sample html on Netsurf browser in ubuntu system. we are checking XML file .In XML Java Script using DOMParser() function to get the data from xml file. BUT in Netsurf browser this function is not working. can anyone help me ? Thanks Regards Navdeep N. On Tue, Jul 1, 2014 at 4:30 PM, netsurf-dev-requ...@netsurf-browser.org wrote: Send netsurf-dev mailing list submissions to netsurf-dev@netsurf-browser.org To subscribe or unsubscribe via the World Wide Web, visit http://vlists.pepperfish.net/cgi-bin/mailman/listinfo/netsurf-dev-netsurf-browser.org or, via email, send a message with subject or body 'help' to netsurf-dev-requ...@netsurf-browser.org You can reach the person managing the list at netsurf-dev-ow...@netsurf-browser.org When replying, please edit your Subject line so it is more specific than Re: Contents of netsurf-dev digest... Today's Topics: 1. Object fetchers moved to scheduled operation (Vincent Sanders) -- Message: 1 Date: Tue, 1 Jul 2014 09:25:38 +0100 From: Vincent Sanders vi...@netsurf-browser.org Subject: Object fetchers moved to scheduled operation To: netsurf-dev@netsurf-browser.org Message-ID: 20140701082537.gx27...@kyllikki.org Content-Type: text/plain; charset=us-ascii As a continuation of the work done by Daniel to adjust the llcache behaviour to use scheduler for user notification I have now changed the fetcher system to also be run from the scheduler. The fetcher API has been simplified to remove the need for polling from the main loop which gets us very close to netsurf_poll() becoming obsolete. The API has also been extended with fetcher_fdset() which allows the fd sets of all active fetchers to be obtained for frontends that wish to wait on fd activity instead of polling unnecessarily. Please can all frontend maintainers check I have not made a glaring error on their platform as this is pretty invasive for such a small cleanup. Especially ChrisY needs to check the amiga frontend as that used to rely on a config to schedule curl directly which is no longer present. This change should improve the overall code cleanliness and gets us much closer to being able to have frontends run their own dispatch loop. -- Regards Vincent http://www.kyllikki.org/ End of netsurf-dev Digest, Vol 98, Issue 1 **
Re: netsurf-dev Digest, Vol 98, Issue 1
On Tue, Jul 01, 2014 at 17:19:09 +0530, Navdeep Nayar wrote: we are checking XML file .In XML Java Script using DOMParser() function to get the data from xml file. BUT in Netsurf browser this function is not working. can anyone help me ? NetSurf's JavaScript integration is very incomplete as of now. I'd be surprised if much beyond the shonky JS some people use to populate dropdowns in script tags works. Sorry. Also, please do not use digest subscription if you ever intend to post to the list, it's very bad form. If if you *must* then please don't reply to, and then quote the entire of the digest when you post. D. -- Daniel Silverstone http://www.netsurf-browser.org/ PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69
Moving reformat to scheduled operation
The final remaining operation performed within the frontends dispatch loop is that of pending reformats. The reformat call differs from the redraw in that it is used when a browser windows scale or extents changes. The current operation is to set the browser_reformat_pending global to signal one or more browser_windows required updating and then each browser window has its own flag which must be checked. This was ineficient as the frontends had to check every browser window even if only one required reformatting and broke our data hiding model for browser_window meaning we had to expose browser_window internals all over the codebase. I have a branch vince/reformatpending which changes this to being a scheduled callback and reduces the frontend involvment to providing a single callback entry in the window operation table. This has revealed some dreadful code in many areas including several frontends that never do anything with the flag at all! Because of this this change is much more invasive and alters behaviour in frontends I could not test. I would appreciate frontend maintainers (I have tested/fixed gtk/framebuffer/monkey and riscos) trying this branch and giving feedback before I commit it. Especialy Chris Young on amiga where my changes are untested and I fear I may have broken the frontend altogether (sorry Chris) Hopefully this is the end of the road with these type of changes, my next is to remove the poll entry and let frontends run the main loop themselves. -- Regards Vincent http://www.kyllikki.org/
Re: Object fetchers moved to scheduled operation
On 01/07/2014 10:25, Vincent Sanders wrote: As a continuation of the work done by Daniel to adjust the llcache behaviour to use scheduler for user notification I have now changed the fetcher system to also be run from the scheduler. The fetcher API has been simplified to remove the need for polling from the main loop which gets us very close to netsurf_poll() becoming obsolete. The API has also been extended with fetcher_fdset() which allows the fd sets of all active fetchers to be obtained for frontends that wish to wait on fd activity instead of polling unnecessarily. Please can all frontend maintainers check I have not made a glaring error on their platform as this is pretty invasive for such a small cleanup. Especially ChrisY needs to check the amiga frontend as that used to rely on a config to schedule curl directly which is no longer present. This change should improve the overall code cleanliness and gets us much closer to being able to have frontends run their own dispatch loop. Seems to work on Haiku. Btw, straight from select(2) manpage: nfds is the highest-numbered file descriptor in any of the three sets, plus 1. So the @todo is solved :D François.
