nds good. My own choice for general purpose browsing is Chrome with chromevox loaded -- give that a shot. You'll need to: 1. Install ChromeVox and the Lois voice from the Chrome Web Store; 2. Ensure that your Chrome has nacl support. Eventually I'd like to use Chrome's remote debugging API to connect emacs to Chrome --- and do the following: Use ChromeVox to work with the general purpose Web. 2. Use the remote port connection between Emacs and Chrome to get Web content into Emacs so you can further manipulate it as desired. All of this is a fair bit of work. >>>>> "Tim" == Tim Cross <theophilusx@xxxxxxxxxxx> writes: Tim> I could be way off the mark, but my thoughts were that Tim> the w3 rendering code could be a worthwhile reference Tim> wrt rendering, but most of it would need to be Tim> updated/modified - same with the css module. I would Tim> like to see something with very separate and independent Tim> modules that each have a well defined interface that are Tim> all hooked up together to provide a usable browser AND Tim> provide a useful set of utilities that could be used for Tim> other processin and provide an interesting tool set for Tim> experimentation and personal customization. Tim> Tim> It is probably this last part, experimentation and Tim> customization for specific tasks I find most appealing Tim> about w3. For general browsing, I am finding it Tim> increasingly necessary to use something like firefox or Tim> chromium. However, as the epub stuff you did shows, Tim> there is still a lot of potential for a reliable text Tim> browser with a very close integration with emacs that Tim> will allow us to manipulate components with custom Tim> elisp. Tim> Tim> Tim Tim> Tim> On 11 May 2012 13:23, T. V. Raman Tim> <tv.raman.tv@xxxxxxxxxxx> wrote: >> shr doesn't use any of the W3 rendering code. >> >> Unfortunately the parse structure that the W3 parser >> builds is not exactly the same shape as that returned by >> libxml -- so you'd have to do a bit of work before the W3 >> renderer can eat the libxml parse tree. But it shouldn't >> be a huge amount of work. >> >>>>>>> "Tim" == Tim Cross <theophilusx@xxxxxxxxxxx> writes: >> Tim> Now that is very interesting. Will certainly be >> checking Tim> out shr - this is exactly along the same >> lines as I was Tim> thinking wrt moving w3 forward and >> helping to ensure it Tim> doesn't end up dying of bit >> rot. Tim> Tim> Since emacs added the interface to >> libxml, I've been Tim> wondering about how much work >> this would take, so I'm Tim> quite excited to find that >> thiswork has already started. Tim> Tim> Tim Tim> >> Tim> On 11 May 2012 03:47, T.V. Raman >> <tv.raman.tv@xxxxxxxxxxx> Tim> wrote: >> From an >> Emacspeak perspective, W3 will always trump W3M >> in >> terms of features --- w3m in emacs is nice, but the >> >> integration leaves a lot to be desired -- in that emacs/w3 >> >> only gets its hands on the content after w3m itself has >> >> done the bulk of the rendering. >> >> In the best >> of all worlds, the parsing and dom >> construction >> would happen in the native layer --- and the >> >> rendering happen in the lisp layer. Module shr is a >> >> beginning to that end --- in that it uses libxml to do the >> >> parsing -- >> >> On 5/9/12, Robert D. Crawford >> <robdcraw@xxxxxxxxxxx> wrote: >>> "Tim Cross" >> <tcross@xxxxxxxxxxx> writes: >>> >>>> The really nice >> thing is that since machines have gotten >>>> so much >> faster in the past few years, the slower >>>> rendering >> time of w3 compared to w3m is pretty much >>>> >> unnoticeable except on really large html files. >>> >> >>> I've not used w3m in such a long time. I've preferred >> w3 >>> since I first used it. Glad to hear I'm not >> really >>> missing out on speed. >>> >>>> thanks >> again, you have made my day! >>> >>> You are quite >> welcome. Glad to have been of assistance. >>> >>> >> rdc >>> -- >>> Robert D. Crawford >>> >> robdcraw@xxxxxxxxxxx >>> >>> >> ----------------------------------------------------------------------------- >> >>> To unsubscribe from the emacspeak list or change your >> >>> address on the emacspeak list send mail to >>> >> "emacspeak-request@xxxxxxxxxxx" with a subject of >>> >> "unsubscribe" or "help". >>> >>> >> >> >> ----------------------------------------------------------------------------- >> >> To unsubscribe from the emacspeak list or change your >> >> address on the emacspeak list send mail to >> >> "emacspeak-request@xxxxxxxxxxx" with a subject of >> >> "unsubscribe" or "help". >> Tim> Tim> Tim> >> Tim> -- Tim Cross >> >> -- >> Best Regards, --raman >> >> -- >> Best Regards, --raman Tim> Tim> Tim> Tim> -- Tim Cross -- Best Regards, --raman ----------------------------------------------------------------------------- To unsubscribe from the emacspeak list or change your address on the emacspeak list send mail to "emacspeak-request@xxxxxxxxxxx" with a subject of "unsubscribe" or "help".
If you have questions about this archive or had problems using it, please send mail to:
priestdo@xxxxxxxxxxx No Soliciting!Emacspeak List Archive | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | 1998 | Pre 1998