Inside My Orphic Mind

Blackberry Compiler Error: Code section too large

Shraddha Kulkarni — Sun, 02 May 2010 18:21:07 +0000

Code section too large error is thrown when the code file size exceeds 64k size.
for a blackberry application cod file size is limited to 64k. It can have 64k code section and 64k data section. When an application file is more than 64k then it is broken in small parts and zipped together to form a larger code file.
For example. if application.cod file is 89k then this file will be divided in smaller parts as application-1.cod — 55k and application-2.cod — 34k and hen these will be archived together to form a application.cod file. If the class is to large then compiler will not be able to make such division and will throw the error
So whenever such error is shown generally the idea is to divide the larger classes in smaller parts, large methods in smaller ones.
While working on a project on Blackberry platform using J2ME Polish I used to get this message. When i checked the size of all cod files it was less than 64k but still compiler was throwing the error!!
When i checked polish.CSS file it was erroneous.

1 – The dot (.) was missing for some of the static styles and pseudo styles. After correcting the errors, the build was successful!!

.mainMenuItem {

	margin: 0px;

/*	font-color: #eee;

/*	background-color: #333; */

	border-color: #600; */

	border-width: 2px;

}

.mainMenuItem {

	margin: 0px;

/*	font-color: #eee;

	background-color: #333;

	border-color: #600; */

	border-width: 2px;

}

My Learning and Suggestion: - Whenever you are getting errors like code section too large or data section too large don’t forget to check your polish.css file for error and wrong syntax.

Porting J2ME Polish Application on Blackberry Storm/9500 series

Shraddha Kulkarni — Mon, 26 Apr 2010 10:47:51 +0000

Language:- J2ME Polish
Platform:- Blackberry
IDE- EasyEclipse 2.1.4

While porting and tuning a J2ME polish application on Blackberry Storm devices, we can not use ItemStateListener and ItemCommandListener both at the same time on an Item placed inside a cell of a TableItem.

for example -
TableItem tbl = new TableItem(2,3); StringItem si1 = new StringItem("Lable1","Text1"); si1.setDefaultCommand(cmd); si1.setItemCommandListener(this); tbl.set(0,0, si1); tbl.setItemStateListener(this);

In the above snippet table has ItemStateListener and SringItem has ItemCommandListener.
For Storm, on press event both the events are fired resulting in the ambiguity!
One of the 2 Listener is sufficient for performing the required action
I will suggest to use ItemStateListener on TableItem and perform the action depending upon the selected row and column.

Hello there!

Shraddha Kulkarni — Sat, 24 Apr 2010 15:02:48 +0000

Finally….. I have got a reason to start blogging!!!

Its been almost 3 years that i have been thinking about writing a blog , have my own Cyber home where i can share my thought and experience and opinions and many more. But never really had anything to say.

I am a newbie in Mobile Application development. Currently, I am working on Blackberry and Nokia devices using J2ME Polish. Mobile is one of the fastest growing field and the study material you get is comparatively very less! It will be my pleasure to share my experience through this Blog.

Say cheeeeeze :D