How to customize Midlogic J2ME apps with MidXML scripting language

1. Deep Customizing
Full Development Environment with MidXML

2. Powerful development environment
Top-notch rendering engine with 6 years of R&D
Full offline user experience
Scalable self-refreshing UI items
Automatic focus management
Optimized rendering algorithm
Effective and easy item stacking (hbox & vbox)
Item bordering with stylesheets for scalable graphics
Animation engine for rich user experience (improvements in v2.3)
Layered graphics even with Java MIDP 1.0 devices
Support for main JSRs like WMA/SMS API, MMAPI, Bluetooth
API, File Access API, Camera API
Full performance on mid-tier mass market phones!

3. Easy adoption from Web technologies
The paradigm for creating a ODP
Service with Midlogic is similar to the
WEB world
ODP Client customization uses MidXML,
a high level scripting language
comparable to html + JavaScript and
easily adopted by any Web designer
familiar with AJAX technologies
ODP Content is created just like
developing mini-web pages using
templates and action scripts (bones)
Service layer provides off-the-shelf
services like poll, RSS feeds, vote, quiz,
rate, blogpost etc.
For retrieving data from external sources
and integration, a XML API is provided
*World Class Product Award by Wireless Business and Technology Magazine 2003
*

4. Content
Customized and managed using Midlogic Admin Console Item
type and action editors, category manager, content templates and
services.
Application
Deep customization of framework screens
using any industry standard XML tool like
Eclipse and uploaded to server.
MidXML Client Architecture
Skin files
images
language files
stylesheet
Framework
Main menu template
Content template
Category template
Configuration
files
Billing mode
files
Splash screen
Error page
Framework Bones
Settings
Billing
information
Device
information
Geniem
Runtime
item type Actions
Text field
Image
Play tune
Title
Choice
Subscribe
Order
Item Types
Game
Wallpaper
Ringtone
News
Video
Subscription
Services
Comment
RSS
Content
data
Video
Images
Audio
Text
Menu
Structure
Sub-dir
Dir1
Main
Uploaded to server Managed with server

5. MidXML Client Scripting Language
UI components such as radio buttons can be made with MidXML UI
components
MidXML scripting language enable full customization and supports over
120 MidXML tags
Script Components made with midxml are called Actions (formerly known
as bones)
Midlogic server includes already made Actions for most of thinkable UI
scenarios.
If there is a new component that is needed but not included, it is easy to write it
with MIDXML
User interface is built with horizontal and vertical boxes. The content/
services are presented with Item templates and populated with data

6. Example: Artist Profile Item Type
Background
Image /
Content area
item name
Softkey1 Softkey2
cg2(vbox)
box3(vbox)
Field Name Action Location
Field 1 Image image box1
Field 2 Subtitle text box2
Field 3 Description text box3
Field 4 Rating rating box2
Field 5 Blog blogpost box3
description
Blog
box1
(hbox)
box2
(vbox)
image subtitle
rating
Item type and its fields
assigned to content template's
locations
Item types are created with item type editor.
Each field in item type can be mapped
to a specified location in the content area.
Content template defines locations, so by modifying
the content template xml file, box1, box2...etc.
Locations can be modified or added new ones.
Content template ps.xml
item

7. Client Generation Service
Generate JAR/JAD file pair for each target device and target language
Systems automatically assigns correct Core Engine, Framework, Skin and
Content Package based on device properties
Content Package size is based on device properties set in device manager
E.g. 40 target devices and 3 languages = 120 jar/jad files
Each time new content version is published, server creates both:
Integrated Packages for first time users (application + content)
Content Packages for updating users
MNC
MCC
MNC
MCC
MNC
MCC
Device A
Language X Language Y
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
Device B
Language X Language Y
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
MNC
MCC
Device C
Language X Language Y
MNC
MCC
MNC
MCC
MNC
MCC

8. Deep Customization via MidXML
Development
environment composes
from any XML editor like
Eclipse, SUN Wireless
toolkit and device
emulators
Example Actions
Text
Comment
Rate
Image
Example Action MidXML scripts
Text Action
Blogpost Action
<bone>
<st n=”FLD”/>
</bone>
<bone>
<va n="commenturi"/>
<vbox n="comments">
<space h="0" w="0"/>
</vbox>
<hbox n="commentnavi">
<space h="0" w="0"/>
</hbox>
<c p1="set" p2="$serviceurl,$serviceuri,cpid"
t="pie" url1="commenturi" url2="#1#2?
sid=1&itemid=#3&comments=1"/>
<c p1="load" t="pie" var1="commenturi"/>
</bone>

9. How to design for multiple handsets?
Skin design
(128 wide), (176-208 wide), (240 wide), (320 wide), (352 wide) skins
Design all skins to use scaling for small deviations in height and width
Skeleton design
Create simple structure for Low-end devices and restricted number of
bones & templates (runtime 38 kB + 15Kb for templates & bones)
Normal structure for mid-range phones (runtime 45 kB + 20 – 40 Kb for
templates & bones)
Add high-end features to high-end devices like file access and camera
usage (runtime 65 kB + 20 – 80 Kb for templates & bones)
Associate skins and skeletons to correct device groups