Quote:
Originally Posted by twobob
I'm not 100% sure that Kindlets are the best target anyways.
(Okay I am 99.999% sure they are not the right thing to use really)
If you imagine that Kindlets will be some fully featured way of getting stuff "to screen" I can assure you (IMHO) they are a locked-down bumache.
(see my many threads on attempting to make kindlets do something "amazing") they never failed to disappoint. It MAY be that they would be a great testbed for super solid browsing. My gut says NO.
|
Hehe... it depends. On the K5 and up, Kindlets actually are quite a nice thing.* They're easy to write, they provide a consistent UI, and they allow you to do pretty much anything (i.e., they can interact with both the Java-based, and the system part of the device) - that is, if you know what to do, and if you escape the "locked-down bumache" - but that part is trivial if you use the Kindlet jailbreak. This is why I personally prefer to write Kindlets, rather than anything else. (yes, they're mostly limited to a specific FW version, but that's also because they do very specific things which are closely coupled to the FW - especially now that Amazon re-obfuscates everything with every new release
- if you stick with "pure userland" and don't try to muck with the system internals, that's much more relaxed).
(*) Not so on the K3, because that doesn't support standard Swing UI components. You'll have to reinvent the wheel for many UI things, and even then, it'll still look ugly. I'm still not sure about the K4, but my guess is that it's similar to the K3, i.e., "not good".