Im developing a new tool called palmdeMON, to help developers understand
the internals of their compiled products. It will disassemble a PRC, along
with all other resources, such as strings, data, bitmaps, alerts etc
Still a beta version, but im interested in feedback.
pdemon is available from http://carpathia.cjb.net
Regards
Carpathia
(Incidentally, anyone know why my posts always appear as 1899. My system
clock is correct!?)
"Ben Combee" <[EMAIL PROTECTED]> wrote in <42957@palm-dev-forum>:
>
>"Chantal C. Leger" <[EMAIL PROTECTED]> wrote in message
>news:42954@palm-dev-forum...
>>
>> Is anyone aware of a utility that would let me get the source code
>> from an application I've downloaded. I really like the way they
>> produce the visual side of the application but I have know idea how
>> they did this, so if I can look at some of the code it would help what
>> I. m doing.
>
>In general, it isn't possible to decompile an application to anything
>more revealing that assembly code. However, on the Palm, there are some
>tools that can help:
>
>1) Insider and Onboard RsrcEdit both will let you look at the
>applications resources and disassemble the code as 68K assembly. I'm
>not sure if either of them understands Macsbug debug symbols which some
>applications leave embedded inside.
>
>2) Running the code on the PalmOS emulator with logging enabled can give
>you a feel for what system calls they use and the event flow. However,
>you have to be careful in picking what you target, as the log is limited
>to the last 1MB of data produced.
>
>3) If the application uses a PQA (web clipping application), there are
>several PQA-to-HTML converters available.
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
