nookBrowser: Auto-sync dual-browse screens (Enhancement)

[GoogleCodeExporter]

This is an enhancement request.

The dual browse capability makes nookBrowser so much more usable.  Thanks 
for adding it so quickly! (I'm nooked from nookboards).  It works 
beautifully!  One enhancement would be to add a user-controlled option to 
automatically sync the E-ink screen to the touch screen when the user 
clicks a link on the touch screen (or on the E-ink too, I suppose--
although I suspect dual browsing has made using the up/down/select link 
method virtually obsolete).

If it is possible to tell when the user has used the touch screen to 
scroll down (or up) past the end of the content currently displayed on the 
E-ink, the e-ink screen could be flipped to the next (or previous) page 
automatically too.  This should probably be a separate setting from the 
one above (if it is even possible--no big deal if not).

Once again, great work on this feature.  Works better than I had hoped!

Original issue reported on code.google.com by jmc...@gmail.com on 5 Feb 2010 at 2:18

[GoogleCodeExporter]

Yeah!!!

Dual screen support is sooooo great!
I agree with jmcode that the circle-control on the right side(i.e., 
left/right/up/down) would be obsolete with the support of dual screen.

But I don't think it a good idea to sync the click for both the E-link screen 
and the 
touch screen. The reason is: When I click a link on the touch screen, I may 
just want 
to quickly check whether the content is really interesting. If I find the 
content 
interesting, I would like to read it on the E-link screen. If I find it not so 
interesting, I would like to check another link and there is no need to show it 
on 
the E-link screen.

Original comment by ttn...@gmail.com on 5 Feb 2010 at 2:48

[GoogleCodeExporter]

That is why I think it should be made a user-configurable option.

Original comment by jmc...@gmail.com on 5 Feb 2010 at 2:52

[GoogleCodeExporter]

We can make this a configurable option. But it won't work 100% of the time. 
java script events, submitting forms, search button clicks etc are handled 
differently by the android webkit and I'm not able to capture those events. So, 
in 
those cases, you will have to click the sync button to make the pages the same. 

regarding pageup/pagedown & scrolling, since the touchscreen and eink are 
refreshing 
at different speeeds, it will be difficult to keep them in sync. It will result 
in 
the eink getting refreshed all the time. So, Let's not do that.

Original comment by hari.swa...@gmail.com on 5 Feb 2010 at 1:41

• Changed state: Accepted

[GoogleCodeExporter]

This is added as a settings option in 0.0.8 ( under Settings-Screen-Both). 
This will work in most cases but not in some cases like forms, searches, 
javasscript 
events, auto refreshing pages etc.

Original comment by hari.swa...@gmail.com on 7 Feb 2010 at 3:58

• Changed state: Fixed