Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums on April 1st. BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
- Kevin Michaluk, Founder, CrackBerry.com
06-02-2009 02:10 AM - edited 06-02-2009 02:12 AM
Is there any way to read cod://net_rim_theme_precision_zen_360x480_t/active
I need to access that theme's data (not the activecallscreen itself)
Is there a way to access it through file system ?
Edit: I just noticed I used completely wrong title. It could trick the reader into thinking this thread is about cod files as in output .cod files.
It is not. I mistakenly used that title. Sorry.
06-04-2009 10:00 AM
06-04-2009 10:09 AM
Thank you for the reply, but I was rather thinking of an Application access to those files.
I saw once in a debugger a reference to the mentioned 'cod://...' theme data path.
So I wondered, if maybe an application can access that data.
I am looking forward to reusing theme data for my apps since I always try to make them look as native as posible.
(for instance if I want to present the User with conversation cost list, wouldn't it be great if I could reuse current theme's call icons (missed call, recieved call,. etc.)?
And since Plazmic already gives such power to the User to create/use his favorite theme, why not give some amount of control to the Developers?
The Users and Developers (as you might already know) make a hell of a team
In this case we just need a little push from RIM
If we get access to the theme data (packed or not) I am sure we will make better native-looking apps. A three way gain for RIM, Users and Developers.