Guide: How to write Kindlets

[knc1]

Originally Posted by digory

EDIT: Added dashes--- because this editor does not preserve the formatting.

In your profile here, select the "advanced editor" rather than the "default editor".
Then use the appropriate type(s) of block quotes.
Translation: The problem is on your side of the keyboard.

[geekmaster]

Originally Posted by digory

EDIT: Added dashes--- because this editor does not preserve the formatting.

To preserve formatting you can wrap text in CODE tags, like this:

Here is some text.
    Here is some indented text.
        This is more indented.
    And out a level.

Or instead of preserving formatting, you can create formatting with INDENT tags, like this:

Text

Indented text.

More indent.

Less indent.

Just quote this message in a new message then view the tags in your edit box.

These tags and more have toolbar icons for them, when you click the "Advanced Edit" button.

Beware that the indent tag adds extra blank lines that you may need to mess with to get it the way you want. After the "end indent" tag, you may need to add a couple of blank lines.

[digory]

OK, thanks. But the editor is the minor problem.

The KTextArea isn't documented in Amazon's dev kit reference, so I replaced the KTextArea with a Button. Now it compiles, cool! However, it still doesn't work. The following is a bash script that generates my azw2:

#!/bin/bash

PROJECTNAME=HelloWorld
CLASSPATH=../lib/Kindlet-2.1.jar
export CLASSPATH

echo "Making $PROJECTNAME..."

if [ -f developer.keystore ]; then
  echo "developer.keystore exists!"
else
  echo "Generating developer.keystore..."
  keytool -genkeypair -keystore developer.keystore -storepass password -keypass password -alias dk$PROJECTNAME -dname "CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown" -validity 5300
  keytool -genkeypair -keystore developer.keystore -storepass password -keypass password -alias di$PROJECTNAME -dname "CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown" -validity 5300
  keytool -genkeypair -keystore developer.keystore -storepass password -keypass password -alias dn$PROJECTNAME -dname "CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown" -validity 5300
fi

echo "Compiling..."
javac *.java

echo "Creating jar file..."
/bin/rm $PROJECTNAME.jar >&/dev/null
/bin/rm $PROJECTNAME.azw2 >&/dev/null
jar cvmf $PROJECTNAME.manifest $PROJECTNAME.jar *.java

echo "Creating signed azw2 file..."

jarsigner -keystore developer.keystore -storepass password $PROJECTNAME.jar dk$PROJECTNAME
jarsigner -keystore developer.keystore -storepass password $PROJECTNAME.jar di$PROJECTNAME
jarsigner -keystore developer.keystore -storepass password $PROJECTNAME.jar dn$PROJECTNAME

mv $PROJECTNAME.jar $PROJECTNAME.azw2

echo "Done."

The PROJECTNAME (the azw2's name) can be any arbitrary name, or does it need to have the same name as the public class (which is Main)? Anyway, when I move this azw2 to the documents folder, it doesn't show up in the Kindle. There is still something wrong here...

[digory]

There was a mistake in my bash script: I added *.java to the jar instead of *.class. Stupid me. Another, minor mistake was that I named my key aliases as xy$PROJECTNAME. I should've used xy$USER, because I obviously need only one developer key triplet, to be used for all my projects. It still wouldn't work, though, and I learnt that the manifest file in the original post was wrong. Here's one that actually works:

Manifest-Version: 1.0
Main-Class: com.digory.helloworld.Main
Implementation-Title: Hello World!
Implementation-Version: 1.0
Implementation-Vendor: digory
Extension-List: SDK
SDK-Extension-Name: com.amazon.kindle.kindlet
SDK-Specification-Version: 2.1
Toolbar-Mode: persistent
Font-Size-Mode: point

The lines Main-Class and those concerning the SDK seem to be important in particular, but are not included in the manifest shown on the first post in this thread. Somebody please update that post!

[twobob]

Originally Posted by digory

There was a mistake in my bash script: I added *.java to the jar instead of *.class. Stupid me. Another, minor mistake was that I named my key aliases as xy$PROJECTNAME. I should've used xy$USER, because I obviously need only one developer key triplet, to be used for all my projects. It still wouldn't work, though, and I learnt that the manifest file in the original post was wrong. Here's one that actually works:

Manifest-Version: 1.0
Main-Class: com.digory.helloworld.Main
Implementation-Title: Hello World!
Implementation-Version: 1.0
Implementation-Vendor: digory
Extension-List: SDK
SDK-Extension-Name: com.amazon.kindle.kindlet
SDK-Specification-Version: 2.1
Toolbar-Mode: persistent
Font-Size-Mode: point

The lines Main-Class and those concerning the SDK seem to be important in particular, but are not included in the manifest shown on the first post in this thread. Somebody please update that post!

Did you update the post with the wrong code in it then?

I still see *.java etc?

[twobob]

okay. here's one that worked for me on 3. (3.3, SDK 1.2, Java 1.4.2_19)

(remember to derive from com.amazon.kindle.kindlet.AbstractKindlet as shown in this project...)

Included the sign.sh that you call like ./sign.sh filename.jar

Included the developer.keystore from ixtabs font project.

you run it against the EXPORTED jar

dump the final azw2 in /mnt/us/documents

should be golden.

#!/bin/sh
dbus-send --system /default com.lab126.powerd.resuming int32:1

called update.sh is an optional file you *could* make, to assist in quick index updating (that's what I run).

hope this helps someone like me who was struggling with the info that is mainly for 4 and 5's these days.

[twobob]

Lifecycle

http://docs.oracle.com/javase/tutori...lifeCycle.html helpful reading.

retroweaver

http://www.openmamba.org/showfile.ht...weaver125.spec

http://retroweaver.sourceforge.net/g...aver-guide.pdf

and more generally about the java: Bit of a "cvm" overview

Spoiler: