search

nagyistoce / emerson-reader

Automatically exported from code.google.com/p/emerson-reader
0 stars 0 forks source link

Feature: Mozilla #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Use the Mozilla Browser on all platforms, and access through the XPCOM API.
This will allow more finely grained event handling, storing selections, etc.

Make sure Firefox plugins are supported (think Ruby):
http://www.eclipse.org/swt/faq.php#mozillaplugins

Original issue reported on code.google.com by markus.g...@gmail.com on 18 Feb 2009 at 9:21

GoogleCodeExporter commented 9 years ago 
could you please explain this enhancement-"mozilla" it will be more helpful

Original comment by ritu.it...@gmail.com on 14 Mar 2009 at 4:50

GoogleCodeExporter commented 9 years ago 
There are several potential features that could be added only if there was a 
more
elaborate browser widget API. The current SWT API (even while enhanced 
considerably
in SWT 3.5) is quite limited in terms of the needs of user interaction with the
browser surface. 

With a uniform use of Mozilla through XPCOM and XULRunner, one can implement 
things
such as:
 - catching of click events on the browser view surface, and relating that to a
reading position 
 - allowing users to select a portion of text, and storing that as a retrievable note
(think: felt-pen notetaking)
 - allow user text annotations of the document (already doable when reading DAISY,
but not EPUB)
 - Using the Mozilla DOM when doing (Lucene) search-retrieval, and using DOM CSS
manipulation for marking search hits in the view
 - Make use of Firefox plugins to support specific static features (rendering of Ruby
is a classic example)
 - Allow user-side or author-side alternatieve CSS stylesheets to be activated
dynamically
 - etc...

Some of these things could be done using the java-script support in SWT 3.5, 
but not all.

Original comment by markus.g...@gmail.com on 15 Mar 2009 at 10:08

GoogleCodeExporter commented 9 years ago 
Does this imply completely replacing the SWT ui by the one created through 
browser
widget API or is there any way out to perform this enhancement over the current
swt/jface ui? Please provide ur suggestion.

Original comment by ritu.it...@gmail.com on 24 Mar 2009 at 4:55

GoogleCodeExporter commented 9 years ago 
The idea would be to use XULRunner and org.eclipse.atf.mozilla.swt.browser, see
http://dev.eclipse.org/newslists/news.eclipse.webtools.atf/msg00553.html
and
http://wiki.eclipse.org/ATF/Mozilla
and
http://www.eclipse.org/atf/downloads/base_files/manualXulrunner_section.php

It may also be that the extended javascript support added in SWT 3.5 can cover 
at
least the most important parts of the needed browser interaction improvments, 
this
needs to be investigated.

Original comment by markus.g...@gmail.com on 31 Mar 2009 at 4:25

GoogleCodeExporter commented 9 years ago 
Remeber that on a Mac Mozilla is not yet accessible with the screen reader.

Original comment by gkearney@gmail.com on 24 Apr 2009 at 3:21

GoogleCodeExporter commented 9 years ago 
Right. And there may be Windows access devices that work better with IE; same
principle as comment 5. 

So - if this is added, there needs to be a user option to toggle "Mozilla mode" 
on or
off, where the default mode is to use the system default browser.

Original comment by markus.g...@gmail.com on 29 May 2009 at 1:41