View Single Post
Old 10-27-2009, 09:38 PM   #6
DairyKnight
Connoisseur
DairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with othersDairyKnight plays well with others
 
Posts: 63
Karma: 2600
Join Date: Oct 2008
Device: PRS-505
Quote:
Originally Posted by dr_g100k View Post
Hi,
what about /opt/amazon/ebook/booklet folder? Did Someone Already reverse engineer the firmware?
So far as I know, to implement a Booklet, you have to extend your class from
the following interfaces:

com.amazon.ebook.framework.a - Booklet interface
com.amazon.ebook.framework.gui.event.a = java.awt.event.KeyListener
com.amazon.ebook.framework.kos.event.b = Kindle OS Events listener

For the booklet interface, you have to implement the following methods:

public abstract interface a
{
public abstract String C(); // Returns the booklet name as String

public abstract void c(); // Init booklet, set up keypad/mimetype hooks?

public abstract void B(); // Load booklet ?
// Use com.amazon.ebook.framework.gui.d.d.j().a(String booklet_title); to set booklet titles

public abstract void b(); // Some method gets called in the init chain. deals with filenames

public abstract void A();

/** @deprecated */
public abstract void a(y paramy, Graphics paramGraphics); // Painting surface - y is some Component similar to JFrame/Frame
/*



It's just toooo hard to peek through the obfuscated codes. That's why I'd suggest to only decode the JNI part and 'reinvent the wheels' with Java.
DairyKnight is offline   Reply With Quote