In article <20050910142815.EEF14E4D64(a)adm1-mta.ggfl.myschools.net&gt;, <iharding(a)ladiescollege.sch.gg&gt; wrote: I may be missing something and my recent return from holiday results in a 24 July version being my most up-to-date but try Run Choices:www.NetSurf.Hotlist in a task window, put it in an obey file, or use !OpenDir (www.timil.com/riscos/op.zip) to get at NetSurf's Choices. The hotlist appears to be stored in an HTML file which is editable, export-able, and apparently just made prettier by NetSurf. If other browsers can export HTML it ought to be simple to import data. What I would like to see is a RISC OS user hotlist, not a software specific one at all. Bookmaker is the nearest implementation of this but, afaik, NetSurf doesn't work with it. -- Tim Hill, <URL:http://www.timil.com/>

In article <4da8b70f59tim(a)timil.com&gt;, Tim Hill <tim(a)timil.com&gt; wrote: [Snip] Indeed. The Bookmaker hotlist is (can be) a similar HTML file, but frustratingly it cannot be imported directly for Netsurf to use. It is possible to convert from one to the other by hand, but it is a fiddle. (I've done it, but can't remember how!) I support this request unreservedly. Since Bookmaker is de facto the most developed, most versatile, and (I suspect) widest-used hotlist, ISTM that it might be more efficient to adapt the code in NetSurf to work with Bookmaker rather than the other way round. It needn't affect the interface Netsurf presents to users at all; AFAICS it is a matter of altering the format of the HTML list it reads and writes a little, and possibly making the location/leafname of the hotlist configurable (I forget what I had to do with it). That done, it should relieve the NS developers of any further work in maintaining the hotlist function. However, if Nick Roberts is around, perhaps we should hear what he has to say? -- Gary Locock, Network Manager, Bablake Junior School Coundon Road, Coventry CV1 4AU School Website: http://www.bablakejs.co.uk Private mail: g a r y (at) l o c o c k . c o . u k --- [This E-mail has been scanned for viruses but it is your responsibility to maintain up to date anti virus software on the device that you are currently using to read this email. ]

Gary Locock <gary(a)locock.co.uk&gt; wrote: From memory, you should just need to remove the '</li>' elements. This is not something that NetSurf actually needs to add, and it comes from us using libxml to write the file. I could add some code to stop it happening, however... ...the real problem is that Bookmaker doesn't preserve the metadata that NetSurf has in the Hotlist files. Making the Hotlist filename configurable is highly trivial, and if Bookmaker gets updated accordingly I'll get it done. Is the source to Bookmaker publicly available? Extending the parser in the necessary manner really should be very easy, and I'll happily do this if Nick doesn't have the time/motivation. R.

In message <4db1b16e79gary(a)locock.co.uk&gt; Gary Locock <gary(a)locock.co.uk&gt; wrote: BookMaker uses two methods to interface with browser clients: 1) ANT Hotlist protocol. This is, from BookMaker's pov, far and away the simplest. However, there are two problems with this. Firstly, the browser needs to support it, which NetSurf doesn't (ATM); and secondly, the protocol doesn't support any of the metadata that NetSurf stores with the URL. 2) A sneaky module that intercepts mouse clicks on the browser window (i.e. the "Add to hotlist" and "Show hotlist" icons) and redirects them to BookMaker. Also two problems: the same metadata issue, and (more importantly) ever since I modified the code to the 32-bit clean it hasn't (quite) worked 8-(. For some reason I have not, as yet, managed to track down, it doesn't always rebuild the required wimp filter when a new browser client starts. However, as this is only really necessary for Browse and ArcWeb, tracking the problem down has not been a high priority. The ideal solution, as I see it, is a new hotlist protocol (based on the ANT one, as that is still basically sound) that supports the NetSurf metadata (or, preferably, a generic set of metadata, as that would in principle mean that Firefox could use it). -- Nick Roberts tigger @ orpheusinternet.co.uk We are all atheists about most of the gods that humanity has ever believed in. Some of us just go one god further.