Quote:
Originally Posted by ixtab
NO WAY!
Seriously: patches affect the CORE "Operating System" of the Kindle, so they should be well-tested, stable, and without side effects. I really don't want script kiddies releasing some random code which might or might not work (and that is the best case I can imagine).
On a side note, if you're using Eclipse, you don't even have to compile the patches after changing the source code, because Eclipse does it automatically. All you have to do is to scp one file to the device...
That said: Feel free to create a Patch which can load JS/Jython/JRuby or even COBOL/FORTRAN/PROLOG patch definitions
|
Hm, unexpected reasoning...
But I think I can understand where it's coming from. Yes, random text files as instructions for patching Java part of UI is bad.
However, BeanShell syntax (for script file) has minimal differencies with original Java syntax. So the only difference between script and .class (and the only barrier for script kiddie) will be in invoking javac. It's pretty easy in fact. (But become tedious).
And it's a bit harder to audit random .class files than random text files with scripts.
Anyway, I'm not arguing because of preaching for embedding script engine. Just advocating the devil
Quote:
Originally Posted by knc1
All *nix (and *nix related) systems have that: it is called a: "package management system".
Often not included (internally) in an embedded system build, but there is 3Gbyte of r/w storage on these things, so plenty of room to put it back in.
|
Question isn't in form of distribution channel (packages or archives or anything). Question is (or was) in form of distributed product.