Java ME/Mobile — OZONE Asylum, home of the Mad Scientists

OZONE

This page's ID: 29409

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	Okay, I haven't adressed the specific issues in two years at least, but while staying general to avoid too specific and false advice : 1) Certainly yes, probably by treating it like an object you serialize - VM instances can also be started with directives which makes life a lot easier in some cases (heap size..) 2) Should be fairly easy to log the stacktrace somewhere 3) Certainly yes again, when catching an error in Java you can explicitely redirect the output, which is a bufferedoutputstream, wherever you want - eg. to an outwards physical port you know you can listen to 4) Is it properly try-caught (the error)? Or is the output "saying" wether it failed or not and how maybe... have to check. (but VM bugs happen, life's a bitch at times). 5) ...see my general purpose advice below. Mobile devices are very different from desktop devices for that matter : you cannot really rely on OOP as it should be and high level stuff, you have to understand the inner workings of the APIs in use to optimize properly. To do this, you need a debug environment that allows you to easilly recover output, profile, etc. My recommendation is the excellent, and free, Nokia J2ME development kit : it will allow you to test several architectures at once for any app, to profile, stacktrace, etc... easilly. Later on, this we, I will gather a few good references, links, etc. to get you started. Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu