by jcompagner » Wed Jan 02, 2013 12:43 pm
Then we need to have a real "mobile_module' type first. Because we need to know that it is really a mobile thing.
Problem is if you are starting to use that as a "dump" module for all kind of utility methods and also relations/datasources/calculations, that maybe are not used at all in the mobile solution you export, then you are using a lot more memory and stuff on the phone
So you need to be very very careful what you define in such a module.
Besides that we also really need a nice way to share the datamodel (calculations and relations) between the mobile solution and the service solution..
Currently we have that special module for that. But we are looking to create more a "binary" include for that of the whole mobile solution in such a service solution.
I say "binary" because you shouldn't really start coding or alter the mobile solution when you are coding the service solution.. Because this could completely break the mobile solution itself.
Johan Compagner
Servoy