SynapseIndia mobile apps deployment framework internal architecture SynapseIndia Iphone Apps, SynapseIndia Android Apps, SynapseIndia Mobile Apps,

1. 1
Backup slides -
Deployment
SynapseIndia Mobile Apps
Deployment Framework internal
architecture

2. 2 17.02.2006
Device Management control flow
Device ManagementDevice Management
ImplementationImplementation
Device ManagementDevice Management
ImplementationImplementation
MTJ CoreMTJ Core
Plug-inPlug-in
MTJ CoreMTJ Core
Plug-inPlug-in
3: getImplementations(“Device Platform”)
return: DevicePlatformProvider [ ]
OutOutOutOut
2: getDevices(devicePlatformName)
1: getImplementations(“Device Management”)
return: DeviceManagement [ ]
DeviceDevice
PlatformPlatform
DeviceDevice
PlatformPlatform
4: getDevices()
return: Device [ ]
5: getImplementations(“Device Description”)
return: DeviceDescriptionProvider [ ]
DeviceDevice
Description Impl.Description Impl.
DeviceDevice
Description Impl.Description Impl.
6: getDeviceDescription( String vendor, String model)
return: DeviceDescription
return: Device [ ]

3. 3 17.02.2006
Device Platform ServicesDevice Platform ServicesDevice Platform ServicesDevice Platform Services
i/f
getDevicePlatforms() : DevicePlatform[]
getDevices(String devicePlatformName) :
Device[]
...
Device Platform, Device Platform Services
• Device Platform Services make it possible to query available Device Platforms.
• Based on Device Platform name it’s possible to get Devices or the Platform.

4. 4 17.02.2006
Device Platform
DevicePlatformType
type
Configuration
ConfigurationItem
name
label
description
value
validValues : String[]
1..*1..*
ConfigurationError
errorType
description
0..*0..*
+item
11
Device
name : String
description : String
DevicePlatform
getName() : String
getDevices() : Device[]
getConfiguration() : PlatformConfiguration
setConfiguration(PlatformConfiguration config)
deploy(Deployment application, DeviceDeployment[] devices)
run(String application, String deviceName)
debug(String application, String deviceName, DebugConfiguration debugConfig)
isDebugEnabled() : boolean
isAccessable() : boolean
getTypeInfo() : DevicePlatformType
openPreferencesDialog()
isPreferencesDialogAvailable() : boolean
openUtilitesDialog()
isUtilitesDialogAvailable() : boolean
getRuntimePlatformDefinitions() : RuntimePlatformDefinition[]
1..*1..*
11
11
Runtime Platform Definition
name
1..*1..*

5. 5 17.02.2006
Device
Screen
width
height
isColor
bitDepth
isTouch
DeviceCommunicationProtocol
Configuration
ConfigurationItem
name
label
description
v alue
v alidValues : String[]
1..*1..*
ConfigurationError
errorTy pe
description
0..*0..*
+item
11
Runtime Platform Definition
name
Device
name : String
description : String
1
+screen
1
1..*1..*
11
+runtimes
1..*
1..*
1..*
1..*

6. 6 17.02.2006
Runtime Platform
DeviceComfiguration Implementation
(from mtj)
JavaVirtualMachine
Specification
(from mtj)
ImplementationRef
fileRef : String
sourceRef : String
javadocRef : String
DeviceProfileAPI
Device OS Application
Device OS Application UI
0..10..1
OptionalServiceAPI
1
1..*1..*
1
DeviceProfile
name
profile name
profile version
1..*1..*
defines
Device OS
name
version
0..*0..*
DeviceConfiguration
Specification
name
configuration name
configuration version
1
1..*
+specification
1
1..*
11 defines
11
isExpanding
Runtime Platform Definition
name
11
11
Device
name : String
description : String
+runtimes
1..*
1..*
1..*
Java API
name
version
1..*
+apis
1..*
1..*
EmulatorDevice
RealDevice
model
1..*1..*
supports
11
JavaVirtualMachine Implementation
(from mtj)
11 isUsing
1..*
0..*
1..*
0..*
implements
0..*1..* 0..*1..*
1
0..*
1
+javaRuntime
JVM Ref
fileRef : String
sourceRef : String
javadocRef : String
0..*

7. 7 17.02.2006
ProjectJava API
name
version
JavaVirtualMachine Implementation
ImplementationRef
fileRef : String
sourceRef : String
javadocRef : String
JVM Ref
fileRef : String
sourceRef : String
javadocRef : String
DeviceProfile
name
profile name
profile version
DeviceConfiguration Specification
name
configuration name
configuration version
Project
1..*1..*
11
Runtime Platform Definition
name
11
11
11
1..* +apis1..*
0..*
1
0..*
+javaRuntime
1
Device
name : String
description : String
1..*1..*
+runtimes
1..*
1..*
1..*
1..*

8. 8
Code Editor
Code Editor internal architecture

9. 9 17.02.2006
Code Editor architecture
 tbd

10. 10 17.02.2006
DeviceDeviceD
P
APIs
D
C
ProjectProjectProjectProject
D
P
APIs
D
C
Project
1
Library JarLibrary Jar
1..n
Library JarLibrary Jar
1
1
• Mobile Project development is targeted to devices that have certain Device Configuration and
Device Profile. Therefore MTJ’s Project has also Device Configuration and Device Profile
defined.
• It’s possible to select a set of Service APIs to the Project. Based on the selected set of APIs
corresponding Jar –libraries are added to the project.
• Project always has default device that matches to the Projects definitions. That default device
also gives the needed Jar –libraries to the Project.
LEGEND:
DP
D
C
DP
APIs
DC •Project’s defined
Device Configuration
•Project’s defined
Device Profile
•Service APIs that are
selected to the Project
•Device’s Device
Configuration
•Device’s Device
Profile
•Service APIs that are
supported by the
Device
APIs
Mobile SDK Emulator