|Subject:||[Lynx-dev] which parts of lynx actually handle the html?|
|Date:||Tue, 3 Mar 2020 14:12:06 -0500|
|User-agent:||Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0|
On windows, I call an explorer embedded task to display the html files, which gives me control over the explorer window since it's a child window of my app, and I can easily move from file to file, but I'm not sure how to do this same kind of thing on linux.
I could of course simply call lynx and pas it the url to the local file to display, but this would require the user to quit lynx after each section was done. I'd like instead to be able to incorporate the relevant pieces of lynx directly into the epub reader, so that I have full control over when things get displayed, and when to change what's being shown. Again, this could probably be done with scripting/moderate modifying of the lynx source, but a full blown web browser isn't strictly necessary, since on average, the epub standard doesn't generally go in for most of the existing xhtml extensions, so just having it handle moderately current html tags should be sufficient. I'm just curious if anyone has any ideas/suggestions on what specific parts of lynx would be necessary for this task, since all files will be local, nothing needs to be pulled from remote servers, simple html parsing should suffice, and I only need to be able to control the browser so far as closing and reopeningnew files goes, I'd think I could strip away quite a lot of lynx's current infrastructure, and just use the html engine, with some window controls, but I don't know how problematic a task like this would be, so any help/advice would be appreciated.
|[Prev in Thread]||Current Thread||[Next in Thread]|