[kosh]

Hi,

Im new to BB development. Just wondering if the below scenario is possible and how to set it up.

Is it possible, to have two '.cod' files under the same application such that, '1.cod' gets an image and url from '2.cod'. However, '1.cod' cannot be recompiled. The only thing I want to do is change the image and url in '2.cod' and recompile it so that '1.cod' picks up the latest image and url.

Please let me know how i could do this. Help is greatly appreciated.

Thanks

[hrbuckley]

Yes you can. Off hand if you have either the source code or JAR file for 1.cod. Then you can have 2.cod call a method in 1.cod.

The other way would be to have 2.cod extend an object or implement an interface that 1.cod 'knows' about. 1.cod could fetch the class by name at run time, create an object and call a method.

[kosh]

thanks for the response.

I dont have the src or jar file for 1.cod....all I will have is the .cod file.

With respect to option 2, I'm not sure I understand what you mean with the 'interface or object that 1.cod knows about'. can u give me an example?

[hrbuckley]

If 1.cod was compiled with code to load a class by name from a module you could specify, then you just write that class to return the data you want. Basically both 1.cod and 2.cod have to be written to support the communications. It sounds like this is not the case, and you don't have control over 1.cod. If this is correct that AFAIK you're out of luck.

[kosh]

Hey, sorry, I probably explained wrong.

Its not that 1.cod is not editable at all. basically, 1.cod is not my application, it is someone elses, but I can tell that person (give him a code guideline) and tell him that so and so is what he needs to do to communicate with my 2.cod that contains the pic and url.

So now, if 1.cod were to call a method from a class in 2.cod, doesnt this mean that 2.cod has to be set up as a library project and 1.cod has to have a dependency on 2.cod (in order to access its modules)?

[Dougsg38p]

In order for these two apps to share objects, they'll have to have a shared namespace (like a library).

Sounds to me like you might be better off using global events, and passing the RIM standard objects that are in the shared RIM runtime library.

[hrbuckley]

Originally Posted by kosh

So now, if 1.cod were to call a method from a class in 2.cod, doesnt this mean that 2.cod has to be set up as a library project and 1.cod has to have a dependency on 2.cod (in order to access its modules)?

There are ways to do that while avoiding library semantics, but since this is a collaborative effort what I would recommend is that 1.cod expose a class and method specifically for 2.cod (and others perhaps) to call to set the data in a way similar to the RIM libraries:

My1CodClass.getInstance().setURL(String url);

When 1.cod is compiled a JAR file will be produced. Use that JAR as an external library to compile 2.cod, 3.cod, 4.cod, etc. In this case 1.cod doesn't need any prior knowledge about where the data is going to come from.

If 1.cod must control when the data is fetched, then you can use:

try {
    Class class = Class.forName("my.cod.DataClass");
    my.cod.DataClass dataClass = class.newInstance();
    String url = dataClass.getUrl();
} catch (ClassNotFoundException e) {
    // Processing for class not found, for example if 2.cod is not loaded on the device.
}

In this case 1.cod and 2.cod would have to share the definition of my.cod.DataClass.

I've used both of these methods.

You could also use the RuntimeStore and global events as suggested above