KindleExplorer - file manager program (GUI)

[anakod]

Hi all. I developed a small and friendly file manager for Kindle PaperWhite (it should also work on Touch).

The KindleExplorer is integrated with the editor LeafPad, and the terminal Kterm.



Last version can be downloaded from project home: http://kindle-explorer.googlecode.com

To get started, you need to install Unified Application Launcher and unpack the archive to "extensions" folder.

I would be happy to hear your feedback.

[knc1]

Originally Posted by anakod

Hi all. I developed a small and friendly file manager for Kindle PaperWhite (I expect that should work for Touch, but this isn't tested).

The KindleExplorer is integrated with the editor LeafPad, and the terminal Kterm.



To get started, you need to install Unified Application Launcher and unpack the archive to "extensions" folder.

I would be happy to hear your feedback.

An archive or link to the public repository of the sources please.
Also, a statement of what license you are releasing this under.

[anakod]

Thanks for the reply. License is freeware. I'm thinking about opening the code.
In my code I'm using tinydir and two methods from Leafpad (keyboard open & close).

[twobob]

Originally Posted by knc1

An archive or link to the public repository of the sources please.
Also, a statement of what license you are releasing this under.

I dug around inside. appears to use the .glade loader stuff.

source would be nice...

[twobob]

If you chuck out the source I will build this for all devices. thanks

[knc1]

Originally Posted by anakod

Thanks for the reply. License is freeware. I'm thinking about opening the code.
In my code I'm using tinydir and two methods from Leafpad (keyboard open & close).

tinydir uses the MIT license (see link you provided, file: COPYING).
leafpad is GPL-v2, so as long as you are using leafpad code in your sources, yours is GPL-v2 also.

If you write your own replacement for those two parts of leafpad, then you could licensed it under the MIT license.

But you **can not** use GPL-v2 code without providing the source or re-license it as "freeware".

This site has firm guidelines about posting/using copyrighted materials in conflict with their license.

[anakod]

Okay, but I don't know how I could rewrite this. This is very simple

PHP Code:

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard open net.fabiszewski.leafpad:Abc:1", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      }

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard close net.fabiszewski.leafpad", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      } 


It's all under GPL.

[anakod]

If you chuck out the source I will build this for all devices.

This is interesting. What specific devices?

[ixtab]

Originally Posted by anakod

Okay, but I don't know how I could rewrite this. This is very simple

PHP Code:

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard open net.fabiszewski.leafpad:Abc:1", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      }

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard close net.fabiszewski.leafpad", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      } 


It's all under GPL.

Write down the shell commands you need, and possibly modify them. Remember the overall logic required, then delete the original code, and, from memory, write your own which essentially achieves the same result, but without being a verbatim copy (you did remember what you have to do, didn't you?)

Or, ask the original author for permission to re-use the code snippet under a different license.

[twobob]

Originally Posted by anakod

This is interesting. What specific devices?

DX, k2, k3, k4, k5, PW (all revisions....)

Those ones ;D

[eureka]

Originally Posted by anakod

Okay, but I don't know how I could rewrite this. This is very simple

PHP Code:

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard open net.fabiszewski.leafpad:Abc:1", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      }

      switch(fork())
      {
        case 0:
          {
            execlp("/bin/sh", "sh", "-c", "/usr/bin/lipc-set-prop -s com.lab126.keyboard close net.fabiszewski.leafpad", NULL);
          }
        case -1:
          perror("Failed to open keyboard\n");
          exit(1);
      } 


It's all under GPL.

These commands use CLI interafce to /usr/lib/liblipc.so. You can reverse engineer this library and link to it with using appropriate functions directly.

[twobob]

Originally Posted by ixtab

[ Gives Good advice ] ...
Or, ask the original author for permission to re-use the code snippet under a different license.

Yeah. the second one is least resistance.

[twobob]

Originally Posted by eureka

These commands use CLI interafce to /usr/lib/liblipc.so. You can reverse engineer this library and link to it with using appropriate functions directly.

Now, THAT is great info

[anakod]

I found that i needed. I will write this code today or tomorrow.

DX, k2, k3, k4, k5, PW (all revisions....)

Those ones ;D

What about other manufacturers, or is it too much? :-D

[twobob]

Originally Posted by anakod

What about other manufacturers, or is it too much? :-D

err.. such as?

This is KINDLE developers corner

Originally Posted by anakod

I found that i needed. I will write this code today or tomorrow.

hmm... that's a rather device specific bit of code...

I'll wait until I see your source before I get excited then