Android Question Application Architecture

[msali]

Hi,
I am creating an application having multiple Activity.
actPlayer (data stored in SQLite)
actCourse (Data stored SQLite and details in OS file based on Map through RandomAccessFile)
actRound (???)

App user adds players and course and based on this stored information gets to the actRound.

actRound is the core of my app and is very complex with tons of information and lots of code
I know how i will be saving it, i.e., base info in SQLite and complex info as Map in OS file.

My question is regarding the architecture of the application.

What is the best place to write the code of saving this complex information.
Since the functionality code in actRound is complex and huge, I tried to add a code module and also a class module. But in those module i do not have access to the variables and Views (few added through designer and many added programmatically) that i have added in my actRound.
(Do not want to move variables to Process_Globals)

Just want to know the best practice and approach.

Regards & thanks in adv.

 

[LucaMs]

It is not very clear for me; I think that you do not want to revolutionize the design already done.
So???

I think that the best practice is to "delegate" all the db operations to a dedicated module.

Access to other activities' "objects" (variables, views, ...) can be done through function routines (sometimes called by CallSubDelayed)

 

[msali]

Ok so what do i have to do to pass on all my variables & views to another routine written in another module.
or how do i utilize the CallSubDelay?

 

[LucaMs]

You can pass any object as parameter to sub routines; you just need to differentiate the cases in which you need to use CallSubDelayed instead of CallSub.

I suggest you read the purpose of callsubdelayed, on the site you can find lots of information and questions about this.

http://www.b4x.com/android/forum/pages/results/?query=CallSubDelayed&page=1&prefix=0

 

[mc73]

Do not want to move variables to Process_Globals

Why?

 

[msali]

Thanks.

Let me go through the info on site and will revert later.

regards,

 

[msali]

mc73: because there are tones of them (no issue in that) but mainly i have created many views programmatically. so do not know how to access them and data stored in them.

 

[LucaMs]

Why?

Because he is lazier than me

(or he does not want to make them accessible from anywhere)

 

[LucaMs]

mc73: because there are tones of them (no issue in that) but mainly i have created many views programmatically. so do not know how to access them and data stored in them.

Usually you have an input screen containing some views; simply call a "modDB" routine from that input actvitity, passing the views content as parameters

 

[mc73]

mc73: because there are tones of them (no issue in that) but mainly i have created many views programmatically. so do not know how to access them and data stored in them.

When you move on from one activity to the other, store your data 'somewhere' (globalVars can be that, a db, a raf or whatever) and get them back to your next actiivity. You can think of it as a 'form' submiting data. Agree with LucaMs, by the way

 

[msali]

Thanks for your responses.

regards.