| 
			
			 | 
		#1 | 
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 1 
				Karma: 10 
				Join Date: May 2012 
				
				
				
				Device: none 
				
				
				 | 
	
	
	
		
		
			
			 
				
				PageList parsing using Javascript.
			 
			
			
			I understand this is not specifically a development forum, but I have a question regarding PageList parsing in an iOS environment. (I only see Development area for Kindle/Nook). 
		
	
		
		
		
		
		
		
		
		
		
		
	
	PageList and supporting targets are fairly straightforward. A list of anchors referring to their respective file (src), and a playOrder for well, ordering. My question is how do eReaders actually detect when anchors are in view? For example, a document at 768px wide by 10,000px height may have 20 PageTargets (pg i, pg ii, pg 1, pg 2, pg 3 ... so on). What mechanism are ePub rendering engines on the web, desktop, and specifically iOS using to detect the closest anchor relative to a users position (XY coordinates)? There seems to be nothing in Javascript or Objective-C which does this. Voodoo functionality.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
![]()  | 
            
        
    
            
  | 
    
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| Changing Format Without Parsing | Sidetrack | Conversion | 10 | 04-01-2011 01:47 AM | 
| NCX-pageList: What should it do? | hpstricker | ePub | 2 | 01-25-2011 06:35 AM | 
| iPad Which difference does it make whether I use NCX-pageList or not? | hpstricker | Apple Devices | 2 | 01-24-2011 07:59 PM | 
| Parsing Titles | cgraving | Calibre | 3 | 01-17-2011 03:52 AM | 
| Error parsing attribute name? | seagull | Calibre | 1 | 01-01-2010 12:30 PM |